anchor.diff:  In general its best to stick to testing in vagrant because the bats scripts are
   destructive. When working with a single package its generally faster to run its
   tests in a tighter loop than maven provides. In one window:
  +
   --------------------------------
   mvn -pl distribution/rpm package
   --------------------------------
  +
   and in another window:
  +
   ----------------------------------------------------
   vagrant up centos-7 && vagrant ssh centos-7
   cd $RPM
  
positive.code: ----------------------------------------------------
  
  If you wanted to retest all the release artifacts on a single VM you could:
  -------------------------------------------------
  # Build all the distributions fresh but skip recompiling elasticsearch:
  mvn -amd -pl distribution install -DskipTests
  
negative.code: 
  . Smoke test the maven/ant dance that we use to get vagrant involved in
  integration testing is working:
  
  ---------------------------------------------
  mvn -Dtests.vagrant -Psmoke-vms -pl qa/vagrant verify
  ---------------------------------------------
  
  or this to validate all the VMs:
  
  -------------------------------------------------
  mvn -Dtests.vagrant=all -Psmoke-vms -pl qa/vagrant verify
  -------------------------------------------------
  
  That will start up the VMs and then immediate quit.
  
  . Finally run the tests. The fastest way to get this started is to run:
  
  -----------------------------------
  mvn clean install -DskipTests
  mvn -Dtests.vagrant -pl qa/vagrant verify
  -----------------------------------
  
  You could just run:
  
  --------------------
  mvn -Dtests.vagrant verify
  --------------------
  
  but that will run all the tests. Which is probably a good thing, but not always
  what you want.
  
  