[openstack-dev] [Glance] Blueprint proposal - Import / Export images with user properties

Emilien Macchi emilien.macchi at enovance.com
Wed Aug 14 17:09:07 UTC 2013


Hi Mark,


I was thinking at the OVF container format first since as far I know, it
does support metadatas.


Thank's,

Emilien Macchi
----------------------------------------------------
# OpenStack Engineer
// eNovance Inc.              http://enovance.com
// ? emilien at enovance.com     ? +33 (0)1 49 70 99 80
// 10 rue de la Victoire 75009 Paris

On 08/14/2013 06:34 PM, Mark Washenberger wrote:
> Lets dig into this a bit more so that I can understand it.
>
> Given that we have properties that we want to export with an image,
> where would those properties be stored? Somewhere in the image data
> itself? I believe some image formats support metadata, but I can't
> imagine all of them would. Is there a specific format you're thinking
> of using?
>
>
> On Wed, Aug 14, 2013 at 8:36 AM, Emilien Macchi
> <emilien.macchi at enovance.com <mailto:emilien.macchi at enovance.com>> wrote:
>
>     Hi,
>
>
>     I would like to discuss here about two blueprint proposal (maybe
>     could I merge them into one if you prefer) :
>
>     https://blueprints.launchpad.net/glance/+spec/api-v2-export-properties
>     https://blueprints.launchpad.net/glance/+spec/api-v2-import-properties
>
>     *Use case* :
>     I would like to set specific properties to an image which could
>     represent a signature, and useful for licensing requirements for
>     example.
>     To do that, I should be able to export an image with user
>     properties included.
>
>     Then, a user could reuse the exported image in the public cloud,
>     and Glance will be aware about its properties.
>     Obviously, we need the import / export feature.
>
>     The idea here is to be able to identify an image after cloning or
>     whatever with a property field. Of course, the user could break it
>     in editing the image manually, but I consider he / she won't.
>
>
>     Let me know if you have any thoughts and if the blueprint is valuable.
>
>     Regards,
>
>     -- 
>     Emilien Macchi
>     ----------------------------------------------------
>     # OpenStack Engineer
>     // eNovance Inc.              http://enovance.com
>     // ? emilien at enovance.com <mailto:emilien at enovance.com>     ? +33 (0)1 49 70 99 80 <tel:%2B33%20%280%291%2049%2070%2099%2080>
>     // 10 rue de la Victoire 75009 Paris
>
>
>     _______________________________________________
>     OpenStack-dev mailing list
>     OpenStack-dev at lists.openstack.org
>     <mailto: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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130814/ddc543b3/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 553 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130814/ddc543b3/attachment.pgp>


More information about the OpenStack-dev mailing list