On Thu, Jan 24, 2013 at 11:19:16AM -0500, Bill Nottingham wrote: > Matthew Miller (mattdm@xxxxxxxxxxxxxxxxx) said: > > On Wed, Jan 23, 2013 at 04:38:13PM -0500, Bill Nottingham wrote: > > > > == Detailed description == > > > > * New images that can be used in other cloud deployments (such as > > > > OpenStack, CloudStack, or Eucalyptus) will be produced. They will be in a > > > > qcow2 format and lack the EC2-specific customization. Images for this feature > > > > would ideally work for all cloud deployments and there will be i686 and x86_64 > > > > versions of both image types. In total and "image drop" will have 4 images: 2 > > > > arches for 2 different types (EC2, not-EC2). > > > Will these images also be usable directly as virt image templates in local > > > virtualization tools such as virt-manager & Boxes? > > > > Yes. They have cloud-init enabled, which will look for a metadata service > > and (probably) not find one and then eventually time out and get you to a > > login prompt. To avoid that, you can boot with "ds=nocloud' > > > > (Apparently there's a RHEVm and vSphere datasource too but I haven't tested > > that.) > > Have the boxes and libvirt people investigated writing a minimal cloud-init > compatibile data-source? First time I hear of cloud-init, so as far as I know no one looked into Boxes integration (though this could be nice). Christophe
Attachment:
pgpHDEPd2mvQf.pgp
Description: PGP signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
