openstack team mailing list archive

[Lorin Hochstein <lorin@xxxxxxxxxxxxxxxxxx>]

On Mar 29, 2012, at 12:00 PM, Scott Moser wrote:

> On Wed, 28 Mar 2012, Lorin Hochstein wrote:
> 
>> All:
>> 
>> Given that I have a qcow2 image from somewhere (e.g., downloaded it from a uec-images.ubuntu.com, created one from a raw image using qemu-img) that i want to add to glance:
>> 
>> 1. How can I tell whether it's an "ovf" or "bare" container format?
>> 2. Why does it matter?
> 
> I dont know either, but I do know what you want, taken from stack.sh in
> devstack, which should probably be updated to not use '-A'
> glance add -A "$TOKEN" \
>   name="${IMAGE_NAME%.img}" is_public=true
>   container_format=ami disk_format=ami <${IMAGE}
> 
> You can also add "ramdisk_id=...." and "kernel_id=...." tags in the upload
> if you want that.
> 
> Note, you can do this with the Ubuntu cloud-images, and that is the best
> way to put images for openstack into glance.
> $ url=https://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64-disk1.img
> $ wget "$url" -O "${url##*/}"
> $ glance add name=${url##*/} is_public=true container_format=ami \
>      disk_format=ami < "${url##*/}"
> 

Isn't that a qcow2 image? Why does devstack use "container_format=ami disk_format=ami" and not "container_format=bare disk_format=qcow2"?



Take care,

Lorin
--
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com