the cloud images for the mirrors

[Dennis Gilmore]

On Wed, 2 Jan 2013 15:13:04 -0500
Bill Nottingham <notting at redhat.com> wrote:

> Matthew Miller (mattdm at fedoraproject.org) said: 
> > So, assuming we have a Go at the meeting tomorrow, what do we need
> > to get the cloud images onto the mirrors?
> > 
> > As we discussed before (in the cloud sig), we'd like both
> > xz-compressed raw and non-compressed qcow2 images. This seems to
> > cover primary cases of something generic that can be translated to
> > many formats and something which can be used immediately.
> > 
> > I think what we want is images built from a non-ec2-specific
> > kickstart from
> > http://git.fedorahosted.org/cgit/cloud-kickstarts.git/tree/generic. 

Really this should have been added at Alpha or Beta not at the last
second. Im extremely hesitant to produce and ship anything 

> > There are several options there, and I *think* the "-cloud" one
> > makes most sense. It has cloud-init and should work in a number of
> > different cloud providers with different metadata services. Unlike
> > the ec2 images, these use grub2 by default so should boot with
> > anything (e.g., KVM) which will just boot an image. In any case,
> > I've tested these to some degree, and although with some big
> > changes at the last minute it's not certain, I don't think there's
> > any brown-paper bag mistakes. It'd be good to spin up the official
> > image builds in the Fedora internal cloud, of course.
> > 
> > Then, those images should _go_ somewhere -- possibly
> > "releases/18/Cloud/", or else "releases/18/Fedora/[arch]/cloud".
> 
> Hm, they're not *really* cloud specific, though - they could be used
> in virt-manager/boxes, or even (I suppose) splatted onto a raw disk.
> Is there a  more generic name that could be used?

I would follow the same naming as we do for arm disk images
releases/18/Images/<arch>/

Dennis