[openstack-dev] RFC: Recording/providing ISO image headers in glance

Mark Washenberger mark.washenberger at markwash.net
Mon Apr 8 17:59:32 UTC 2013

Sorry I missed this earlier, but, couldn't you just run "isoinfo" on
the image data before you upload it to Glance, and add the properties
you care about during image creation? We could document those property
names and values (and maybe even validate them) to make sure they
retain their canonical meaning.

Otherwise, adding a hook to "inspect image and add relevant
properties" doesn't really have a good place to fit into Glance at the
moment, IMO.

On Fri, Apr 5, 2013 at 3:04 PM, Mark Atwood <mark.atwood at hp.com> wrote:
> Instead of just for ISO9660, I know that other filesystem images and also
> various VM storage images also define various metadata.  (I know that I've
> read and written metadata for Virtual Box images using the GUI tool, for
> example.)
> I think it makes sense to do this in such a way that Glance can make all
> these metadatas from all image formats discoverable and displayable.
> Mark Atwood <mark.atwood at hp.com>
> Director of Open Source Evangelism for HP Cloud Services
> +1-206-473-7118
> On Wed, Jan 30, 2013 at 2:55 AM, Daniel P. Berrange <berrange at redhat.com>
> wrote:
>> Some apps have a need to be able to obtain ISO filesystem headers from
>> images stored in glance. Now obviously they can just download the image
>> (or part of it) and run 'isoinfo' on it, but this is really horrifically
>> inefficient/wasteful of bandwidth. It would be desirable for glance to
>> have explicit support for this in some way.
>> I've written a short wiki page describing one approach, which is to
>> make glance extract the data upon upload of an ISO and store it in
>> some well-defined metadata properties against the image.
>>     http://wiki.openstack.org/GlanceISOHeaders
>>     https://blueprints.launchpad.net/glance/+spec/iso-image-metadata
>> A completely different approach we be to ignore metadata properties
>> and add an explicit API to glance which would extract it on-demand,
>> but I feel this is a needlessly large amount of work & less convenient
>> and flexible than simply using existing metadata properties.
>> Regards,
>> Daniel
>> --
>> |: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/
>> :|
>> |: http://libvirt.org              -o-             http://virt-manager.org
>> :|
>> |: http://autobuild.org       -o-         http://search.cpan.org/~danberr/
>> :|
>> |: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc
>> :|
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

More information about the OpenStack-dev mailing list