The build pipeline for running marvin tests on physical hardware is
now finally shaping up. The test-matrix [1] runs through a few valid
configurations across hypervisors and distributions. Please have a
look.
Currently the RPM package is tested with a centos63 distro. I'll add
ubuntu as well when the packaging is sorted. The hypervisors enabled
are the ones in the OSS package (kvm and xen).
test-matrix splits into a few jobs after choosing a hypervisor and a
distro for the management server
- test-packaging (installs the latest packages from
yum.cloudstack.org)
- test-environment-refresh (cleans up the hypervisors to prepare a
fresh run)
- test-setup-advanced-zone (brings together an advanced zone, TODO:
basic zone deployments)
- test-cloudstack-smoke (disabled for now until above jobs
stabilize, will run the existing smoke tests)
All the end-to-end configuration is automated using puppet recipes and
there is negligible manual interference at this point. Except to
collect logs, which I'll push on to the jenkins artifacts too.
The plan is to have functional tests hitting the repo run immediately
on the existing configuration. As well as run tests on a regular
schedule. I'll put together the schedule - a complete regression suite
twice a week and a smoke test every few hours would be the goal I'd
like to begin with.
The tests being dated will likely have failures and I'll start fixing
them starting early next week. Patches and fixes welcome.
[1] http://jenkins.cloudstack.org/view/cloudstack-qa/job/test-matrix/
Thanks,
--
Prasanna.,
