Hi guys,
We are running functional tests on the CentOS OpenStack images, in particular the Hyper-V ones. The results so far are very positive.
The testing environment consists in a multi node RDO OpenStack Grizzly deployment on top of CentOS 6.4, using additional Hyper-V Server 2012 compute nodes. We’re going to add Havana and Hyper-V 2012 R2 as well, since both have been publicly released this month.
The configuration of OpenStack RDO, including the Hyper-V nodes is entirely unattended:
https://github.com/cloudbase/unattended-setup-scripts/blob/master/configure-...
Once RDO is up and running, the CentOS image to be tested is deployed in a fully unattended way as well:
https://github.com/cloudbase/job-runner/blob/master/jobs/openstack_create_in...
As soon as the VM has been deployed on the Hyper-V compute node, we access it by using the openstack SSH key pair on the floating IP assigned by Quantum / Neutron to the instance. This means that cloud-init did its job properly and that the public key has been properly deployed.
ssh root@$FLOATING_IP
yum -y install git && git clone git://gitorious.org/testautomation/t_functional.git && cd t_functional && time ./runtests.sh" > t_functional_out.txt 2> t_functional_err.txt
At this point we check ?$ to make sure the tests went ok.
Here’s the output from one of the runs:
t_functional_out.txt http://paste.openstack.org/show/50135/
t_functional_err.txt http://paste.openstack.org/show/50137/
The test environment uses only OSS and freely available software, which means that we focus mainly on the free Hyper-V releases in order to give a change to anybody to replicate the tests without incurring into additional costs.
This is of course meant to be a starting point for a discussion on how to test those images, please let me know what do you think!
Note: to add some additional context, one of our principal activities consists in developing and maintaining the Hyper-V bits in OpenStack (Nova, Neutron, Ceilometer, etc) along with Cloudbase-Init and Crowbar.
Thanks,
Alessandro
Cloudbase Solutions http://www.cloudbase.it
On 29 Oct 2013, at 16:25 , Florian La Roche Florian.LaRoche@gmx.net wrote:
Hello Karanbir,
My assumption was that people would ssh-key login via root, after using the metadata service to inject a ssh-key; is that an unfair assumption here ?
Right, this should be the normal case.
The thought of having a pre-setup root password in images that might make it to public interfaces is a bit unsettling.
So the current image already disables password login for ssh. And I think Nux is right to also remove the root password in /etc/shadow completely.
For the "problem case" where e.g. ssh over the network might be broken then cloud-init needs to inject a root password or something similar to allow for console access.
For people now looking at the new OpenStack Havana release: If you want to setup your own test cloud ontop of CentOS-6.4, please have a look at http://jur-linux.org/testwiki/index.php/CloudLinux/OpenStack
this looks like a good resource - both for people starting off and for people looking at references specific for the EL base. We could do with something like this at wiki.centos.org/Cloud/OpenStack - fancy hacking that up ?
If I get the right access, I'd be happy to move information over to the centos wiki.
P.S.: Will the script to setup this CentOS image also be available to allow for many stable/customized versions to show up?
yes, I might have cleaned up the kickstarts; but in future builds those should still be in place. The image is built from an anaconda run, and not a loop mounted package injection process.
Looking forward to these.
best regards,
Florian La Roche
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel