hi,
I have just pushed a public build for a qcow2 image, this should be suiteable for any HVM environment. Please test as widely as possible.
http://buildlogs.centos.org/centos/7/cloud/
I also spoke with Rich Jones earlier in the day today and we will try and get virt-builder images registered, with signs etc ready to go in sync with 7GA, making it much easier for people to get and consume these images on standalone virtualised environs.
Send reports here, or to bugs.centos.org, but note: there is no cloud-init included as yet. I spoke with Sam Kottler earlier as well today and he's going to work on pushing that through soon.
- KB
On 06/21/2014 03:10 AM, Karanbir Singh wrote:
hi,
I have just pushed a public build for a qcow2 image, this should be suiteable for any HVM environment. Please test as widely as possible.
root pw on that image is 'builder'
Boot on KVM with OpenStack went well.
Will the image contain cloud-init and a set of default repo lists enabled in future ?
Tim
-----Original Message----- From: centos-devel-bounces@centos.org [mailto:centos-devel- bounces@centos.org] On Behalf Of Karanbir Singh Sent: 21 June 2014 04:11 To: centos-devel@centos.org Subject: Re: [CentOS-devel] Cloud and VM Images
On 06/21/2014 03:10 AM, Karanbir Singh wrote:
hi,
I have just pushed a public build for a qcow2 image, this should be suiteable for any HVM environment. Please test as widely as possible.
root pw on that image is 'builder'
-- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On 06/21/2014 03:53 AM, Tim Bell wrote:
Boot on KVM with OpenStack went well.
Will the image contain cloud-init and a set of default repo lists enabled in future ?
Tim
That is the plan, yes (cloud-init and repos)
-----Original Message----- From: centos-devel-bounces@centos.org [mailto:centos-devel- bounces@centos.org] On Behalf Of Karanbir Singh Sent: 21 June 2014 04:11 To: centos-devel@centos.org Subject: Re: [CentOS-devel] Cloud and VM Images
On 06/21/2014 03:10 AM, Karanbir Singh wrote:
hi,
I have just pushed a public build for a qcow2 image, this should be suiteable for any HVM environment. Please test as widely as possible.
root pw on that image is 'builder'
-- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc
On 06/21/2014 09:53 AM, Tim Bell wrote:
Boot on KVM with OpenStack went well.
Will the image contain cloud-init and a set of default repo lists enabled in future ?
Sam is going to work on the cloud-init stack and the deps under it, for the time being ( Mondays build ) - I will add in a script enough to get root key setup and disable all password logins.
( sort of what we have on the AMI's at the moment )
On Sat, Jun 21, 2014 at 03:10:39AM +0100, Karanbir Singh wrote:
hi,
I have just pushed a public build for a qcow2 image, this should be suiteable for any HVM environment. Please test as widely as possible.
Is that built using the centos.sh script?
As a general comment, although not required, virt-builder would prefer it if the image was xz-compressed. The reason is that it has to download the template and cache it in the user's $HOME, so a 960MB template is obviously both slow to download and takes a lot of space.
NB: Don't bother with qcow2's internal compression feature. It's a waste of space. xz is where it's at.
- nearly best in class compression
- real API (liblzma)
- preserves sparseness, important for raw format images
- virt-builder has a custom multithreaded unxz [1] -- it is sysconf(_SC_NPROCESSORS_ONLN) times faster than unxz
Rich.
[1] https://github.com/libguestfs/libguestfs/blob/master/builder/pxzcat-c.c
On 06/21/2014 09:45 AM, Richard W.M. Jones wrote:
Is that built using the centos.sh script?
slightly modified one - i will merge in the kickstarts used for the CentOS AMI's and the stuff we have in the cloud-instance-sig kickstarts into one.
xz is interesting, can certainly do one of those as well, but we want to have a qcow2 as well so it can be directly consumed as a url inside opennebula, openstack, eucalyptus and fog ( and its friends )
also, how and what exactly do we need to sign for virt-builder and where do i need to submit that ?
On Sat, Jun 21, 2014 at 05:20:18PM +0100, Karanbir Singh wrote:
On 06/21/2014 09:45 AM, Richard W.M. Jones wrote:
Is that built using the centos.sh script?
slightly modified one - i will merge in the kickstarts used for the CentOS AMI's and the stuff we have in the cloud-instance-sig kickstarts into one.
xz is interesting, can certainly do one of those as well, but we want to have a qcow2 as well so it can be directly consumed as a url inside opennebula, openstack, eucalyptus and fog ( and its friends )
Do these make a copy? In qemu there is support for directly using http as a block device .. unfortunately it doesn't work well. Any delay of over 60 seconds in the HTTP request causes I/O errors in the guest.
also, how and what exactly do we need to sign for virt-builder and where do i need to submit that ?
Create an index file like this example:
http://libguestfs.org/download/builder/index
The exact specification is here:
http://libguestfs.org/virt-builder.1.html#creating-and-signing-the-index-fil...
and there is a validation tool in Fedora 20+:
$ virt-index-validate ./index ./index validated OK
It would be good to call the guests "centos-*", eg. centos-7.0 etc. If you can have the index cover your existing CentOS 6.x cloud images, then I can delete the ones we are hosting. I'm not interested in hosting CentOS images long term if I can help it.
Sign the index file using:
gpg --clearsign --armor index
which creates 'index.asc'.
Upload index.asc to your site, and keep it up to date as new cloud images are created.
In the meantime, send your GPG public key, and the URL of the index.asc file (ideally a permanent URL) to: mailto:libguestfs@redhat.com
I will create a repo file which will be bundled with virt-builder upstream. The repo file will look something like this:
--------------- /etc/virt-builder/repos.d/centos.conf --- [centos] uri=http://centos.org/path/to/index.asc gpgkey=file:///etc/virt-builder/repos.d/centos.gpg ---------------------------------------------------------
The result will be that anyone on any distro can create CentOS cloud images just by doing:
$ virt-builder centos-7.0
Rich.