Ryan,
This is great! I had not thought of using vagrant in this
way. In order to be able to test my own changes in as many
environments as possible, I have started working with your vagrant
file and added a bunch of VMs as you mentioned. Vagrantfile
attached and work ongoing here:
https://github.com/ubccr/pcp/tree/vagrant_test
A "vagrant up" will start , provision and run qa on all the
hosts. The provisioning happens in serial and the QA runs happen
in parallel. I have a script that does the provisioning in
parallel, but my host machine is not powerful enough to support
that, kept getting disk errors.
After the qa is done, any .bad files as well as the QA output
itself are copied to a new "qaresults" hierarchy in the current
directory. Probably could scripts something to do a simple
analysis on the results.
If you had a good enough host machine, you could probably run all
the VMs at once, but vagrant up will also take a regex, so I tend
to do something like:
vagrant up /centos.*/
or depending on your shell
vagrant up \/centos.\*\/
The boxes are all standard vagrant cloud images except opensuse.
I couldn't get that to boot, so had to build my own from the bento
project, so those are commented out in the vagrantfile.
Some of the QA tests trigger the OOM killer with 512 MB VMs. It's
likely that at least 1024 is needed. I haven't looked too much
into that yet.
You can configure the VM characteristics as well as the QA tests
to run with a few variables at the top.
Thanks
Martins
On 12/11/14 5:53 PM, Ryan Doyle wrote: