Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Hi Haim, Thanks for taking care of this. I see that Miguel has started working on the new L2 extension for Flow management。 https://bugs.launchpad.net/neutron/+bug/1563967 https://review.openstack.org/#/c/320439/ We may need to sync up the change with this new work too. Thanks, Cathy From:

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Hi all, sorry for digging up this thread. I took a liberty to submitt an RFE per Ihar's suggestion for the first step (switching to l2 agent extensions): https://bugs.launchpad.net/networking-sfc/+bug/1586024 As a followup on that - hoping to send some wip patches in the near time. Hope to hear

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

+1 for the bi-weekly proposal @17:00 UTC Tuesday. IMO, let's start with this and then we can check on the feasibility of having the meeting on a weekly basis. On May 23, 2016 1:10 PM, "Takashi Yamamoto" wrote: > On Wed, May 18, 2016 at 4:57 PM, Miguel Angel Ajo Pelayo >

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

On Wed, May 18, 2016 at 4:57 PM, Miguel Angel Ajo Pelayo wrote: > Hey, > >Finally we took over the channel for 1h. mostly because the time was > already agreed between many people on opposed timezones and it was a bit > late to cancel it. > >The first point was

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

No worries. If the slot isn't available maybe we can get infra to add another channel. On Wed, May 18, 2016 at 12:57 AM, Miguel Angel Ajo Pelayo < majop...@redhat.com> wrote: > Hey, > >Finally we took over the channel for 1h. mostly because the time was > already agreed between many people

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Hey, Finally we took over the channel for 1h. mostly because the time was already agreed between many people on opposed timezones and it was a bit late to cancel it. The first point was finding a suitable timeslot for a biweekly meeting -for some time- and alternatively following up on

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Yeah, no meetings in #openstack-neutron please. It leaves us nowhere to discuss development stuff during that hour. On Tue, May 17, 2016 at 2:54 AM, Miguel Angel Ajo Pelayo < majop...@redhat.com> wrote: > I agree, let's try to find a timeslot that works. > > using #openstack-neutron with the

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

I agree, let's try to find a timeslot that works. using #openstack-neutron with the meetbot works, but it's going to generate a lot of noise. On Tue, May 17, 2016 at 11:47 AM, Ihar Hrachyshka wrote: > > > On 16 May 2016, at 15:47, Takashi Yamamoto >

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

> On 16 May 2016, at 15:47, Takashi Yamamoto wrote: > > On Mon, May 16, 2016 at 10:25 PM, Takashi Yamamoto > wrote: >> hi, >> >> On Mon, May 16, 2016 at 9:00 PM, Ihar Hrachyshka wrote: >>> +1 for earlier time. But also, have

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

On Mon, May 16, 2016 at 10:25 PM, Takashi Yamamoto wrote: > hi, > > On Mon, May 16, 2016 at 9:00 PM, Ihar Hrachyshka wrote: >> +1 for earlier time. But also, have we booked any channel for the meeting? >> Hijacking #openstack-neutron may not work fine

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

hi, On Mon, May 16, 2016 at 9:00 PM, Ihar Hrachyshka wrote: > +1 for earlier time. But also, have we booked any channel for the meeting? > Hijacking #openstack-neutron may not work fine during such a busy (US) time. > I suggest we propose a patch for >

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

+1 for earlier time. But also, have we booked any channel for the meeting? Hijacking #openstack-neutron may not work fine during such a busy (US) time. I suggest we propose a patch for https://github.com/openstack-infra/irc-meetings Ihar > On 10 May 2016, at 20:35, Cathy Zhang

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

It is always hard to find a day and time that is good for everyone around the globe:-) The first meeting will still be UTC 1700 ~ UTC 1800 May 17 on Neutron channel. In the meeting, we can see if we can reach consensus on a new meeting time. Cathy -Original Message- From: Takashi

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

On Tue, May 10, 2016 at 12:41 AM, wrote: > Hi Cathy, > > Cathy Zhang: >> >> I will tentatively set the meeting time to UTC 1700 ~ UTC 1800 Tuesday. >> Hope this time is good for all people who have interest and like to >> contribute to this work. We plan to start the

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Hi Cathy, Cathy Zhang: I will tentatively set the meeting time to UTC 1700 ~ UTC 1800 Tuesday. Hope this time is good for all people who have interest and like to contribute to this work. We plan to start the first meeting on May 17. I would be happy to participate, but I'm unlikely to be

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Thank you! Cathy -Original Message- From: Miguel Angel Ajo Pelayo [mailto:majop...@redhat.com] Sent: Friday, May 06, 2016 12:42 AM To: OpenStack Development Mailing List (not for usage questions) Cc: Cathy Zhang Subject: Re: [openstack-dev] [neutron] work on Common Flow Classifier and

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Sounds good, I started by opening a tiny RFE, that may help in the organization of flows inside OVS agent, for inter operability of features (SFC, TaaS, ovs fw, and even port trunking with just openflow). [1] [2] [1] https://bugs.launchpad.net/neutron/+bug/1577791 [2]

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Hi Miguel, No worry. Today is just a meeting for lunch to get to know each other although we touched some technical points. We will recap and do the technical discussion at Room 400 at 3:10pm Thursday. Cathy From: Miguel Angel Ajo Pelayo [mailto:majop...@redhat.com] Sent: Wednesday, April 27,

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Please add me to whatsapp or telegram if you use that : +34636522569 El 27/4/2016 12:50, majop...@redhat.com escribió: > Trying to find you folks. I was late > El 27/4/2016 12:04, "Paul Carver" escribió: > >> SFC team and anybody else dealing with flow

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Trying to find you folks. I was late El 27/4/2016 12:04, "Paul Carver" escribió: > SFC team and anybody else dealing with flow selection/classification (e.g. > QoS), > > I just wanted to confirm that we're planning to meet in salon C today > (Wednesday) to get lunch but

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

SFC team and anybody else dealing with flow selection/classification (e.g. QoS), I just wanted to confirm that we're planning to meet in salon C today (Wednesday) to get lunch but then possibly move to a quieter location to discuss the common flow classifier ideas. On 4/21/2016 19:42, Cathy

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

On 04/22/2016 02:42 AM, Cathy Zhang wrote: > So let’s meet at "Salon C" for lunch from 12:30pm~1:50pm on Wednesday > and then continue the discussion at Room 400 at 3:10pm Thursday. > > Since Salon C is a big room, I will put a sign “Common Flow Classifier > and OVS Agent Extension” on the

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

I like Malini’s suggestion on meeting for a lunch to get to know each other, then continue on Thursday. So let’s meet at "Salon C" for lunch from 12:30pm~1:50pm on Wednesday and then continue the discussion at Room 400 at 3:10pm Thursday. Since Salon C is a big room, I will put a sign “Common

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

+1 on Wednesday lunch On Thu, Apr 21, 2016 at 12:02 PM, Ihar Hrachyshka wrote: > Cathy Zhang wrote: > > Hi everyone, >> >> We have room 400 at 3:10pm on Thursday available for discussion of the >> two topics. >> Another option is to use the common

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Cathy Zhang wrote: Hi everyone, We have room 400 at 3:10pm on Thursday available for discussion of the two topics. Another option is to use the common room with roundtables in "Salon C" during Monday or Wednesday lunch time. Room 400 at 3:10pm is a closed room

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

I vote for Monday to get the ball rolling, meet the interested parties, and Continue on Thursday at 3:10 in a quieter setting ... so we leave with some consensus. Thanks Cathy! Malini -Original Message- From: Cathy Zhang [mailto:cathy.h.zh...@huawei.com] Sent: Thursday, April 21, 2016

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Hi everyone, We have room 400 at 3:10pm on Thursday available for discussion of the two topics. Another option is to use the common room with roundtables in "Salon C" during Monday or Wednesday lunch time. Room 400 at 3:10pm is a closed room while the Salon C is a big open room which can

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

On Thu, Apr 21, 2016 at 9:54 AM, Vikram Choudhary wrote: > AFAIK, there is proposal about adding a 'priority' option in the existing > flow classifier rule. This can ensure the rule ordering. > > It's more complicated than that, there you're only considering Flow Classifiers,

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

AFAIK, there is proposal about adding a 'priority' option in the existing flow classifier rule. This can ensure the rule ordering. On Thu, Apr 21, 2016 at 12:58 PM, IWAMOTO Toshihiro wrote: > At Wed, 20 Apr 2016 14:12:07 +0200, > Miguel Angel Ajo Pelayo wrote: > > > > I

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

At Wed, 20 Apr 2016 14:12:07 +0200, Miguel Angel Ajo Pelayo wrote: > > I think this is an interesting topic. > > What do you mean exactly by FC ? (feature chaining?) > > I believe we have three things to look at: (sorry for the TL) > > 1) The generalization of traffic filters / traffic

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

I think this is an interesting topic. What do you mean exactly by FC ? (feature chaining?) I believe we have three things to look at: (sorry for the TL) 1) The generalization of traffic filters / traffic classifiers. Having common models, some sort of common API or common API structure

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Sorry, I just saw, FC = flow classifier :-), I made it a multi purpose abrev. now ;) On Wed, Apr 20, 2016 at 2:12 PM, Miguel Angel Ajo Pelayo wrote: > I think this is an interesting topic. > > What do you mean exactly by FC ? (feature chaining?) > > I believe we have three

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Hi Reedip, Sure will include you in the discussion. Let me know if there are other Tap-as-a-Service members who would like to join this initiative. Cathy From: reedip banerjee [mailto:reedi...@gmail.com] Sent: Thursday, April 14, 2016 7:03 PM To: OpenStack Development Mailing List (not for

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Hi Ihar, My replies are inline. Thanks, Cathy -Original Message- From: Ihar Hrachyshka [mailto:ihrac...@redhat.com] Sent: Thursday, April 14, 2016 4:45 PM To: Cathy Zhang Cc: OpenStack Development Mailing List (not for usage questions); Vikram Choudhary; Sean M. Collins; Haim Daniel;

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Speaking on behalf of Tap-as-a-Service members, we would also be very much interested in the following initiative :) On Fri, Apr 15, 2016 at 5:14 AM, Ihar Hrachyshka wrote: > Cathy Zhang wrote: > > >> I think there is no formal spec or

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Cathy Zhang wrote: I think there is no formal spec or anything, just some emails around there. That said, I don’t follow why it’s a requirement for SFC to switch to l2 agent extension mechanism. Even today, with SFC maintaining its own agent, there are no clear

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Thanks for everyone's reply! Here is the summary based on the replies I received: 1. We should have a meet-up for these two topics. The "to" list are the people who have interest in these topics. I am thinking about around lunch time on Tuesday or Wednesday since some of us will fly

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Just to echo others: FWaaS would be interested in this as well so please keep us in the loop. Thanks, German On 4/14/16, 7:12 AM, "Sean M. Collins" wrote: >Vikram Choudhary wrote: >> Hi Cathy, >> >> A project called "neutron-classifier [1]" is also there addressing the

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Vikram Choudhary wrote: > Hi Cathy, > > A project called "neutron-classifier [1]" is also there addressing the same > use case. Let's sync up and avoid work duplicity. > > [1] https://github.com/openstack/neutron-classifier Agree with Vikram - we have a small git repo that we're using to futz

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Hi Cathy. I’d be interested in contributing. I think a meet up at the summit would be a good idea as the people I’ve engaged with from the other projects on this topic expressed interest. There was an etherpad for the l2-agent-extensions-api that was merged in Mitaka that listed projects that

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Cathy Zhang wrote: Hi everyone, Per Armando’s request, Louis and I are looking into the following features for Newton cycle. · Neutron Common FC used for SFC, QoS, Tap as a service etc., · OVS Agent extension Some of you might know that we already

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Hi cathy, at net-bgpvpn, we're very interested in this effort. Please, keep us in the loop. Mathieu On Thu, Apr 14, 2016 at 8:59 AM, Haim Daniel wrote: > Hi, > > I'd +1 Vikram's comment on neutron-classifier , RFE [1] contains the > original thread about that topic. > > >

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Hi Cathy, A project called "neutron-classifier [1]" is also there addressing the same use case. Let's sync up and avoid work duplicity. [1] https://github.com/openstack/neutron-classifier Thanks Vikram On Apr 14, 2016 6:40 AM, "Cathy Zhang" wrote: Hi everyone, Per