Hi,
CentOS-6.4 i386 and x86_64 images targetting OpenStack are now available for testing at http://dev.centos.org/centos/hvm/ Images are available for KVM, Hyper-V, VMware, Xen and any other HVM hypervisor. Although, the 6.x kernel has the pv support enabled, so should work fine under paravirt Xen as well.
Images are published as raw, qcow2 qcow2compressed and vpc ( vhd ) for both i386 and x86_64 CentOS-6.4 The images represent media versions, and have not had an update run against them. Its highly recommended that in testing, please check this version *then* do a yum update and repeat tests to ensure that there is no test result change in the 6.4+updates tree's.
Keeping in line with the general CentOS Cloud strategy, ie to help people migrate or investigate cloud instances, we expect the images to represent as close as possible to a real machine CentOS install ( ie. no cloud specific user, people use root to login, selinux is enabled ). With some exceptions like isdn support is removed, as is cups and bluetooth since those things make little sense on a cloud instance ( nothing stopping the users from installing them later if they need to ).
Also, cloud-init is included. This is based on the 0.7.x stream and based off sources published by Red Hat in their RHEL-Common/ tree.
md5sums: ac6c1f683f18ec2742fc620930b6b77a CentOS-6.4-i386-Minimal-OpenStack.image.bz2 ac6c1f683f18ec2742fc620930b6b77a CentOS-6.4-i386-Minimal-OpenStack.image.qcow2.bz2 d0ef1077886714d9808eb21b0d35b64e CentOS-6.4-i386-Minimal-OpenStack.image.qcow2c.bz2 853487ac600963da6c00f69be10f11d5 CentOS-6.4-i386-Minimal-OpenStack.image.raw.bz2 dc16f7339c97856514ce35f65196a928 CentOS-6.4-i386-Minimal-OpenStack.image.vpc.bz2 9169abb16ad2b0a0195574fc8c7c6e7a CentOS-6.4-i386-Minimal-VMware.image.vmdk.bz2 1c1ff6ffca8ca7845f49a017f5386961 CentOS-6.4-x86_64-Minimal-OpenStack.image.bz2 1c1ff6ffca8ca7845f49a017f5386961 CentOS-6.4-x86_64-Minimal-OpenStack.image.qcow2.bz2 2d9a25fa573b3c512e97c9d6cea64657 CentOS-6.4-x86_64-Minimal-OpenStack.image.qcow2c.bz2 f701914d4eafb563b086853cd8e7e79d CentOS-6.4-x86_64-Minimal-OpenStack.image.raw.bz2 8476063151f9163ba37e260e144270e1 CentOS-6.4-x86_64-Minimal-OpenStack.image.vpc.bz2 a68f0bd1328bd67056e07be8501607a0 CentOS-6.4-x86_64-Minimal-VMware.image.vmdk.bz2
sha256sums: 2418f233fabc02074e54f705667ba16e2845883863e5c2e860ffc5b615f1a096 CentOS-6.4-i386-Minimal-OpenStack.image.bz2 2418f233fabc02074e54f705667ba16e2845883863e5c2e860ffc5b615f1a096 CentOS-6.4-i386-Minimal-OpenStack.image.qcow2.bz2 1156a84f18c62e5bb04d82976e6c7aa412c8486de0780e35b42f97697fe06aed CentOS-6.4-i386-Minimal-OpenStack.image.qcow2c.bz2 70c9c4f1a44b8ef349ca13da1993c1b9211a1ec72f68b4ddfc85ad21e70e6e97 CentOS-6.4-i386-Minimal-OpenStack.image.raw.bz2 ec1e5ab7508d9139df110e4a5c957c56a4dc6011fc8030cb6e48d3f6a27866ab CentOS-6.4-i386-Minimal-OpenStack.image.vpc.bz2 675c9717b82b71833cb074e76357aa2325d03730d989507110caa0e6d2e4cb5c CentOS-6.4-i386-Minimal-VMware.image.vmdk.bz2 a68e76596568b9e3117f021ba4d1db983b763ef31097b9aa47139927dcbf14bc CentOS-6.4-x86_64-Minimal-OpenStack.image.bz2 a68e76596568b9e3117f021ba4d1db983b763ef31097b9aa47139927dcbf14bc CentOS-6.4-x86_64-Minimal-OpenStack.image.qcow2.bz2 888da1ac03dd78027421db0629d899187456058a72a6e555d459bcb1d4f20296 CentOS-6.4-x86_64-Minimal-OpenStack.image.qcow2c.bz2 4626a83e8d0c706d9303874d0e26d2b127983207adb7a64e079e359e6b33a156 CentOS-6.4-x86_64-Minimal-OpenStack.image.raw.bz2 3bd4c91b276e9b4a049fd5ecd32e6e538593331a1298162ffe07e9033eefd903 CentOS-6.4-x86_64-Minimal-OpenStack.image.vpc.bz2 8c70a927d761e99e1529585b43d8dc2e080977b00436ec7038288d542fba6d4c CentOS-6.4-x86_64-Minimal-VMware.image.vmdk.bz2
Note: these images have not been through a regular CentOS QA cycle, and I am requesting people to actually test these in either dev or test environments that run the hypervisor being tested, the cloud controller being tested and provide feedback here to the mailing list. Please clearly indicate what hypervisor was used, what cloud controller and versions of the relevant software.
As a baseline the CentOS CI tests ( https://gitorious.org/testautomation/t_functional ) is a good place to start, if you just need tests to run ( although these tests mostly target machine instances, its still a good baseline for these images ). And while you are at it, please feel free to submit cloud, virtualised, instance and image specific tests.
The overall aim is to be ready for inclusion of Cloud image release in sync with iso and distro release for next-version ( 6.5 most likely ).
Apart from baseline testing, I am also looking for feedback on package manifests included in the images ( should we add something ? should we remove something ? ) and if there is any need / scope for publishing specific role images as well ? ( eg. should we do a LAMP image ? )
Finally, I want to thank Alessandro and Octavian from Cloudbase Solutions for helping get this effort off the ground, and then their patience as I went through the mechanics of automating the build process and getting the images ready.
Enjoy!
Hello Karanbir,
On Thu, Oct 24, 2013 at 05:38:18PM +0100, Karanbir Singh wrote:
Hi,
CentOS-6.4 i386 and x86_64 images targetting OpenStack are now available for testing at http://dev.centos.org/centos/hvm/ Images are available for KVM, Hyper-V, VMware, Xen and any other HVM hypervisor. Although, the 6.x kernel has the pv support enabled, so should work fine under paravirt Xen as well.
Works for me with OpenStack Havana with kvm and your qcow2 image.
Images are published as raw, qcow2 qcow2compressed and vpc ( vhd ) for both i386 and x86_64 CentOS-6.4 The images represent media versions, and have not had an update run against them. Its highly recommended that in testing, please check this version *then* do a yum update and repeat tests to ensure that there is no test result change in the 6.4+updates tree's.
Keeping in line with the general CentOS Cloud strategy, ie to help people migrate or investigate cloud instances, we expect the images to represent as close as possible to a real machine CentOS install ( ie. no cloud specific user, people use root to login, selinux is enabled ).
This is a very good decision.
Image logs good to the log output and console seems to wok fine. Is there a root password setup? Ssh also accepts password login per default. (My favourite would be a standard password people can login on the console, but only allow ssh login via ssh keys. ??)
With some exceptions like isdn support is removed, as is cups and bluetooth since those things make little sense on a cloud instance ( nothing stopping the users from installing them later if they need to ).
Good.
Also, cloud-init is included. This is based on the 0.7.x stream and based off sources published by Red Hat in their RHEL-Common/ tree.
Good.
Apart from baseline testing, I am also looking for feedback on package manifests included in the images ( should we add something ? should we remove something ? ) and if there is any need / scope for publishing specific role images as well ? ( eg. should we do a LAMP image ? )
Minimal image first, this one looks good.
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
best regards,
Florian La Roche
P.S.: Will the script to setup this CentOS image also be available to allow for many stable/customized versions to show up?
+1 for below... I am new to use this image, may i know the default password for root? ================================= Image logs good to the log output and console seems to wok fine. Is there a root password setup? Ssh also accepts password login per default. (My favourite would be a standard password people can login on the console, but only allow ssh login via ssh keys. ??)
On Fri, Oct 25, 2013 at 3:10 AM, Florian La Roche Florian.LaRoche@gmx.netwrote:
Hello Karanbir,
On Thu, Oct 24, 2013 at 05:38:18PM +0100, Karanbir Singh wrote:
Hi,
CentOS-6.4 i386 and x86_64 images targetting OpenStack are now available for testing at http://dev.centos.org/centos/hvm/ Images are available for KVM, Hyper-V, VMware, Xen and any other HVM hypervisor. Although, the 6.x kernel has the pv support enabled, so should work fine under paravirt Xen as well.
Works for me with OpenStack Havana with kvm and your qcow2 image.
Images are published as raw, qcow2 qcow2compressed and vpc ( vhd ) for both i386 and x86_64 CentOS-6.4 The images represent media versions, and have not had an update run against them. Its highly recommended that in testing, please check this version *then* do a yum update and repeat tests to ensure that there is no test result change in the 6.4+updates tree's.
Keeping in line with the general CentOS Cloud strategy, ie to help people migrate or investigate cloud instances, we expect the images to represent as close as possible to a real machine CentOS install ( ie. no cloud specific user, people use root to login, selinux is enabled ).
This is a very good decision.
Image logs good to the log output and console seems to wok fine. Is there a root password setup? Ssh also accepts password login per default. (My favourite would be a standard password people can login on the console, but only allow ssh login via ssh keys. ??)
With some exceptions like isdn support is removed, as is cups and bluetooth since those things make little sense on a cloud instance ( nothing stopping the users from installing them later if they need to ).
Good.
Also, cloud-init is included. This is based on the 0.7.x stream and based off sources published by Red Hat in their RHEL-Common/ tree.
Good.
Apart from baseline testing, I am also looking for feedback on package manifests included in the images ( should we add something ? should we remove something ? ) and if there is any need / scope for publishing specific role images as well ? ( eg. should we do a LAMP image ? )
Minimal image first, this one looks good.
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
best regards,
Florian La Roche
P.S.: Will the script to setup this CentOS image also be available to allow for many stable/customized versions to show up?
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On Fri, Oct 25, 2013 at 04:33:32PM +0800, mail.zhang.yee wrote:
+1 for below... I am new to use this image, may i know the default password for root? ================================= Image logs good to the log output and console seems to wok fine. Is there a root password setup? Ssh also accepts password login per default. (My favourite would be a standard password people can login on the console, but only allow ssh login via ssh keys. ??)
Also sudo could be configured to allow the "cloud-user" access to root/ALL. "cloud-user" seems to not have any password set, so ssh keys are probably the only way for login.
best regards,
Florian La Roche
On 25.10.2013 09:33, mail.zhang.yee wrote:
+1 for below... I am new to use this image, may i know the default password for root? ================================= Image logs good to the log output and console seems to wok fine. Is there a root password setup? Ssh also accepts password login per default. (My favourite would be a standard password people can login on the console, but only allow ssh login via ssh keys. ??)
-1 , I'm against this. Cloud-init and Openstack Havana seem (untested) to support setting an admin password as well in addition to the SSH key and I'd rather be able to use this feature. If the images are for Openstack then they should be so all the way. As such the SSH root login should be enabled and the root password should be randomly generated and unknown.
If anyone really wants to change the password to something known to them libguestfs can be used (e.g. virt-edit) or just boot into single user mode, though this should not be necessary as cloud-init should set the provided admin password.
My 2 slips of gold-pressed latinum.
On 10/25/2013 09:33 AM, mail.zhang.yee wrote:
+1 for below... I am new to use this image, may i know the default password for root? ================================= Image logs good to the log output and console seems to wok fine. Is there a root password setup? Ssh also accepts password login per default. (My favourite would be a standard password people can login on the console, but only allow ssh login via ssh keys. ??)
I'm not too keen on having a published access password on these images, the idea would be that people use whatever metadata service they are keen on, specific to their cloud setup, to inject keys and take it from there.
We can disable password access in sshd by default, how does everyone feel about that ?
Regards
Hi,
On 10/24/2013 08:10 PM, Florian La Roche wrote:
Hello Karanbir,
On Thu, Oct 24, 2013 at 05:38:18PM +0100, Karanbir Singh wrote:
Hi,
CentOS-6.4 i386 and x86_64 images targetting OpenStack are now available for testing at http://dev.centos.org/centos/hvm/ Images are available for KVM, Hyper-V, VMware, Xen and any other HVM hypervisor. Although, the 6.x kernel has the pv support enabled, so should work fine under paravirt Xen as well.
Works for me with OpenStack Havana with kvm and your qcow2 image.
thanks!
Image logs good to the log output and console seems to wok fine. Is there a root password setup? Ssh also accepts password login per default. (My favourite would be a standard password people can login on the console, but only allow ssh login via ssh keys. ??)
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 ?
The thought of having a pre-setup root password in images that might make it to public interfaces is a bit unsettling.
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 ?
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.
regards
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
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
On 24.10.2013 17:38, Karanbir Singh wrote:
Hi,
CentOS-6.4 i386 and x86_64 images targetting OpenStack are now available for testing at http://dev.centos.org/centos/hvm/ Images are available for KVM, Hyper-V, VMware, Xen and any other HVM hypervisor. Although, the 6.x kernel has the pv support enabled, so should work fine under paravirt Xen as well.
Images are published as raw, qcow2 qcow2compressed and vpc ( vhd ) for both i386 and x86_64 CentOS-6.4 The images represent media versions, and have not had an update run against them. Its highly recommended that in testing, please check this version *then* do a yum update and repeat tests to ensure that there is no test result change in the 6.4+updates tree's.
Keeping in line with the general CentOS Cloud strategy, ie to help people migrate or investigate cloud instances, we expect the images to represent as close as possible to a real machine CentOS install ( ie. no cloud specific user, people use root to login, selinux is enabled ).
This is great news, good job!
Really glad to see acpid was not excluded. Ctrl+alt+del ftw! :-)
One suggestion, please add also this to kernel command line so we can get some VNC output during boot as well: console=tty0
I'm not sure if the included cloud-init contains the grow root feature, but if it does is LVM partitioning supported?
Hi,
On 10/24/2013 10:34 PM, Nux! wrote:
This is great news, good job!
Really glad to see acpid was not excluded. Ctrl+alt+del ftw! :-)
It was in the intial builds, but I quickly realised that wasent going to work.
One suggestion, please add also this to kernel command line so we can get some VNC output during boot as well: console=tty0
Is tty0 something that is always in place ? isnt it Serial emulated as well in some situations ?
I'm not sure if the included cloud-init contains the grow root feature, but if it does is LVM partitioning supported?
No, i dont think this one does. its 0.7.1 based - also, is there a really stable growroot option somewhere ? I've seen quite a few different solutions, but they all mostly seem site specific or make assumptions about how the disks are setup, images are built and how they are deployed.
Regards
On 28.10.2013 12:41, Karanbir Singh wrote:
One suggestion, please add also this to kernel command line so we can get some VNC output during boot as well: console=tty0
Is tty0 something that is always in place ? isnt it Serial emulated as well in some situations ?
I don't know about other situations, but with these templates the output goes only to the serial tty (ttyS0) so it can be viewed in the openstack log file. If you add console=tty0 we'll also be able to see the same output on the VNC window, just like with a real server. No idea why openstack templates ommit this.
I'm not sure if the included cloud-init contains the grow root feature, but if it does is LVM partitioning supported?
No, i dont think this one does. its 0.7.1 based - also, is there a really stable growroot option somewhere ? I've seen quite a few different solutions, but they all mostly seem site specific or make assumptions about how the disks are setup, images are built and how they are deployed.
But you DO know how the image is setup and will be deployed. :-) My approach was running fdisk from initrd and should be quite safe assuming the image/template is used as it was meant, i.e. on KVM.
Anyway, EPEL provides "dracut-modules-growroot":
Description : This dracut module will re-write the partition table of a disk so that the : root partition has as much space as possible, bumping it up to the edge of the : disk, or the edge of the next partition.
I would imagine it doesn't work with LVM. I have a test RDO set up and will try a generate a template with this dracut module included. I'll keep you updated.
Hi Guys,
On 10/24/2013 05:38 PM, Karanbir Singh wrote:
CentOS-6.4 i386 and x86_64 images targetting OpenStack are now available for testing at http://dev.centos.org/centos/hvm/ Images are available for KVM, Hyper-V, VMware, Xen and any other HVM hypervisor. Although, the 6.x kernel has the pv support enabled, so should work fine under paravirt Xen as well.
We found a couple of things:
1) The udev persistence rules are still there, those need to go - otherwise snapshot + boot of snapshot is a problem
2) The cloud-user account is still being created, we need to disable that.
3) cloud-init is, at the moment, setup to disable root access - but that does not seem to be happening in some cases, whereas in other cases it does. We need to figure that out.
4) there is no grow-root, while this should not be a blocker for the existing / present images - we should fix this for 6.5
Comments / thoughts ?
- KB
Hello Karanbir Singh,
On Thu, Oct 24, 2013 at 05:38:18PM +0100, Karanbir Singh wrote:
Hi,
CentOS-6.4 i386 and x86_64 images targetting OpenStack are now available for testing at http://dev.centos.org/centos/hvm/ Images are available for KVM, Hyper-V, VMware, Xen and any other HVM hypervisor. Although, the 6.x kernel has the pv support enabled, so should work fine under paravirt Xen as well.
Images are published as raw, qcow2 qcow2compressed and vpc ( vhd ) for both i386 and x86_64 CentOS-6.4 The images represent media versions, and have not had an update run against them. Its highly recommended that in testing, please check this version *then* do a yum update and repeat tests to ensure that there is no test result change in the 6.4+updates tree's.
Keeping in line with the general CentOS Cloud strategy, ie to help people migrate or investigate cloud instances, we expect the images to represent as close as possible to a real machine CentOS install ( ie. no cloud specific user, people use root to login, selinux is enabled ). With some exceptions like isdn support is removed, as is cups and bluetooth since those things make little sense on a cloud instance ( nothing stopping the users from installing them later if they need to ).
Are there also CentOS-6.5 images available? Or has the repository moved to a more official CentOS location and has newer releases available?
The overall aim is to be ready for inclusion of Cloud image release in sync with iso and distro release for next-version ( 6.5 most likely ).
Might not have happened. I think official CentOS cloud images are really important and should be shared broadly.
best regards from Germany,
Florian La Roche
-
Alessandro Pilotti -
Florian La Roche -
Karanbir Singh -
mail.zhang.yee -
Nux!