<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 04/01/2012 11:15 AM, Lorin Hochstein
      wrote:<br>
    </div>
    <blockquote
      cite="mid:93CE7620-CEEB-484B-A3D6-F17BCD9049A6@nimbisservices.com"
      type="cite">
      <div apple-content-edited="true"><br
          class="Apple-interchange-newline">
      </div>
      <br>
      <div>
        <div>On Mar 29, 2012, at 12:40 PM, Daniel P. Berrange wrote:</div>
        <br class="Apple-interchange-newline">
        <blockquote type="cite">
          <div>On Wed, Mar 28, 2012 at 04:41:28PM -0400, Lorin Hochstein
            wrote:<br>
            <blockquote type="cite">All:<br>
            </blockquote>
            <blockquote type="cite"><br>
            </blockquote>
            <blockquote type="cite">Given that I have a qcow2 image from
              somewhere (e.g., downloaded<br>
            </blockquote>
            <blockquote type="cite">it from a <a moz-do-not-send="true"
                href="http://uec-images.ubuntu.com">uec-images.ubuntu.com</a>,
              created one from a raw image using<br>
            </blockquote>
            <blockquote type="cite">qemu-img) that i want to add to
              glance:<br>
            </blockquote>
            <blockquote type="cite"><br>
            </blockquote>
            <blockquote type="cite">1. How can I tell whether it's an
              "ovf" or "bare" container format?<br>
            </blockquote>
            <br>
            You are mixing up terminology here. Disk image formats are
            things like<br>
            raw, qcow2, vmdk, etc.<br>
            <br>
            OVF refers to the format of a metadata file provided
            alongside the<br>
            disk image, which describes various requirements for running
            the<br>
            image.<br>
            <br>
            The two are not tied together at all, merely complementary
            to<br>
            each other.<br>
            <br>
          </div>
        </blockquote>
        <div><br>
        </div>
        <div>Thanks, that clears things up. I was confused by this
          language, which sounded to me like the metadata was embedded
          in the disk image file:</div>
        <div><br>
        </div>
        <div><a moz-do-not-send="true"
            href="http://glance.openstack.org/formats.html">http://glance.openstack.org/formats.html</a></div>
        <div><br>
        </div>
        <div>"The container format refers to whether the virtual machine
          image is in a file format that also contains metadata about
          the actual virtual machine."</div>
        <div><br>
        </div>
        <div>In addition, the docs have examples like this, which
          clearly aren't meaningful:</div>
        <div><a moz-do-not-send="true"
href="http://glance.openstack.org/glance.html#important-information-about-uploading-images">http://glance.openstack.org/glance.html#important-information-about-uploading-images</a></div>
      </div>
    </blockquote>
    <br>
    Just to add to the confusion  the OVF can contain both the metadata
    file and the disk image file in a single archived file.  <br>
    <br>
    "An OVF package consists of several files, placed in one directory.
    A one-file alternative is the OVA package, which is a TAR file with
    the OVF directory inside."<br>
    <br>
<a class="moz-txt-link-freetext" href="http://en.wikipedia.org/wiki/Open_Virtualization_Format#Technical_description">http://en.wikipedia.org/wiki/Open_Virtualization_Format#Technical_description</a><br>
    <br>
    <br>
    I think that what you are reading above refers to the single file
    alternative.<br>
    <blockquote
      cite="mid:93CE7620-CEEB-484B-A3D6-F17BCD9049A6@nimbisservices.com"
      type="cite">
      <div>
        <div><br>
        </div>
        <div><br>
        </div>
        <div>
          <pre style="overflow: auto; font-family: Consolas, 'Deja Vu Sans Mono', 'Bitstream Vera Sans Mono', monospace; font-size: 0.95em; letter-spacing: normal; line-height: 15px; padding: 0.5em; border: 1px solid rgb(204, 204, 204); background-color: rgb(248, 248, 248); color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; orphans: 2; text-align: left; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">$> glance add name="My Image" is_public=true \
     container_format=ovf disk_format=raw < /tmp/images/myimage.iso</pre>
          <div><br>
          </div>
        </div>
        <div>I'll propose a change to the docs for that.</div>
        <div><br>
        </div>
        <blockquote type="cite">
          <div><font class="Apple-style-span" color="#000000"><br>
            </font>
            <blockquote type="cite">Whenever I add a qcow2 image to
              glance, I always choose "ovf",<br>
            </blockquote>
            <blockquote type="cite">even though it's probably "bare",
              because I saw an example<br>
            </blockquote>
            <blockquote type="cite">somewhere, and it just works, so I
              keep doing it. But I don't<br>
            </blockquote>
            <blockquote type="cite">know how to inspect a binary file to
              determine what its container<br>
            </blockquote>
            <blockquote type="cite">is (if "file image.qcow2" says it's
              a QEMU QCOW2 Image (v2), does<br>
            </blockquote>
            <blockquote type="cite">that mean it's "bare"?). In
              particular, why does the user need to<br>
            </blockquote>
            <blockquote type="cite">specify this information?<br>
            </blockquote>
            <br>
            If you simply have a single  someimage.qcow2 file, then you
            simply<br>
            have a disk image. Thus there is no OVF metadata involved at
            all.<br>
            <br>
            eg, this is the (qcow2) disk image:<br>
            <br>
             <a moz-do-not-send="true"
href="http://uec-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64-disk1.img">http://uec-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64-disk1.img</a><br>
            <br>
            While this is an OVF metadata file that optionally
            accompanies the disk image<br>
            <br>
             <a moz-do-not-send="true"
href="http://uec-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64.ovf">http://uec-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64.ovf</a><br>
            <br>
          </div>
        </blockquote>
        <div><br>
        </div>
        <div>Gotcha.</div>
        <div><br>
        </div>
        <div><br>
        </div>
        <div>It's not clear to me how you would specify the OVF metadata
          file when adding an image file to glance.</div>
        <div><br>
        </div>
      </div>
      <div><br>
      </div>
      <div>
        <div style="word-wrap: break-word; -webkit-nbsp-mode: space;
          -webkit-line-break: after-white-space; ">
          <div style="word-wrap: break-word; -webkit-nbsp-mode: space;
            -webkit-line-break: after-white-space; ">
            <div>Take care,</div>
            <div><br>
            </div>
            <div>Lorin</div>
            <div>--</div>
            <div>Lorin Hochstein</div>
            <div>Lead Architect - Cloud Services</div>
            <div>Nimbis Services, Inc.</div>
            <div><a moz-do-not-send="true"
                href="https://www.nimbisservices.com/">www.nimbisservices.com</a></div>
            <div><br>
            </div>
          </div>
          <br class="Apple-interchange-newline">
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Mailing list: <a class="moz-txt-link-freetext" href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a>
Post to     : <a class="moz-txt-link-abbreviated" href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>
Unsubscribe : <a class="moz-txt-link-freetext" href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a>
More help   : <a class="moz-txt-link-freetext" href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a>
</pre>
    </blockquote>
    <br>
    <br>
  </body>
</html>