<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 25 May 2015 at 09:46, Mike Bayer <span dir="ltr"><<a href="mailto:mbayer@redhat.com" target="_blank">mbayer@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div bgcolor="#FFFFFF" text="#000000"><span class="">
    <br>
    <br>
    <div>On 5/25/15 12:34 PM, Armando M. wrote:<br>
    </div>
    <blockquote type="cite">
      <div dir="ltr"><br>
        <div>
          <div><br>
            <br>
          </div>
        </div>
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div> </div>
            <div>One thing I would like to point out is that in this
              cycle we'll be working extensively in this area to make
              the very task you are working on easier to deal with, and
              better documented. This will fall under the umbrella of
              the blueprint [1].</div>
            <div><br>
            </div>
            <div>HTH</div>
            <div>Armando</div>
            <div><br>
            </div>
            <div>[1] <a href="https://blueprints.launchpad.net/neutron/+spec/core-vendor-decomposition" target="_blank">https://blueprints.launchpad.net/neutron/+spec/core-vendor-decomposition</a></div>
          </div>
        </div>
      </div>
    </blockquote>
    <br></span>
    took a look at <a href="https://review.openstack.org/#/c/134680/17" target="_blank">https://review.openstack.org/#/c/134680/17</a>, can I
    have some clarification on what "currently alembic requires extra
    work to support multiple db migration paths onto a single database"?
      Want to make sure you're aware that Alembic supports this fully
    (and my job has been to try to get Openstack projects to notice);
    see
<a href="http://alembic.readthedocs.org/en/latest/branches.html#working-with-multiple-bases" target="_blank">http://alembic.readthedocs.org/en/latest/branches.html#working-with-multiple-bases</a>.<span class=""><br>     </span></div></blockquote><div><br></div><div>The wording might be confusing, my bad.</div><div><br></div><div>What I intended there was that neutron's logic to handle alembic migrations required some work in order to simplify the support of out-of-tree DB migrations. Past experiences, like the one that triggered this thread, have shown that we can improve neutron's tooling (neutron-db-manage), as well as documentation.</div><div><br></div><div>Cheers,</div><div>Armando</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000"><span class=""> <br></span></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000"><span class="">
    <br>
    <blockquote type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div><br>
            </div>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
              <div>
                <div>
                  <br>
                  <br>
                  <br>
                  <br>
__________________________________________________________________________<br>
                  OpenStack Development Mailing List (not for usage
                  questions)<br>
                  Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</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>
                </div>
              </div>
            </blockquote>
          </div>
          <br>
        </div>
      </div>
      <br>
      <fieldset></fieldset>
      <br>
      <pre>__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<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>
</pre>
    </blockquote>
    <br>
  </span></div>

<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</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>
<br></blockquote></div><br></div></div>