<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Did you mean EBS? I thought it was
      generally hard to get the same kind of performance from block
      storage that local ephemeral storage provides but perhaps Amazon
      has found a way. Life would certainly be much simpler with a
      single ephemeral backend. Storage pools
      (<a class="moz-txt-link-freetext" href="https://blueprints.launchpad.net/nova/+spec/use-libvirt-storage-pools">https://blueprints.launchpad.net/nova/+spec/use-libvirt-storage-pools</a>)
      should provide some of the same benefits.<br>
      <br>
      On 10/21/2014 02:54 PM, Preston L. Bannister wrote:<br>
    </div>
    <blockquote
cite="mid:CA+R0Njb_AzLyoTLSZDGmavv9ZNZ8d4WmcUc-qndgWETf=dNUnA@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <div dir="ltr">As a side-note, the new AWS flavors seem to
        indicate that the Amazon infrastructure is moving to all ECS
        volumes (and all flash, possibly), both ephemeral and not. This
        makes sense, as fewer code paths and less interoperability
        complexity is a good thing.
        <div><br>
        </div>
        <div>That the same balance of concerns should apply in
          OpenStack, seems likely.</div>
        <div><br>
        </div>
        <div><br>
        </div>
        <div><br>
        </div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Tue, Oct 21, 2014 at 7:59 AM, Dan
          Genin <span dir="ltr"><<a moz-do-not-send="true"
              href="mailto:daniel.genin@jhuapl.edu" target="_blank">daniel.genin@jhuapl.edu</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
            <br>
            I would like to add to DevStack the ability to stand up Nova
            with LVM ephemeral<br>
            storage. Below is a draft of the blueprint describing the
            proposed feature.<br>
            <br>
            Suggestions on architecture, implementation and the
            blueprint in general are very<br>
            welcome.<br>
            <br>
            Best,<br>
            Dan<br>
            <br>
            ========================<br>
            Enable LVM ephemeral storage for Nova<br>
            ========================<br>
            <br>
            Currently DevStack supports only file based ephemeral
            storage for Nova, e.g.,<br>
            raw and qcow2. This is an obstacle to Tempest testing of
            Nova with LVM ephemeral<br>
            storage, which in the past has been inadvertantly broken<br>
            (see for example, <a moz-do-not-send="true"
              href="https://bugs.launchpad.net/nova/+bug/1373962"
              target="_blank">https://bugs.launchpad.net/nova/+bug/1373962</a>),
            and to Tempest<br>
            testing of new features based on LVM ephemeral storage, such
            as LVM ephemeral<br>
            storage encryption.<br>
            <br>
            To enable Nova to come up with LVM ephemeral storage it must
            be provided a<br>
            volume group. Based on an initial discussion with Dean
            Troyer, this is best<br>
            achieved by creating a single volume group for all services
            that potentially<br>
            need LVM storage; at the moment these are Nova and Cinder.<br>
            <br>
            Implementation of this feature will:<br>
            <br>
             * move code in lib/cinder/cinder_backends/lvm to lib/lvm
            with appropriate<br>
               modifications<br>
            <br>
             * rename the Cinder volume group to something generic,
            e.g., devstack-vg<br>
            <br>
             * modify the Cinder initialization and cleanup code
            appropriately to use<br>
               the new volume group<br>
            <br>
             * initialize the volume group in stack.sh, shortly before
            services are<br>
               launched<br>
            <br>
             * cleanup the volume group in unstack.sh after the services
            have been<br>
               shutdown<br>
            <br>
            The question of how large to make the common Nova-Cinder
            volume group in order<br>
            to enable LVM ephemeral Tempest testing will have to be
            explored. Although,<br>
            given the tiny instance disks used in Nova Tempest tests,
            the current<br>
            Cinder volume group size may already be adequate.<br>
            <br>
            No new configuration options will be necessary, assuming the
            volume group size<br>
            will not be made configurable.<br>
            <br>
            <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>