← Back to team overview

openstack team mailing list archive

Re: Glance x-image-meta-type raw vs machine


Correct me if I am wrong, but I believe AMIs use IMG so that should be
another disk format a well (it would be the only one in the AMI appliance
format unless AWS changes it).  Is there enough variance in the virtual
disk and envelope formats over time that we want to include version
columns or would new versions just be another format choice.


On 1/10/11 10:59 AM, "John Purrier" <john@xxxxxxxxxxxxx> wrote:

>Jay, this makes a lot of sense. For disk formats I would suggest: VHD,
>VDI, VMDK, RAW, & QCOW2. For the appliance formats: OVF, OVA, & AMI.
>Conversion within Glance will need to be able to handle both disk image
>conversion and appliance format conversion.
>-----Original Message-----
>From: Jay Pipes [mailto:jaypipes@xxxxxxxxx]
>Sent: Monday, January 10, 2011 10:26 AM
>To: John Purrier
>Cc: Ewan Mellor; openstack@xxxxxxxxxxxxxxxxxxx
>Subject: Re: [Openstack] Glance x-image-meta-type raw vs machine
>And I think we need to come to an agreement on the terms used here...
>What is a "type" of virtual image? Do we mean a *disk* image format?
>Do we mean a *metadata envelope* type (OVF, AMI, etc)? Do we mean some
>"type" of system image or image part (kernel, ramdisk, etc)?
>What Glance is serving/registering is really called a *virtual
>appliance*, as described in this article:
>Change the Image model to have these following fields, instead of the
>existing "type" column:
>disk_format -- choice between ('VHD', 'VDI', 'VMDK')
>appliance_file_format -- choice between ('AMI','OVF')
>On Mon, Jan 10, 2011 at 11:11 AM, John Purrier <john@xxxxxxxxxxxxx> wrote:
>> My 2 cents... We need to define a transport-neutral specification that
>>allows us to encapsulate and copy/move a variety of virtual image
>>formats, this should be based on OVF. The envelope can contain both the
>>actual image as well as any required meta-data.
>> The image elements specified are very AMI specific, we should
>>generalize to be able to indicate the type of virtual image (i.e. AMI,
>>VHD, etc.). A test for POC can be a service that takes the data in the
>>OVF or what is stored in Glance to convert between formats. If we do
>>this correctly all of the required data will be available at the correct
>>point in the flow.
>> Don't know if this is directly applicable to the discussion point
>>below, but it is important that we get the fundamental
>>design/architecture concepts in place moving forward.
>> John
>> -----Original Message-----
>> From: openstack-bounces+john=openstack.org@xxxxxxxxxxxxxxxxxxx
>>[mailto:openstack-bounces+john=openstack.org@xxxxxxxxxxxxxxxxxxx] On
>>Behalf Of Jay Pipes
>> Sent: Monday, January 10, 2011 9:44 AM
>> To: Ewan Mellor
>> Cc: openstack@xxxxxxxxxxxxxxxxxxx
>> Subject: Re: [Openstack] Glance x-image-meta-type raw vs machine
>> On Sat, Jan 1, 2011 at 7:30 PM, Ewan Mellor <Ewan.Mellor@xxxxxxxxxxxxx>
>>> What is the intended semantics of the Glance x-image-meta-type header
>>> ³raw² vs ³machine²?
>> When we pulled the Image model from Nova into Glance, there was a
>> field "image_type" that was limited to the strings "raw", "machine",
>> "kernel", and "ramdisk".
>> I'm open to changing this or using something like a "format" field
>> (AMI vs OVF, etc..)
>> Thoughts?
>> -jay
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>Mailing list: https://launchpad.net/~openstack
>Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>Unsubscribe : https://launchpad.net/~openstack
>More help   : https://help.launchpad.net/ListHelp

Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use of the
individual or entity to which this message is addressed, and unless otherwise
expressly indicated, is confidential and privileged information of Rackspace. 
Any dissemination, distribution or copying of the enclosed material is prohibited.
If you receive this transmission in error, please notify us immediately by e-mail
at abuse@xxxxxxxxxxxxx, and delete the original message. 
Your cooperation is appreciated.

Follow ups