[Openstack-operators] Neutron database upgrade kilo-liberty and parallel Alembic migration branches

Ihar Hrachyshka ihrachys at redhat.com
Wed Jun 1 12:58:09 UTC 2016


> On 01 Jun 2016, at 14:49, Saverio Proto <zioproto at gmail.com> wrote:
> 
> Hello,
> 
> reading this documentation page:
> 
> http://docs.openstack.org/mitaka/networking-guide/migration-neutron-database.html
> 
> I dont get what means having two parallel migration branches.
> 
> Do you have to choose one of the branches ? If yes how ?
> 
> 
> Or it just means that some operations can be safely run when Neutron
> Server API is running, (e.g.
> neutron-db-manage upgrade --expand)
> 
> while other operations (e.g. neutron-db-manage upgrade --contract)
> require the Neutron Server to be stopped ??
> 

The latter. If you think the documentation is deficient, please propose a patch that would clarify that.

> Anyone has some upgrade notes to share that can clarify the procedure ?
> 
> Thank you
> 
> Saverio
> 
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators




More information about the OpenStack-operators mailing list