On Fri, Oct 31, 2014 at 3:28 PM, Ben Nemec wrote:
> On 10/29/2014 10:17 AM, Kyle Mestery wrote:
> > On Wed, Oct 29, 2014 at 7:25 AM, Hly wrote:
> >>
> >>
> >> Sent from my iPad
> >>
> >> On 2014-10-29, at 下午8:01, Robert van Leeuwen <
> robert.vanleeu...@spilgames.com> wrote:
> >>
> > I find
ray flows.
Regards,
Erik
From: Germy Lure [mailto:germy.l...@gmail.com<mailto:germy.l...@gmail.com>]
Sent: den 5 november 2014 10:46
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron][TripleO] Clear all flows when ovs agent
start? why and ho
hod so we can avoid
>>> network downtime and stray flows.
>>>
>>>
>>>
>>> Regards,
>>>
>>> Erik
>>>
>>>
>>>
>>>
>>>
>>> *From:* Germy Lure [mailto:germy.l...@gmail.com]
>>&g
> Erik
>>>
>>>
>>>
>>>
>>>
>>> *From:* Germy Lure [mailto:germy.l...@gmail.com]
>>> *Sent:* den 5 november 2014 10:46
>>> *To:* OpenStack Development Mailing List (not for usage questions)
>>> *Subject:* Re: [openst
MHO we need flow synchronization method so we can avoid
>> network downtime and stray flows.
>>
>>
>>
>> Regards,
>>
>> Erik
>>
>>
>>
>>
>>
>> *From:* Germy Lure [mailto:germy.l...@gmail.com]
>> *Sent:* den 5 novembe
(not for usage questions)
Subject: Re: [openstack-dev] [neutron][TripleO] Clear all flows when ovs agent
start? why and how avoid?
I have no opposition to that, and I will be happy to assist reviewing the code
that will enable flow synchronisation (or to say it in an easier way, punctual
removal
-dev] [neutron][TripleO] Clear all flows when ovs agent
start? why and how avoid?
I have no opposition to that, and I will be happy to assist reviewing the code
that will enable flow synchronisation (or to say it in an easier way, punctual
removal of flows unknown to the l2 agent).
In the
,
>
> Erik
>
>
>
>
>
> *From:* Germy Lure [mailto:germy.l...@gmail.com]
> *Sent:* den 5 november 2014 10:46
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [neutron][TripleO] Clear all flows when
> ovs agent start? wh
-dev] [neutron][TripleO] Clear all flows when ovs agent
start? why and how avoid?
Hi Salvatore,
A startup flag is really a simpler approach. But in what situation we should
set this flag to remove all flows? upgrade? restart manually? internal fault?
Indeed, only at the time that there are
Hi Salvatore,
A startup flag is really a simpler approach. But in what situation we
should set this flag to remove all flows? upgrade? restart manually?
internal fault?
Indeed, only at the time that there are inconsistent(incorrect, unwanted,
stable and so on) flows between agent and the ovs relat
>From what I gather from this thread and related bug report, the change
introduced in the OVS agent is causing a data plane outage upon agent
restart, which is not desirable in most cases.
The rationale for the change that introduced this bug was, I believe,
cleaning up stale flows on the OVS agen
Hi,
Consider the triggering of restart agent, I think it's nothing but:
1). only restart agent
2). reboot the host that agent deployed on
When the agent started, the ovs may:
a.have all correct flows
b.have nothing at all
c.have partly correct flows, the others may need to be reprogrammed,
delete
Clearing all flows upon agent restart is a major issue, imho. We should really
look at this with higher priority than the modular L2 agent as the timeline of
the refactor isn't clear for the modular layer 2 agent. Whatever the issue
was, I think we ought to be able to find a better solution t
On 10/29/2014 10:17 AM, Kyle Mestery wrote:
> On Wed, Oct 29, 2014 at 7:25 AM, Hly wrote:
>>
>>
>> Sent from my iPad
>>
>> On 2014-10-29, at 下午8:01, Robert van Leeuwen
>> wrote:
>>
> I find our current design is remove all flows then add flow by entry, this
> will cause every network nod
14 matches
Mail list logo
