On Fri, Feb 08, 2013 at 12:32:02PM -0500, Hugo Trippaers wrote: > Hey guys, > > Just a quick note before the weekend with a status update on RPM. > > The management server package is pretty much done and installation > on a clean system works like a charm. This is actually tested every > few hours with a Jenkins setup a colleague and I built. We take the > sources, compile and package. The packages are added to a repo and > chef is used to deploy two new clean CentOS 6.3 boxes. One is > configured as database server and another one as CloudStack > management server by chef. After installation an ApiKey is created > for the admin user. This proves that the package can be installed on > a clean system and that the management server starts.
Just tested the rpms myself and they are working well. Well done! I'll be setting up a public repository to host packages so such test jobs can use them downstream. Wido's repo can hold the released binaries while these can be unstable. > Next week: > * we will continue with the setup and add some real tests to create zones > and add hypervisors. > *I will also start testing with the agent and usage package, they are > created at the moment but not tested for functionality. > * Deploy fedora 18 image and extend the test to that > * Deploy Ubuntu 12.04 and add packaging scripts for that (check with > wido/noa) This is really cool Hugo. I've connected my test infrastructure to run your packaging job as a test as well [1]. The system I'm using is similar to yours except I'm using puppet in place of chef for my configuration. Would you guys be able to setup your jobs via jenkins.cs.o as well? I'd ideally love to see multi-site environments running tests. Also we should perhaps standardize on some marvin configurations for the zones. I'm going to start with advanced zone with kvm and xenserver. I've got hypervisors refreshing using cobbler kickstarts and added some dashboards to cobbler and puppet so it's not all command line now :) On my TODO list this week are: 0) ubuntu packaging tests 1) configuring zones for kvm and xen 2) jobs for marvin smoke tests 3) jobs for regression tests per component 4) upstreaming debug logs to jenkins for troubleshooting [1] http://jenkins.cloudstack.org/view/cloudstack-qa/job/test-packaging-rhel63/ -- Prasanna.,
