Re: [openstack-dev] [neutron][taas] neutron ovs-agent deletes taas flows

which have a reserved integer cookie value. https://review.openstack.org/#/c/257285/ https://review.openstack.org/#/c/257286/ Thanks, KAZ From: Soichi Shigeta <shigeta.soi...@jp.fujitsu.com> Subject: Re: [openstack-dev] [neutron][taas] neutron ovs-agent deletes taas flows Date: Thu

Re: [openstack-dev] [neutron][taas] neutron ovs-agent deletes taas flows

Thank you for your helpful comments. I'd like to update my proposal as follows: 1. Set an integer cookie value to taas flows. Maybe all "1" for short term tentative value. 2. Modify the cleanup logic in ovs-agent not to delete flows which have a reserved integer cookie value.

Re: [openstack-dev] [neutron][taas] neutron ovs-agent deletes taas flows

If you go this route, taas will have to implement flow recovery logic itself as well if you want hitless restarts. On Wed, Dec 16, 2015 at 5:28 PM, Soichi Shigeta < shigeta.soi...@jp.fujitsu.com> wrote: > > Thank you for your helpful comments. > > I'd like to update my proposal as follows: > >

Re: [openstack-dev] [neutron][taas] neutron ovs-agent deletes taas flows

Kyle Mestery wrote: >> o) Workaround: >> >> After a vm is deployed on a (re)started compute node, restart taas >> agent before creating a tap-service or tap-flow. >> That is, create taas flows after cleanup has been done. >> >> Note that cleanup will

Re: [openstack-dev] [neutron][taas] neutron ovs-agent deletes taas flows

Assaf Muller wrote: SFC are going to hit this issue as well. Really any out of tree Neutron project that extends the OVS agent and expects things to work :) Yes. SFC project is considered for l2 agent extensions mechanism, though we need to deliver in core first. AFAIK

Re: [openstack-dev] [neutron][taas] neutron ovs-agent deletes taas flows

o) An idea to fix: 1. Set "taas" stamp(*) to taas flows. 2. Modify the cleanup logic in ovs-agent not to delete entries stamped as "taas". * Maybe a static string. If we need to use a string which generated dynamically (e.g. uuid), API to interact

Re: [openstack-dev] [neutron][taas] neutron ovs-agent deletes taas flows

Soichi Shigeta wrote: Hi, We find a problem that neutron ovs-agent deletes taas flows. o) Problem description: Background: At Liberty, a bug fix to drop only old flows was merged to Neutron. When ovs-agent is restarted, the cleanup

Re: [openstack-dev] [neutron][taas] neutron ovs-agent deletes taas flows

SFC are going to hit this issue as well. Really any out of tree Neutron project that extends the OVS agent and expects things to work :) On Tue, Dec 15, 2015 at 9:30 AM, Ihar Hrachyshka wrote: > Soichi Shigeta wrote: > >> >> Hi, >> >> We

Re: [openstack-dev] [neutron][taas] neutron ovs-agent deletes taas flows

On Tue, Dec 15, 2015 at 9:11 AM, Assaf Muller wrote: > SFC are going to hit this issue as well. Really any out of tree > Neutron project that extends the OVS agent and expects things to work > :) > > Yes, this is the case. > On Tue, Dec 15, 2015 at 9:30 AM, Ihar Hrachyshka

Re: [openstack-dev] [neutron][taas] neutron ovs-agent deletes taas flows

Sorry, that I don't see this earlier. Yes, cookies have integer values, so we won't be able to set string there. May be we can have a reserved integer cookie value for a project like all "1". I won't support idea of modifying cleanup logic not to drop 0x0 cookies. During implementation of

[openstack-dev] [neutron][taas] neutron ovs-agent deletes taas flows

Hi, We find a problem that neutron ovs-agent deletes taas flows. o) Problem description: Background: At Liberty, a bug fix to drop only old flows was merged to Neutron. When ovs-agent is restarted, the cleanup logic drops flow entries unless they are stamped

Re: [openstack-dev] [neutron][taas] neutron ovs-agent deletes taas flows

hi, On Tue, Dec 8, 2015 at 6:52 PM, Soichi Shigeta wrote: > > Hi, > > We find a problem that neutron ovs-agent deletes taas flows. > > o) Problem description: > > Background: > At Liberty, a bug fix to drop only old flows was merged > to