Open Stack

Oh, I suppose it depends on what you mean by "ovs" in this context. The
Neutron OVS agent shouldn't trigger any flow losses, but restarted the OVS
vswitchd process may do that.

On Sat, Oct 7, 2017 at 2:31 AM, Sean Dague <sean at dague.net> wrote:

> On 10/06/2017 07:23 PM, Kevin Benton wrote:
>
>>  >The neutron story is mixed on accessable upgrade, because at least in
>> some cases, like ovs, upgrade might trigger a network tear down / rebuild
>> that generates an outage (though typically a pretty small one).
>>
>> This shouldn't happen. If it does it should be reported as a bug. All
>> existing OVS flows are left in place during agent initialization and we
>> don't get rid of the old ones until the agent finishes setting up the new
>> ones.
>>
>
> I thought it was literally a problem with the daemon restart where it is
> stateful and does a teardown / rebuild when started. I'd be happy to be
> wrong about that, but was told in the past that it was just an OVS
> limitation.
>
>
>         -Sean
>
> --
> Sean Dague
> http://dague.net
>
> __________________________________________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20171007/a90ccf3a/attachment.html>