Update: The setup is now reliably functional with xen and kvm hosts coming up successfully, mgmt servers spinning up fine, server health is also good with systemvms up and functional. A misbehaving network issue prevented us from turning on the infra. This is now worked around:
All the sequence of jobs are on: http://jenkins.cloudstack.org/view/cloudstack-qa/ (Currently set to test against the 4.1 branch. The packaging has been broken for a couple of days but the setup will use the lastSuccessfulBuild) test-matrix (master job that triggers all others, xen, kvm profiles are running) - test-packaging (latest package tested from the s3 repo at yum.cloudstack.org) - test-environment-refresh (xen/kvm hosts are reimaged and agent package is seeded) (Above two run in parallel) - test-setup-advanced-zone (brings up an advanced zone) - test-cloudstack-smoke (right now server health is checked, but will be adding the actual tests tomorrow) Most of the work has been happening on github [1] [2] making it less visible on the lists. My fault entirely. I know this might have caused some impatience among folks. But hopefully we can pull off 100% pass rate before 4.1 goes out the door! [1] https://github.com/vogxn/acs-infra-test/tree/4.1 [2] https://github.com/vogxn/cloud-autodeploy/tree/acs-infra-fmt Thanks, -- Prasanna., On Fri, Feb 22, 2013 at 08:17:49PM +0530, Prasanna Santhanam wrote: > 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.,
