[openstack-dev] [neutron][upgrades] Potential issues when performing Neutron upgrades

Kevin Benton blak111 at gmail.com
Mon Jul 13 21:08:44 UTC 2015

Thanks for the info. So the equivalent in neutron would be if we just
ensure backward compatible AMQP APIs, right?

On Mon, Jul 13, 2015 at 7:33 AM, Russell Bryant <rbryant at redhat.com> wrote:

> On 07/13/2015 04:09 AM, Kevin Benton wrote:
> >>because you won't have to run Neutron agents on compute nodes anymore.
> >
> > How will upgrades work for OVN?
> We haven't written anything down yet, but here's what I expect.
> Right now we're still changing the db schema however is needed without
> messing with versioning.  As we get to "production ready", I expect
> we'll start being strict about only making backwards compatible ovsdb
> schema changes to make upgrades easier.
> There are 2 central components - ovn-northd and ovsdb-server - that
> would be upgraded first, which I would expect to be done at the same
> time as upgrading your Neutron control plane.  As long as any ovsdb
> schema changes are backwards compatible, you could do rolling-upgrades
> of ovn-controller on compute or network nodes.
> --
> Russell Bryant
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Kevin Benton
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150713/cc288e90/attachment.html>

More information about the OpenStack-dev mailing list