On Fri, Feb 22, 2013 at 10:55:33AM -0500, Mice Xia wrote: > > > That's really awesome, some questions: > > Is the hypervisor installed on physical machine or VM?
Correct, physical machines are used. We are experimenting the same solution on a nested virtualization environment using vmware. So far we haven't seen a significant reduction in time for provisioning physical hw vs virtual hw. Now we are trying to use restored snapshots of hypervisors for this but that's still a WIP. > is it possible to test VMware? I intend to. Right now the cloudstack packages are built for OSS (xen and kvm) and once vmware goes into OSS including it is as simple as including a kickstart file for the esxi hypervisor in our setup. > Any guideline to setup this env? I'm writing up some guidelines and will update this thread with the instructions from wiki. To give an overview: A single multi-homed (one per pod) centos VM is installed with - cobbler (for pxe booting and reimaging virtual and physical nodes) - puppet (for configuring kvm agents and cloudstack mgmt server) - ipmi (for power mgmt) - dnsmasq (for dhcp and DNS) - some driver scripts to trigger (via jenkins) and relaying status/progress between ipmi-cobbler-puppet Workflow is as follows: given a marvin JSON description of the cloud we parse the physical resources out of it and trigger an environment refresh. There is a new cobbler profile created everytime a physical resource is to be refreshed. A new mgmt server VM is spun up which is installed with latest packages available. Once mgmt service is running, systemvm template seeded, storage cleaned and hosts are up - we deploy CloudStack and wait for favourable system health (systemvm up, builtin templates ready) to start triggering tests. Since cloudstack deployments differ from the kind of storage layer used, networking configuration etc the current setup has its limitations. But hopefully some of our work will be usable for others to set up similar test deployments -- Prasanna., > > 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.,
