<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <br>
    <br>
    <div class="moz-cite-prefix">Le 18/03/2016 09:48, Dulko, Michal a
      écrit :<br>
    </div>
    <blockquote cite="mid:1458290921.19704.0.camel@intel.com"
      type="cite">
      <pre wrap="">On Fri, 2016-03-18 at 08:27 +0000, Tan, Lin wrote:
</pre>
      <blockquote type="cite">
        <pre wrap="">Hi,

I noticed that expand/migrate/contract was revert in <a class="moz-txt-link-freetext" href="https://review.openstack.org/#/c/239922/">https://review.openstack.org/#/c/239922/</a>
There is a new CMD 'online_data_migrations' was introduced to Nova and some data-migration scripts have been added.
So I wonder will Nova keep expand the DB schema at beginning of live upgrade like before Or Nova have some new ways to handle DB Schema change?
The upgrade doc was not update for a long time.... <a class="moz-txt-link-freetext" href="http://docs.openstack.org/developer/nova/upgrade.html">http://docs.openstack.org/developer/nova/upgrade.html</a>

Thanks a lot.

Best Regards,

Tan
</pre>
      </blockquote>
      <pre wrap="">
[1] will help you understand current way of doing live schema upgrades.

[1] <a class="moz-txt-link-freetext" href="http://www.danplanet.com/blog/2015/10/07/upgrades-in-nova-database-migrations/">http://www.danplanet.com/blog/2015/10/07/upgrades-in-nova-database-migrations/</a></pre>
    </blockquote>
    <br>
    To be clear, that's mentioned in the (in progress) release notes for
    Mitaka
    <a class="moz-txt-link-freetext" href="http://docs.openstack.org/releasenotes/nova/unreleased.html#new-features">http://docs.openstack.org/releasenotes/nova/unreleased.html#new-features</a><br>
    <br>
    "Added a <cite>nova-manage db online_data_migrations</cite> command
    for forcing online data migrations, which will run all registered
    migrations for the release, instead of there being a separate
    command for each logical data migration. Operators need to make sure
    all data is migrated before upgrading to the next release, and the
    new command provides a unified interface for doing it."<br>
    <br>
    HTH,<br>
    -Sylvain<br>
    <blockquote cite="mid:1458290921.19704.0.camel@intel.com"
      type="cite">
      <pre wrap="">
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</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>