Open Stack

We did this for our I to J move. Control nodes first, setting the nova
compat flag, then compute nodes, then removing the flag. Things worked
along the way but  when the compat flag was set live-migration was
disabled (by nova). Our larger concerns were dealing with a clustered DB
that was being upgraded from I to J.

I do not recall any specific neutron server/agent issues.

On 3/4/15, 1:56 PM, "Assaf Muller" <amuller at redhat.com> wrote:

>Hello everyone,
>
>An issue came up recently:
>http://lists.openstack.org/pipermail/openstack-dev/2015-March/058280.html
>
>Where a recent Kilo patch made non-backwards compatible to the RPC
>interface
>between the Neutron server and its agents. I'm trying to figure out how
>much
>of an issue that really is.
>
>The question is: Does anyone have any experience with performing a
>'rolling upgrade'
>for Neutron, specifically, upgrading the Neutron API server(s) first, and
>upgrading
>Neutron agents later? Has anyone performed this from Icehouse to Juno
>successfully?
>Would this typically work across the board for other services as well?
>
>Thank you.
>
>
>Assaf Muller, Cloud Networking Engineer
>Red Hat
>
>_______________________________________________
>OpenStack-operators mailing list
>OpenStack-operators at lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.