<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Hi Mark,<br>
      <br>
      <br>
      I was thinking at the OVF container format first since as far I
      know, it does support metadatas.<br>
      <br>
      <br>
      Thank's,<br>
      <br>
      <pre class="moz-signature" cols="72">Emilien Macchi
----------------------------------------------------
# OpenStack Engineer
// eNovance Inc.              <a class="moz-txt-link-freetext" href="http://enovance.com">http://enovance.com</a>
// ✉ <a class="moz-txt-link-abbreviated" href="mailto:emilien@enovance.com">emilien@enovance.com</a>     ☎ +33 (0)1 49 70 99 80
// 10 rue de la Victoire 75009 Paris</pre>
      On 08/14/2013 06:34 PM, Mark Washenberger wrote:<br>
    </div>
    <blockquote
cite="mid:CAJyP2C9WZD+Er1Z6QEQVCYakV18wNWDv1oRFr1+6wdnX_K8LgQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">Lets dig into this a bit more so that I can
        understand it.
        <div><br>
        </div>
        <div>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?</div>
      </div>
      <div class="gmail_extra"><br>
        <br>
        <div class="gmail_quote">On Wed, Aug 14, 2013 at 8:36 AM,
          Emilien Macchi <span dir="ltr"><<a moz-do-not-send="true"
              href="mailto:emilien.macchi@enovance.com" target="_blank">emilien.macchi@enovance.com</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div text="#000000" bgcolor="#FFFFFF"> Hi,<br>
              <br>
              <br>
              I would like to discuss here about two blueprint proposal
              (maybe could I merge them into one if you prefer) :<br>
              <br>
              <a moz-do-not-send="true"
href="https://blueprints.launchpad.net/glance/+spec/api-v2-export-properties"
                target="_blank">https://blueprints.launchpad.net/glance/+spec/api-v2-export-properties</a><br>
              <a moz-do-not-send="true"
href="https://blueprints.launchpad.net/glance/+spec/api-v2-import-properties"
                target="_blank">https://blueprints.launchpad.net/glance/+spec/api-v2-import-properties</a><br>
              <br>
              <b>Use case</b> :<br>
              I would like to set specific properties to an image which
              could represent a signature, and useful for licensing
              requirements for example.<br>
              To do that, I should be able to export an image with user
              properties included.
              <p>Then, a user could reuse the exported image in the
                public cloud, and Glance will be aware about its
                properties.<br>
                Obviously, we need the import / export feature.<br>
              </p>
              <p>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.<br>
              </p>
              <p><br>
                Let me know if you have any thoughts and if the
                blueprint is valuable.<br>
                <br>
              </p>
              <p>Regards,<span class="HOEnZb"><font color="#888888"><br>
                  </font></span></p>
              <span class="HOEnZb"><font color="#888888">
                  <pre cols="72">-- 
Emilien Macchi
----------------------------------------------------
# OpenStack Engineer
// eNovance Inc.              <a moz-do-not-send="true" href="http://enovance.com" target="_blank">http://enovance.com</a>
// ✉ <a moz-do-not-send="true" href="mailto:emilien@enovance.com" target="_blank">emilien@enovance.com</a>     ☎ <a moz-do-not-send="true" href="tel:%2B33%20%280%291%2049%2070%2099%2080" value="+33149709980" target="_blank">+33 (0)1 49 70 99 80</a>
// 10 rue de la Victoire 75009 Paris</pre>
                </font></span></div>
            <br>
            _______________________________________________<br>
            OpenStack-dev mailing list<br>
            <a moz-do-not-send="true"
              href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
            <a moz-do-not-send="true"
              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>
            <br>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>