<div dir="ltr">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.)<div>
<br></div><div style>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.</div></div><div class="gmail_extra"><br clear="all"><div>
Mark Atwood <<a href="mailto:mark.atwood@hp.com" target="_blank">mark.atwood@hp.com</a>><br>
Director of Open Source Evangelism for HP Cloud Services<br>+1-206-473-7118<br></div>
<br><br><div class="gmail_quote">On Wed, Jan 30, 2013 at 2:55 AM, Daniel P. Berrange <span dir="ltr"><<a href="mailto:berrange@redhat.com" target="_blank">berrange@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Some apps have a need to be able to obtain ISO filesystem headers from<br>
images stored in glance. Now obviously they can just download the image<br>
(or part of it) and run 'isoinfo' on it, but this is really horrifically<br>
inefficient/wasteful of bandwidth. It would be desirable for glance to<br>
have explicit support for this in some way.<br>
<br>
I've written a short wiki page describing one approach, which is to<br>
make glance extract the data upon upload of an ISO and store it in<br>
some well-defined metadata properties against the image.<br>
<br>
<a href="http://wiki.openstack.org/GlanceISOHeaders" target="_blank">http://wiki.openstack.org/GlanceISOHeaders</a><br>
<a href="https://blueprints.launchpad.net/glance/+spec/iso-image-metadata" target="_blank">https://blueprints.launchpad.net/glance/+spec/iso-image-metadata</a><br>
<br>
A completely different approach we be to ignore metadata properties<br>
and add an explicit API to glance which would extract it on-demand,<br>
but I feel this is a needlessly large amount of work & less convenient<br>
and flexible than simply using existing metadata properties.<br>
<br>
Regards,<br>
Daniel<br>
<span class="HOEnZb"><font color="#888888">--<br>
|: <a href="http://berrange.com" target="_blank">http://berrange.com</a> -o- <a href="http://www.flickr.com/photos/dberrange/" target="_blank">http://www.flickr.com/photos/dberrange/</a> :|<br>
|: <a href="http://libvirt.org" target="_blank">http://libvirt.org</a> -o- <a href="http://virt-manager.org" target="_blank">http://virt-manager.org</a> :|<br>
|: <a href="http://autobuild.org" target="_blank">http://autobuild.org</a> -o- <a href="http://search.cpan.org/~danberr/" target="_blank">http://search.cpan.org/~danberr/</a> :|<br>
|: <a href="http://entangle-photo.org" target="_blank">http://entangle-photo.org</a> -o- <a href="http://live.gnome.org/gtk-vnc" target="_blank">http://live.gnome.org/gtk-vnc</a> :|<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</font></span></blockquote></div><br></div>