Re: [openstack-dev] [Neutron] Neutron team social event in Barcelona

[John McDowall]

-1

Unfortunately, a business meeting has come up

Regards

John
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Neutron team social event in Barcelona

[John McDowall]

+1

Thanks for organizing this

Regards

John
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

[John McDowall]

Ryan,

In-line below.

Regards

John

From: Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
Date: Friday, June 17, 2016 at 7:35 AM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>, Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>, "OpenStack Development 
Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
discuss <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>
Subject: Re: [ovs-discuss] [openstack-dev] [OVN] [networking-ovn] 
[networking-sfc] SFC andOVN


In-line below

"discuss" 
<discuss-boun...@openvswitch.org<mailto:discuss-boun...@openvswitch.org>> wrote 
on 06/15/2016 05:51:20 PM:

> From: John McDowall 
> <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
> To: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>
> Cc: Srilatha Tangirala/San Francisco/IBM@IBMUS, "OpenStack
> Development Mailing List \(not for usage questions\)"  d...@lists.openstack.org<mailto:d...@lists.openstack.org>>, discuss 
> <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>
> Date: 06/15/2016 05:51 PM
> Subject: Re: [ovs-discuss] [openstack-dev] [OVN] [networking-ovn]
> [networking-sfc] SFC andOVN
> Sent by: "discuss" 
> <discuss-boun...@openvswitch.org<mailto:discuss-boun...@openvswitch.org>>
>
> Juno,
>
> Apologies - I see your issue now, also I have got nothing done today
> - got sucked into an all day meeting. I was thinking very much from
> a  ovs/ovn perspective and also my first prototype was very simple.
>
> So while in networking=sfc/ovn the port-cahin does not have a switch
> I think port-chain needs a lswitch context as that is where the
> port-chain table is created. Let me try and lay this out. I am not
> sure if I am getting this right but it is a starting point for
> discussion and comment by the community.
>
> The first thing is that there could be three different types of
> VNF's, L3, L2, and Bump in the Wire (BITW). I am not sure if it
> would be possible to mix and match these different types in a series
> of port-pair-groups. Also as a first phase I have been trying to
> remove the need for the VNF to participate in the service chain (or
> be aware of it). In addition I also wanted to remove the need for
> any "proxy" as documented in the NSH model, by moving a lot of the
> functionality to the ovn-northd.
>
> Mode 1: BITW
> Port-Pairs: The logical ports need to be on the same logical switch
> Port-pair-groups: They are made up of sets of port-pairs, until we
> see the load-balancing proposal for ovs/ovn not sure if port-pairs
> can be on different logical switches or not. This translates to a
> set of rules in the port-chain table that chains output ports of one
> VNF to the input port of the next VNF, until the last VNF when the
> traffic is forwarded to the final destination of the packet. If the
> port-chain is bi-directional then the rule set has to be implemented
> in reverse (many VNF's Firewalls, Load Balancers etc need to see
> both legs of the traffic).
> Flow-classifier: Is a set of rules that are set as an ACL rule with
> first logical port of the first pair in the first port-pair-group.
> Likewise if the port-chain is bi-directional then the rules have to
> be symmetric to steer the traffic in both directions.
> Port-chain: defined on the same logical switch as the first logical-
> source-port of the flow-classifier, as this is where the port-chain
> table is created and the rules for traffic steering are inserted.
> Mode 2: L2
>
> I think this would be similar to the BITH case but instead of
> steering by logical ports the steering would be done by VLAN tags.
> This would also mean that the VNFs would have to be aware of the
> steering rules and be able to manipulate VLAN tags.
>
> Mode 3: L3
>
> This would require the VNF's to be aware of the routing rules and
> set static routes/net hop rules for each step in the service chain.
>
> Modes 2 & 3 would require a much more sophisticated control plane to
> program both OVN and the VNFs.

[Snip to save BW]

I'm not so sure John.  I agree that OVN would have to know about the
VF type (BiW/L2/L3) and further that OVN would need to be told about
the appropriate L2/L3 "next port" information - either VLAN tags or
IP addresses, but once I have that, I think the actual vswitch
programming is fairly straightforward:  for L2, the vswitch is
programmed to use

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

[John McDowall]

Ryan,

See inline

Regards

John

From: Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
Date: Friday, June 17, 2016 at 7:26 AM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: discuss <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, Na Zhu 
<na...@cn.ibm.com<mailto:na...@cn.ibm.com>>, "OpenStack Development Mailing 
List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
Srilatha Tangirala <srila...@us.ibm.com<mailto:srila...@us.ibm.com>>
Subject: Re: [ovs-discuss] [openstack-dev] [OVN] [networking-ovn] 
[networking-sfc] SFC andOVN


Apologies for being delayed on replying and in-line back as well

Ryan

John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>> wrote 
on 06/15/2016 05:58:35 PM:

> From: John McDowall 
> <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>, Srilatha 
> Tangirala/San Francisco/
> IBM@IBMUS, "OpenStack Development Mailing List (not for usage
> questions)" 
> <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>,
>  discuss
> <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>
> Date: 06/15/2016 05:58 PM
> Subject: Re: [ovs-discuss] [openstack-dev] [OVN] [networking-ovn]
> [networking-sfc] SFC andOVN
>
> Ryan,
>
> In-line
>
> Regards
>
> John
>
> From: Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
> Date: Tuesday, June 14, 2016 at 9:42 PM
> To: John McDowall 
> <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
> Cc: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>, Srilatha Tangirala 
> <srila...@us.ibm.com<mailto:srila...@us.ibm.com>
> >, "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
> discuss <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>
> Subject: Re: [ovs-discuss] [openstack-dev] [OVN] [networking-ovn]
> [networking-sfc] SFC andOVN
>
> "discuss" 
> <discuss-boun...@openvswitch.org<mailto:discuss-boun...@openvswitch.org>> 
> wrote on 06/14/2016 10:31:40 PM:
>
> > From: John McDowall 
> > <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
> > To: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>
> > Cc: Srilatha Tangirala/San Francisco/IBM@IBMUS, "OpenStack
> > Development Mailing List \(not for usage questions\)"  > d...@lists.openstack.org<mailto:d...@lists.openstack.org>>, discuss 
> > <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>
> > Date: 06/14/2016 10:48 PM
> > Subject: Re: [ovs-discuss] [openstack-dev] [OVN] [networking-ovn]
> > [networking-sfc] SFC andOVN
> > Sent by: "discuss" 
> > <discuss-boun...@openvswitch.org<mailto:discuss-boun...@openvswitch.org>>
> >
> > Juno,
> >
> > It is a container for port-pair-groups and flow-classifier. I
> > imagine there could be more the than one port-chain per switch. Also
> > we may want to extend the model beyond a single lswitch
>
> I agree that there could be more than one port-chain per switch, determined
> by the flow classifier.
>
> What I'm confused by is:
>
> 1. Why are items only recorded in logical switches?  I would think
> that I could also attach an SFC to a logical router - although I admit
> that the current neutron model for ports doesn't really allow that
> easily.  Couple that with the change of name from Logical_Port to
> Logical_Switch_Port, and I'm left wondering if we aren't better off
> with the following "weak" links instead:
> -the Port_Chain includes the logical switch as an external_id
> -each Port_Pair_Group includes the Port_Chain as an external_id
> -each Port_Pair includes the PPG as an external_id
> -each Logical_Switch_Port includes the PP as an external_id
>
> I *think* that *might* allow me (in the future) to attach a port chain
> to a logical router by setting the logical router as an external_id and
> using Logical_Router_Ports to make up the PPs...
>
> JED> If there are “port-chain” tables for switches and routers I
> think I agree. Not sure how this is impacted by the type of VNF (see
> the last email to Juno). I struggle a bit with imagining the flows.

RM> Back in the day when we discussed this in

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

[John McDowall]

Ryan,

In-line

Regards

John

From: Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
Date: Tuesday, June 14, 2016 at 9:42 PM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>, Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>, "OpenStack Development 
Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
discuss <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>
Subject: Re: [ovs-discuss] [openstack-dev] [OVN] [networking-ovn] 
[networking-sfc] SFC andOVN


"discuss" 
<discuss-boun...@openvswitch.org<mailto:discuss-boun...@openvswitch.org>> wrote 
on 06/14/2016 10:31:40 PM:

> From: John McDowall 
> <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
> To: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>
> Cc: Srilatha Tangirala/San Francisco/IBM@IBMUS, "OpenStack
> Development Mailing List \(not for usage questions\)"  d...@lists.openstack.org<mailto:d...@lists.openstack.org>>, discuss 
> <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>
> Date: 06/14/2016 10:48 PM
> Subject: Re: [ovs-discuss] [openstack-dev] [OVN] [networking-ovn]
> [networking-sfc] SFC andOVN
> Sent by: "discuss" 
> <discuss-boun...@openvswitch.org<mailto:discuss-boun...@openvswitch.org>>
>
> Juno,
>
> It is a container for port-pair-groups and flow-classifier. I
> imagine there could be more the than one port-chain per switch. Also
> we may want to extend the model beyond a single lswitch

I agree that there could be more than one port-chain per switch, determined
by the flow classifier.

What I'm confused by is:

1. Why are items only recorded in logical switches?  I would think
that I could also attach an SFC to a logical router - although I admit
that the current neutron model for ports doesn't really allow that
easily.  Couple that with the change of name from Logical_Port to
Logical_Switch_Port, and I'm left wondering if we aren't better off
with the following "weak" links instead:
-the Port_Chain includes the logical switch as an external_id
-each Port_Pair_Group includes the Port_Chain as an external_id
-each Port_Pair includes the PPG as an external_id
-each Logical_Switch_Port includes the PP as an external_id

I *think* that *might* allow me (in the future) to attach a port chain
to a logical router by setting the logical router as an external_id and
using Logical_Router_Ports to make up the PPs...

JED> If there are "port-chain" tables for switches and routers I think I agree. 
Not sure how this is impacted by the type of VNF (see the last email to Juno). 
I struggle a bit with imagining the flows.

2. I still don't see what Logical_Flow_Classifier is buying me that
ACL doesn't - I can codify all of the classifiers given in the match
criteria of an ACL entry and codify the first PPG of the SFC as
the action of the ACL entry...

JED> Flow classifiers do map to an ACL entry - just need additional metadata, 
I.e. Action of the ACL and wether the rules should be uni or bi-directional. 
Though that information could be in the port-chain.

Ryan
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

[John McDowall]

Juno,

I worked on ovs/ovn today and re-structured the schema. I could not figure out 
how to make this work without have lport-chains as a child of lswitch. So I 
have got the basics working – attached a simple shell script that creates and 
shows the port-chains. I tried to merge with the upstream master but there are 
a bunch of changes that while minor would have taken sometime to merge in, so I 
skipped it for now.

The new schema will break the networking-ovn IDL, apologies.  The areas I can 
think of are:

Port-chain is now a child of lswitch so needs that as a parameter.
Flow-classifier is now a child of port-chain only so need to change from 
lswitch to lport-chain

If you can work on the changes to networking-ovn great (I promise not to change 
the schema again until we have had a wider review). If not I will get to it 
tomorrow.

Regards

John

From: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>
Date: Monday, June 13, 2016 at 9:57 PM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: discuss <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, 
"OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
Srilatha Tangirala <srila...@us.ibm.com<mailto:srila...@us.ibm.com>>
Subject: Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] 
[networking-sfc] SFC andOVN

Hi John,

OK, I also find the column "port_pairs" and "flow_classifiers" can not be wrote 
by idl APIs, I will try to fix it.
If any update, i will send you email.



Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com<mailto:na...@cn.ibm.com>
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, 
Shanghai, China (201203)



From:John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
To:Na Zhu/China/IBM@IBMCN
Cc:"OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
discuss <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, Srilatha 
Tangirala <srila...@us.ibm.com<mailto:srila...@us.ibm.com>>
Date:2016/06/14 12:17
Subject:Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] 
[networking-sfc] SFC andOVN




Juno,

Trying to implement this today showed that this will not work for OVN. I am 
going back to RussellB 's original model with port-chain as a child of lswitch.

I can make this work and then we can evolve from there. It will require some 
re-write of the idl code - hopefully I will get it done tomorrow.

Regards

John

Sent from my iPhone

On Jun 13, 2016, at 8:41 PM, Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>> 
wrote:

Hi John,

I see you add column "port_pairs" and "flow_classifiers" to table 
Logical_Switch, I am not clear about it, the port-pair ingress port and egress 
port can be the same, they also can be different and in same/different network, 
and the flow classifier is not per network neither, can you explain why you do 
that?




Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com<mailto:na...@cn.ibm.com>
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, 
Shanghai, China (201203)



From:Na Zhu/China/IBM@IBMCN
To:John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc:Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>, "OpenStack Development 
Mailing List \(not for usage questions\)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
discuss <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>
Date:2016/06/14 10:44
Subject:Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] 
[networking-sfc] SFC andOVN




Hi John,

My github account is JunoZhu, pls add me as member of your private repo.
If you submit WIP patch today, then i can update your WIP patch, no need to 
update your private repo.
If not, i will update your private repo.

Thanks.



Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com<mailto:na...@cn.ibm.com>
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, 
Shanghai, China (201203)



From:John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
To:Na Zhu/China/IBM@IBMCN
Cc:discuss <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, 
Srilatha Tangirala <srila...@us

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

[John McDowall]

Juno,

Added you to my private repos


Regards

John

Sent from my iPhone

On Jun 13, 2016, at 7:39 PM, Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>> 
wrote:

Hi John,

My github account is JunoZhu, pls add me as member of your private repo.
If you submit WIP patch today, then i can update your WIP patch, no need to 
update your private repo.
If not, i will update your private repo.

Thanks.



Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com<mailto:na...@cn.ibm.com>
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, 
Shanghai, China (201203)



From:    John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
To:Na Zhu/China/IBM@IBMCN
Cc:discuss <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, 
Srilatha Tangirala <srila...@us.ibm.com<mailto:srila...@us.ibm.com>>, 
"OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Date:2016/06/13 23:55
Subject:Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] 
[networking-sfc] SFC andOVN




Juno,

What ever is easiest for you – I can submit WIP patches today for 
networking-ovn and networking-ovs. If you send me your github login I will add 
you as a collaborator to my private repo.

I am currently working on getting the changes into ovs/ovn ovn-northd.c to 
support the new schema – hopefully today or tomorrow. Most of the IDL is in and 
I can get info from networking-sfc to ovs/ovn northd.

Regards

John
From: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>
Date: Monday, June 13, 2016 at 6:25 AM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: discuss <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, Srilatha 
Tangirala <srila...@us.ibm.com<mailto:srila...@us.ibm.com>>, "OpenStack 
Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] 
[networking-sfc] SFC andOVN

Hi John,

I know you are busy recently, sorry to disturb you. I want to ask you whether I 
can submit patch to your private repo, I test your code changes and find some 
minor errors, I think we can work together to make the debug work done faster, 
then you can submit the WIP patch.

What do you think?




Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com<mailto:na...@cn.ibm.com>
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, 
Shanghai, China (201203)



From:Na Zhu/China/IBM@IBMCN
To:John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc:Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>, "OpenStack Development 
Mailing List \(not for usage questions\)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
discuss <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>
Date:2016/06/09 16:18
Subject:Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] 
[networking-sfc] SFC andOVN




Hi John,

I know most of the OVN driver codes are copied from OVS driver, OVN driver is 
different from OVS driver. For OVS driver, it should build the sfc flows and 
send to ovs agent, while OVN controller does not need to do it, OVN controller 
only need send the sfc parameters to OVN northbound DB, then ovn-controller can 
build the sfc flow.

networking-sfc defines some common APIs for each driver, see 
networking_sfc/services/sfc/drivers/base.py, I think for OVN, we only need 
write the methods about port-chain create/update/delete, and leave other method 
empty, What do you think?
If you agree with me, you have to refactor the OVN sfc driver, do you want me 
to do it?



Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com<mailto:na...@cn.ibm.com>
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, 
Shanghai, China (201203)



From:John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
To:Amitabha Biswas <azbis...@gmail.com<mailto:azbis...@gmail.com>>
Cc:Na Zhu/China/IBM@IBMCN, Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>, "OpenStack Development 
Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
discuss <disc...@openvswitch.org<mailto

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

[John McDowall]

Juno,

Trying to implement this today showed that this will not work for OVN. I am 
going back to RussellB 's original model with port-chain as a child of lswitch.

I can make this work and then we can evolve from there. It will require some 
re-write of the idl code - hopefully I will get it done tomorrow.

Regards

John

Sent from my iPhone

On Jun 13, 2016, at 8:41 PM, Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>> 
wrote:

Hi John,

I see you add column "port_pairs" and "flow_classifiers" to table 
Logical_Switch, I am not clear about it, the port-pair ingress port and egress 
port can be the same, they also can be different and in same/different network, 
and the flow classifier is not per network neither, can you explain why you do 
that?




Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com<mailto:na...@cn.ibm.com>
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, 
Shanghai, China (201203)



From:Na Zhu/China/IBM@IBMCN
To:John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc:Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>, "OpenStack Development 
Mailing List \(not for usage questions\)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
discuss <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>
Date:2016/06/14 10:44
Subject:Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] 
[networking-sfc] SFC andOVN




Hi John,

My github account is JunoZhu, pls add me as member of your private repo.
If you submit WIP patch today, then i can update your WIP patch, no need to 
update your private repo.
If not, i will update your private repo.

Thanks.



Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com<mailto:na...@cn.ibm.com>
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, 
Shanghai, China (201203)



From:John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
To:Na Zhu/China/IBM@IBMCN
Cc:discuss <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, 
Srilatha Tangirala <srila...@us.ibm.com<mailto:srila...@us.ibm.com>>, 
"OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Date:2016/06/13 23:55
Subject:Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] 
[networking-sfc] SFC andOVN




Juno,

What ever is easiest for you – I can submit WIP patches today for 
networking-ovn and networking-ovs. If you send me your github login I will add 
you as a collaborator to my private repo.

I am currently working on getting the changes into ovs/ovn ovn-northd.c to 
support the new schema – hopefully today or tomorrow. Most of the IDL is in and 
I can get info from networking-sfc to ovs/ovn northd.

Regards

John
From: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>
Date: Monday, June 13, 2016 at 6:25 AM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: discuss <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, Srilatha 
Tangirala <srila...@us.ibm.com<mailto:srila...@us.ibm.com>>, "OpenStack 
Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] 
[networking-sfc] SFC andOVN

Hi John,

I know you are busy recently, sorry to disturb you. I want to ask you whether I 
can submit patch to your private repo, I test your code changes and find some 
minor errors, I think we can work together to make the debug work done faster, 
then you can submit the WIP patch.

What do you think?




Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com<mailto:na...@cn.ibm.com>
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, 
Shanghai, China (201203)



From:Na Zhu/China/IBM@IBMCN
To:John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc:Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>, "OpenStack Development 
Mailing List \(not for usage questions\)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
discuss <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>
Date:2016/06/09 16:18
Subject:Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] 
[net

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

[John McDowall]

Juno,

What ever is easiest for you – I can submit WIP patches today for 
networking-ovn and networking-ovs. If you send me your github login I will add 
you as a collaborator to my private repo.

I am currently working on getting the changes into ovs/ovn ovn-northd.c to 
support the new schema – hopefully today or tomorrow. Most of the IDL is in and 
I can get info from networking-sfc to ovs/ovn northd.

Regards

John
From: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>
Date: Monday, June 13, 2016 at 6:25 AM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: discuss <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, Srilatha 
Tangirala <srila...@us.ibm.com<mailto:srila...@us.ibm.com>>, "OpenStack 
Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] 
[networking-sfc] SFC andOVN

Hi John,

I know you are busy recently, sorry to disturb you. I want to ask you whether I 
can submit patch to your private repo, I test your code changes and find some 
minor errors, I think we can work together to make the debug work done faster, 
then you can submit the WIP patch.

What do you think?




Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com<mailto:na...@cn.ibm.com>
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, 
Shanghai, China (201203)



From:Na Zhu/China/IBM@IBMCN
To:John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc:Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>, "OpenStack Development 
Mailing List \(not for usage questions\)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
discuss <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>
Date:2016/06/09 16:18
Subject:Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] 
[networking-sfc] SFC andOVN




Hi John,

I know most of the OVN driver codes are copied from OVS driver, OVN driver is 
different from OVS driver. For OVS driver, it should build the sfc flows and 
send to ovs agent, while OVN controller does not need to do it, OVN controller 
only need send the sfc parameters to OVN northbound DB, then ovn-controller can 
build the sfc flow.

networking-sfc defines some common APIs for each driver, see 
networking_sfc/services/sfc/drivers/base.py, I think for OVN, we only need 
write the methods about port-chain create/update/delete, and leave other method 
empty, What do you think?
If you agree with me, you have to refactor the OVN sfc driver, do you want me 
to do it?



Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com<mailto:na...@cn.ibm.com>
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, 
Shanghai, China (201203)



From:John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
To:Amitabha Biswas <azbis...@gmail.com<mailto:azbis...@gmail.com>>
Cc:Na Zhu/China/IBM@IBMCN, Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>, "OpenStack Development 
Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
discuss <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>
Date:2016/06/09 00:53
Subject:Re: [ovs-discuss] [openstack-dev] [OVN] [networking-ovn] 
[networking-sfc] SFC andOVN




Amitabha,

Thanks for looking at it . I took the suggestion from Juno and implemented it. 
I think it is a good solution as it minimizes impact on both networking-ovn and 
networking-sfc. I have updated my repos, if you have suggestions for 
improvements let me know.

I agree that there needs to be some refactoring of the networking-sfc driver 
code. I think the team did a good job with it as it was easy for me to create 
the OVN driver ( copy and paste). As more drivers are created I think the model 
will get polished and refactored.

Regards

John

From: Amitabha Biswas <azbis...@gmail.com<mailto:azbis...@gmail.com>>
Date: Tuesday, June 7, 2016 at 11:36 PM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>, Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>, "OpenStack Development 
Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

[John McDowall]

Juno,

Ok added the code and I have port-chains creating up to the IDL 
networking-sfc->networking-ovn then I have an issue with my IDL I need to fix.

So we have a model for creating port-chains all the way through, updated the 
repos to reflect the changes.

Thanks for your help.

Regards

John

From: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>
Date: Wednesday, June 8, 2016 at 12:44 AM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, "OpenStack 
Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
Srilatha Tangirala <srila...@us.ibm.com<mailto:srila...@us.ibm.com>>
Subject: Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] 
[networking-sfc] SFC andOVN

Hi John,

I think you can create ovsdb idl client in networking-sfc to connect to 
OVN_Northbound DB, then call the APIs you add to networking-ovn to configure 
SFC.
Now OVN is a ML2 mechanism driver (OVNMechanismDriver), not core plugin, the 
OVN L3 (OVNL3RouterPlugin) is a neutron service plugin like vpn, sfc and ect.

You can refer to method OVNMechanismDriver._ovn and OVNL3RouterPlugin._ovn, 
they both create ovsdb idl client object, so in your ovn driver, you can do it 
in the same way. Here is the code sample:

class OVNSfcDriver(driver_base.SfcDriverBase,
   ovs_sfc_db.OVSSfcDriverDB)
..
@property
def _ovn(self):
if self._ovn_property is None:
LOG.info(_LI("Getting OvsdbOvnIdl"))
self._ovn_property = impl_idl_ovn.OvsdbOvnIdl(self)
return self._ovn_property

..
@log_helpers.log_method_call
def create_port_chain(self, context):
port_chain = context.current
for flow_classifier in port_chain:
first get the flow classifier contents
then call self._ovn.create_lflow_classifier()
for port_pair_groups in port_chain:
get the port_pair_group contents
then call self._ovn.create_lport_pair_group()
for port_pair in port_pair_group
first get the port_pair contents
then call self._ovn.create_lport_pair()







Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com<mailto:na...@cn.ibm.com>
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, 
Shanghai, China (201203)



From:John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
To:Na Zhu/China/IBM@IBMCN, Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>
Cc:"disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, "OpenStack 
Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Date:2016/06/08 12:55
Subject:Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] 
[networking-sfc] SFC andOVN




Juno, Srilatha,

I need some help – I have fixed most of the obvious typo’s in the three repos 
and merged them with mainline. There is still a problem with the build I think 
in mech_driver.py but I will fix it asap in the am.

However I am not sure of the best way to interface between sfc and ovn.

In networking_sfc/services/src/drivers/ovn/driver.py there is a function that 
creates a deep copy of the port-chain dict, 
create_port_chain(self,contact,port_chain).

Looking at networking-ovn I think it should use mech_driver.py so we can call 
the OVS-IDL to send the parameters to ovn. However I am not sure of the best 
way to do it. Could you make some suggestions or send me some sample code 
showing the best approach?

I will get the ovs/ovn cleaned up and ready. Also Louis from the networking-sfc 
has posted a draft blueprint.

Regards

John

From: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>
Date: Monday, June 6, 2016 at 7:54 PM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>, Ryan 
Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, "OpenStack 
Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
Srilatha Tangirala <srila...@us.ibm.com<mailto:srila...@us.ibm.com>>
Subject: Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] 
[netw

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

[John McDowall]

Amitabha,

Thanks for looking at it . I took the suggestion from Juno and implemented it. 
I think it is a good solution as it minimizes impact on both networking-ovn and 
networking-sfc. I have updated my repos, if you have suggestions for 
improvements let me know.

I agree that there needs to be some refactoring of the networking-sfc driver 
code. I think the team did a good job with it as it was easy for me to create 
the OVN driver ( copy and paste). As more drivers are created I think the model 
will get polished and refactored.

Regards

John

From: Amitabha Biswas <azbis...@gmail.com<mailto:azbis...@gmail.com>>
Date: Tuesday, June 7, 2016 at 11:36 PM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>, Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>, "OpenStack Development 
Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
discuss <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>
Subject: Re: [ovs-discuss] [openstack-dev] [OVN] [networking-ovn] 
[networking-sfc] SFC andOVN

Hi John,

Looking at the code with Srilatha, it seems like the 
https://github.com/doonhammer/networking<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_doonhammer_networking=CwMF-g=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo=vZ6VUDaavDpfOdPQrz1ED54jEjvAE36A8TVJroVlrOQ=HkxBkhm69SxTBQTw2-s5MvEDiFsrOjXero1F3DeFO88=0qATypbGGShogPxjkRq8oKnjHMUvVwiWLAY17gBr6iM=>-ovn
 repo has gone down the path of having a sfc_ovn.py file in the 
networking-ovn/ovsdb directory. This file deals with the SFC specific OVSDB 
transactions in OVN. So to answer your question of invoking OVS-IDL, we can 
import the src_ovn.py file from 
networking_sfc/services/src/drivers/ovn/driver.py and invoke calls into IDL.

Another aspect from a networking-sfc point of view is the duplication of code 
between networking_sfc/services/src/drivers/ovn/driver.py and 
networking_sfc/services/src/drivers/ovs/driver.py in the 
https://github.com/doonhammer/networking-sfc<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_doonhammer_networking-2Dsfc=CwMF-g=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo=vZ6VUDaavDpfOdPQrz1ED54jEjvAE36A8TVJroVlrOQ=HkxBkhm69SxTBQTw2-s5MvEDiFsrOjXero1F3DeFO88=8ftwwsdvSwYTc3WSmDDad9L9dwV6CwaIuOwtoN5FwqA=>
 repo. There should be a mechanism to coalesce the common code and invoke the 
OVS and OVN specific parts separately.

Regards
Amitabha

On Jun 7, 2016, at 9:54 PM, John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>> wrote:

Juno, Srilatha,

I need some help – I have fixed most of the obvious typo’s in the three repos 
and merged them with mainline. There is still a problem with the build I think 
in mech_driver.py but I will fix it asap in the am.

However I am not sure of the best way to interface between sfc and ovn.

In networking_sfc/services/src/drivers/ovn/driver.py there is a function that 
creates a deep copy of the port-chain dict, 
create_port_chain(self,contact,port_chain).

Looking at networking-ovn I think it should use mech_driver.py so we can call 
the OVS-IDL to send the parameters to ovn. However I am not sure of the best 
way to do it. Could you make some suggestions or send me some sample code 
showing the best approach?

I will get the ovs/ovn cleaned up and ready. Also Louis from the networking-sfc 
has posted a draft blueprint.

Regards

John

From: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>
Date: Monday, June 6, 2016 at 7:54 PM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>, Ryan 
Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, "OpenStack 
Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
Srilatha Tangirala <srila...@us.ibm.com<mailto:srila...@us.ibm.com>>
Subject: Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] 
[networking-sfc] SFC andOVN

Hi John,

I do not know any better approach, I think it is good to write all the 
parameters in the creation of a port chain, this can avoid saving many data in 
northbound db which are not used. We can do it in that way currently, if the 
community has opposite ideas, we can change, what do you think?

Hi Ryan,

Do you agree with that?



Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com<mailto:na...@cn.ibm.com>
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, 
Shanghai, China (201203)

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

[John McDowall]

Juni,

Thanks – added the code and everything builds, just need to debug end-to-end 
now.  I think your approach is the best so far all the IDL code for accessing 
ovs/ovn is in networking-ovn. The OVN driver in networking-sfc calls the IDL 
code to access ovs/ovn. There is minimal linkage between networking-sfc and 
networking-ovn , just one import:

from networking_ovn.ovsdb import impl_idl_ovn

I think this is what Ryan was asking for.

I have updated all repos so we can think about creating WIP patches.

Regards

John
From: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>
Date: Wednesday, June 8, 2016 at 12:44 AM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, "OpenStack 
Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
Srilatha Tangirala <srila...@us.ibm.com<mailto:srila...@us.ibm.com>>
Subject: Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] 
[networking-sfc] SFC andOVN

Hi John,

I think you can create ovsdb idl client in networking-sfc to connect to 
OVN_Northbound DB, then call the APIs you add to networking-ovn to configure 
SFC.
Now OVN is a ML2 mechanism driver (OVNMechanismDriver), not core plugin, the 
OVN L3 (OVNL3RouterPlugin) is a neutron service plugin like vpn, sfc and ect.

You can refer to method OVNMechanismDriver._ovn and OVNL3RouterPlugin._ovn, 
they both create ovsdb idl client object, so in your ovn driver, you can do it 
in the same way. Here is the code sample:

class OVNSfcDriver(driver_base.SfcDriverBase,
   ovs_sfc_db.OVSSfcDriverDB)
..
@property
def _ovn(self):
if self._ovn_property is None:
LOG.info(_LI("Getting OvsdbOvnIdl"))
self._ovn_property = impl_idl_ovn.OvsdbOvnIdl(self)
return self._ovn_property

..
@log_helpers.log_method_call
def create_port_chain(self, context):
port_chain = context.current
for flow_classifier in port_chain:
first get the flow classifier contents
then call self._ovn.create_lflow_classifier()
for port_pair_groups in port_chain:
get the port_pair_group contents
then call self._ovn.create_lport_pair_group()
for port_pair in port_pair_group
first get the port_pair contents
then call self._ovn.create_lport_pair()







Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com<mailto:na...@cn.ibm.com>
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, 
Shanghai, China (201203)



From:John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
To:Na Zhu/China/IBM@IBMCN, Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>
Cc:"disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, "OpenStack 
Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Date:2016/06/08 12:55
Subject:Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] 
[networking-sfc] SFC andOVN




Juno, Srilatha,

I need some help – I have fixed most of the obvious typo’s in the three repos 
and merged them with mainline. There is still a problem with the build I think 
in mech_driver.py but I will fix it asap in the am.

However I am not sure of the best way to interface between sfc and ovn.

In networking_sfc/services/src/drivers/ovn/driver.py there is a function that 
creates a deep copy of the port-chain dict, 
create_port_chain(self,contact,port_chain).

Looking at networking-ovn I think it should use mech_driver.py so we can call 
the OVS-IDL to send the parameters to ovn. However I am not sure of the best 
way to do it. Could you make some suggestions or send me some sample code 
showing the best approach?

I will get the ovs/ovn cleaned up and ready. Also Louis from the networking-sfc 
has posted a draft blueprint.

Regards

John

From: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>
Date: Monday, June 6, 2016 at 7:54 PM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>, Ryan 
Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, "OpenStack 
Development Mailing List (not for usage questions)" 
<openstack-dev@

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

[John McDowall]

Juno,

Sorry jumped the gun not published yet :-(. Will send you the link when it is 
published.

Apologies

John

From: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>
Date: Wednesday, June 8, 2016 at 1:41 AM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, "OpenStack 
Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
Srilatha Tangirala <srila...@us.ibm.com<mailto:srila...@us.ibm.com>>
Subject: Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] 
[networking-sfc] SFC andOVN

John,

Is the blueprint Louis posted this one?
https://blueprints.launchpad.net/networking-sfc/+spec/networking-sfc-ovn-driver<https://urldefense.proofpoint.com/v2/url?u=https-3A__blueprints.launchpad.net_networking-2Dsfc_-2Bspec_networking-2Dsfc-2Dovn-2Ddriver=CwMFoQ=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo=vZ6VUDaavDpfOdPQrz1ED54jEjvAE36A8TVJroVlrOQ=nIPBwUi3I7aIENifgoU9Xk8JpByXc6PbztSGYkUTtmc=umGwhbq4t2actpS589D1IOuVHPzXBgS8xjlIaYp-Jj0=>

If not, can you send me the link?


Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com<mailto:na...@cn.ibm.com>
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, 
Shanghai, China (201203)



From:John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
To:Na Zhu/China/IBM@IBMCN, Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>
Cc:"disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, "OpenStack 
Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Date:2016/06/08 12:55
Subject:Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] 
[networking-sfc] SFC andOVN




Juno, Srilatha,

I need some help – I have fixed most of the obvious typo’s in the three repos 
and merged them with mainline. There is still a problem with the build I think 
in mech_driver.py but I will fix it asap in the am.

However I am not sure of the best way to interface between sfc and ovn.

In networking_sfc/services/src/drivers/ovn/driver.py there is a function that 
creates a deep copy of the port-chain dict, 
create_port_chain(self,contact,port_chain).

Looking at networking-ovn I think it should use mech_driver.py so we can call 
the OVS-IDL to send the parameters to ovn. However I am not sure of the best 
way to do it. Could you make some suggestions or send me some sample code 
showing the best approach?

I will get the ovs/ovn cleaned up and ready. Also Louis from the networking-sfc 
has posted a draft blueprint.

Regards

John

From: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>
Date: Monday, June 6, 2016 at 7:54 PM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>, Ryan 
Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, "OpenStack 
Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
Srilatha Tangirala <srila...@us.ibm.com<mailto:srila...@us.ibm.com>>
Subject: Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] 
[networking-sfc] SFC andOVN

Hi John,

I do not know any better approach, I think it is good to write all the 
parameters in the creation of a port chain, this can avoid saving many data in 
northbound db which are not used. We can do it in that way currently, if the 
community has opposite ideas, we can change, what do you think?

Hi Ryan,

Do you agree with that?



Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com<mailto:na...@cn.ibm.com>
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, 
Shanghai, China (201203)



From:John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
To:Na Zhu/China/IBM@IBMCN
Cc:"disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, Ryan Moats 
<rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>, Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>, "OpenStack Development 
Mailing List (not for usage questions)" 

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

[John McDowall]

Juno, Srilatha,

I need some help – I have fixed most of the obvious typo’s in the three repos 
and merged them with mainline. There is still a problem with the build I think 
in mech_driver.py but I will fix it asap in the am.

However I am not sure of the best way to interface between sfc and ovn.

In networking_sfc/services/src/drivers/ovn/driver.py there is a function that 
creates a deep copy of the port-chain dict, 
create_port_chain(self,contact,port_chain).

Looking at networking-ovn I think it should use mech_driver.py so we can call 
the OVS-IDL to send the parameters to ovn. However I am not sure of the best 
way to do it. Could you make some suggestions or send me some sample code 
showing the best approach?

I will get the ovs/ovn cleaned up and ready. Also Louis from the networking-sfc 
has posted a draft blueprint.

Regards

John

From: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>
Date: Monday, June 6, 2016 at 7:54 PM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>, Ryan 
Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, "OpenStack 
Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
Srilatha Tangirala <srila...@us.ibm.com<mailto:srila...@us.ibm.com>>
Subject: Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] 
[networking-sfc] SFC andOVN

Hi John,

I do not know any better approach, I think it is good to write all the 
parameters in the creation of a port chain, this can avoid saving many data in 
northbound db which are not used. We can do it in that way currently, if the 
community has opposite ideas, we can change, what do you think?

Hi Ryan,

Do you agree with that?



Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com<mailto:na...@cn.ibm.com>
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, 
Shanghai, China (201203)



From:John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
To:Na Zhu/China/IBM@IBMCN
Cc:"disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, Ryan Moats 
<rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>, Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>, "OpenStack Development 
Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Date:2016/06/06 23:36
Subject:Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] 
[networking-sfc] SFC andOVN




Juno,

Let me check – my intention was that the networking-sfc OVNB driver would 
configure all aspects of the port-chain and add the parameters to the 
networking-sfc db. Once all the parameters were in the creation of a port-chain 
would call networking-ovn (passing a deep copy of the port-chain dict). Here I 
see networking-ovn acting only as a bridge into ovs/ovn (I did not add anything 
in the ovn plugin – not sure if that is the right approach). Networking-ovn 
calls into ovs/ovn and inserts the entire port-chain.

Thoughts?

j

From: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>
Date: Monday, June 6, 2016 at 5:49 AM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, Ryan Moats 
<rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>, Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>, "OpenStack Development 
Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] 
[networking-sfc] SFC andOVN

Hi John,

One question need confirm with you, I think the ovn flow classifier driver and 
ovn port chain driver should call the APIs which you add to networking-ovn to 
configure the northbound db sfc tables, right? I see your networking-sfc ovn 
drivers, they does not call the APIs you add to networking-ovn, do you miss 
that?



Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com<mailto:na...@cn.ibm.com>
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, 
Shanghai, China (201203)



From:Na Zhu/China/IBM@IBMCN
To:John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloa

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

[John McDowall]

Srilatha,

I am trying to get these resolved but my devstack is broken and I am truing to 
resolve it.

Let me try and manual edit this and fix it – it is left over from the old API 
before I moved to the port-chain api.

Regards

John

From: Srilatha Tangirala <srila...@us.ibm.com<mailto:srila...@us.ibm.com>>
Date: Monday, June 6, 2016 at 2:01 PM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, Na Zhu 
<na...@cn.ibm.com<mailto:na...@cn.ibm.com>>, "OpenStack Development Mailing 
List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
Subject: Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] 
[networking-sfc] SFC andOVN


Hi John,

To get started with adding test scripts, I was trying to workout one end to end 
flow with the latest code from your private repos and found the following.

create_port_chain is calling _create_ovn_vnf.
This is calling self._ovn.create_lservice(
lservice_name = 'sfi-%s' % ovn_info['id'],
lswitch_name = lswitch_name,
name = ovn_info['name'],
app_port = ovn_info['app_port_id'],
in_port = ovn_info['in_port_id'],
out_port = ovn_info['out_port_id'] ))

I could not find create_lservice() in networking-sfc or networking-ovn repos. 
Are you planning to move OVN related apis(ex:_create_ovn_vnf) from SFC driver 
to networking-ovn? Please let us know what is the best way to proceed to write 
the test scripts.

Thanks,
Srilatha.






[Inactive hide details for John McDowall ---06/06/2016 08:36:16 AM---Juno, Let 
me check – my intention was that the networking-]John McDowall ---06/06/2016 
08:36:16 AM---Juno, Let me check – my intention was that the networking-sfc 
OVNB driver would configure all aspect

From: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
To: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>
Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, Ryan 
Moats/Omaha/IBM@IBMUS, Srilatha Tangirala/San Francisco/IBM@IBMUS, "OpenStack 
Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Date: 06/06/2016 08:36 AM
Subject: Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] 
[networking-sfc] SFC andOVN





Juno,

Let me check – my intention was that the networking-sfc OVNB driver would 
configure all aspects of the port-chain and add the parameters to the 
networking-sfc db. Once all the parameters were in the creation of a port-chain 
would call networking-ovn (passing a deep copy of the port-chain dict). Here I 
see networking-ovn acting only as a bridge into ovs/ovn (I did not add anything 
in the ovn plugin – not sure if that is the right approach). Networking-ovn 
calls into ovs/ovn and inserts the entire port-chain.

Thoughts?

j

From: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>
Date: Monday, June 6, 2016 at 5:49 AM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, Ryan Moats 
<rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>, Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>, "OpenStack Development 
Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] 
[networking-sfc] SFC andOVN

Hi John,

One question need confirm with you, I think the ovn flow classifier driver and 
ovn port chain driver should call the APIs which you add to networking-ovn to 
configure the northbound db sfc tables, right? I see your networking-sfc ovn 
drivers, they does not call the APIs you add to networking-ovn, do you miss 
that?



Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com<mailto:na...@cn.ibm.com>
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, 
Shanghai, China (201203)



From: Na Zhu/China/IBM@IBMCN
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: Srilatha Tangirala <srila...@us.ibm.com<mailto:srila...@us.ibm.com>>, 
OpenStack Development Mailing List 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
Ryan Moats <rmo...@

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

[John McDowall]

Juno,

I was going to take a pass at 3 today to see if I can get a working use case 
before I submit the patches.
On 1 I will reach out to the networking-sfc team to get the design spec started.
I will start looking at how to get the patches submitted too.

So with your and Srilatha’s help I think we can get in done in the next few 
days.

j

From: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>
Date: Sunday, June 5, 2016 at 11:22 PM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, OpenStack 
Development Mailing List 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>, Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>
Subject: Re: [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

John,

Thanks your working overtime in last weekend, now we have the following works 
to do:
1, submit design spec to networking-sfc
2, submit the RFC to ovs community
3, debug end-to-end about your code changes.
4, submit the initial patch to networking-sfc
5, submit the initial patch to ovs community
6, submit the initial patch to networking-ovn

Do you have plan to start #1 and #2 now? I think it can be done in parallel 
with the other tasks.
Srilatha and I can start #4 and #6, we need to look at your code changes and 
write the unit test scripts for your code changes and then submit to community, 
what do you think?




Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com<mailto:na...@cn.ibm.com>
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, 
Shanghai, China (201203)



From:John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
To:Na Zhu/China/IBM@IBMCN
Cc:"disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, "OpenStack 
Development Mailing List" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>, Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>
Date:2016/06/06 11:35
Subject:Re: [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC 
andOVN




Juno and team,

I have written and compiled (but not tested ) the ovs/ovn interface to 
networking-ovn and similarly I have written but not tested the IDL interfaces 
on the networking-ovn side. I will put it all together tomorrow and start 
debugging end to end. I know I am going to find a lot of issues as it is a 
major rewrite from my original interface to networking-sfc – it is the right 
path (IMHO) just a little more work than I expected.

I have merged my repos with the upstream masters and I will keep them sync’ed 
so if you want to take a look and start thinking where you can help it would be 
really appreciated.

Regards

John

From: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>
Date: Saturday, June 4, 2016 at 6:30 AM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, OpenStack 
Development Mailing List 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>, Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>
Subject: Re: [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

Hi John,

OK, please keep me posted once you done, thanks very much.




Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com<mailto:na...@cn.ibm.com>
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, 
Shanghai, China (201203)



From:John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
To:Na Zhu/China/IBM@IBMCN
Cc:"disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, "OpenStack 
Development Mailing List" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>, Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>
Date:2016/06/03 13:15
Subject:Re: [ovs

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

[John McDowall]

Juno,

Let me check – my intention was that the networking-sfc OVNB driver would 
configure all aspects of the port-chain and add the parameters to the 
networking-sfc db. Once all the parameters were in the creation of a port-chain 
would call networking-ovn (passing a deep copy of the port-chain dict). Here I 
see networking-ovn acting only as a bridge into ovs/ovn (I did not add anything 
in the ovn plugin – not sure if that is the right approach). Networking-ovn 
calls into ovs/ovn and inserts the entire port-chain.

Thoughts?

j

From: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>
Date: Monday, June 6, 2016 at 5:49 AM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, Ryan Moats 
<rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>, Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>, "OpenStack Development 
Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] 
[networking-sfc] SFC andOVN

Hi John,

One question need confirm with you, I think the ovn flow classifier driver and 
ovn port chain driver should call the APIs which you add to networking-ovn to 
configure the northbound db sfc tables, right? I see your networking-sfc ovn 
drivers, they does not call the APIs you add to networking-ovn, do you miss 
that?



Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com<mailto:na...@cn.ibm.com>
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, 
Shanghai, China (201203)



From:Na Zhu/China/IBM@IBMCN
To:John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc:Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>, OpenStack Development 
Mailing List 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>, 
"disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>
Date:2016/06/06 14:28
Subject:Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn]
[networking-sfc] SFC andOVN




John,

Thanks your working overtime in last weekend, now we have the following works 
to do:
1, submit design spec to networking-sfc
2, submit the RFC to ovs community
3, debug end-to-end about your code changes.
4, submit the initial patch to networking-sfc
5, submit the initial patch to ovs community
6, submit the initial patch to networking-ovn

Do you have plan to start #1 and #2 now? I think it can be done in parallel 
with the other tasks.
Srilatha and I can start #4 and #6, we need to look at your code changes and 
write the unit test scripts for your code changes and then submit to community, 
what do you think?




Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com<mailto:na...@cn.ibm.com>
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, 
Shanghai, China (201203)



From:John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
To:Na Zhu/China/IBM@IBMCN
Cc:"disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, "OpenStack 
Development Mailing List" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>, Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>
Date:2016/06/06 11:35
Subject:Re: [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC 
andOVN




Juno and team,

I have written and compiled (but not tested ) the ovs/ovn interface to 
networking-ovn and similarly I have written but not tested the IDL interfaces 
on the networking-ovn side. I will put it all together tomorrow and start 
debugging end to end. I know I am going to find a lot of issues as it is a 
major rewrite from my original interface to networking-sfc – it is the right 
path (IMHO) just a little more work than I expected.

I have merged my repos with the upstream masters and I will keep them sync’ed 
so if you want to take a look and start thinking where you can help it would be 
really appreciated.

Regards

John

From: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>
Date: Saturday, June

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

[John McDowall]

Juno and team,

I have written and compiled (but not tested ) the ovs/ovn interface to 
networking-ovn and similarly I have written but not tested the IDL interfaces 
on the networking-ovn side. I will put it all together tomorrow and start 
debugging end to end. I know I am going to find a lot of issues as it is a 
major rewrite from my original interface to networking-sfc – it is the right 
path (IMHO) just a little more work than I expected.

I have merged my repos with the upstream masters and I will keep them sync’ed 
so if you want to take a look and start thinking where you can help it would be 
really appreciated.

Regards

John

From: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>
Date: Saturday, June 4, 2016 at 6:30 AM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, OpenStack 
Development Mailing List 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>, Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>
Subject: Re: [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

Hi John,

OK, please keep me posted once you done, thanks very much.




Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com<mailto:na...@cn.ibm.com>
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, 
Shanghai, China (201203)



From:John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
To:Na Zhu/China/IBM@IBMCN
Cc:"disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, "OpenStack 
Development Mailing List" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>, Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>
Date:2016/06/03 13:15
Subject:Re: [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC 
andOVN




Juno

Whatever gets it done faster- let me get the three repos aligned. I need to get 
the ovs/ovn work done so networking-ovn can call it, and the networking-sfc can 
call networking-ovn.

Hopefully I will have it done tomorrow or over the weekend - let's touch base 
Monday or Sunday night.

Regards

John

Sent from my iPhone

On Jun 2, 2016, at 6:30 PM, Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>> 
wrote:

Hi John,

I agree with submitting WIP patches to community, because you already did many 
works on networking-sfc and networking-ovn, it is better that you submit the 
initial patches about networking-sfc and networking-ovn, then me and Srilatha 
take over the patches. Do you have time to do it? if not, me and Srilatha can 
help to do it and you are always the co-author.




Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com<mailto:na...@cn.ibm.com>
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, 
Shanghai, China (201203)



From:John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
To:Na Zhu/China/IBM@IBMCN
Cc:"disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, "OpenStack 
Development Mailing List" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>, Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>
Date:2016/06/03 00:08
Subject:Re: [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC 
andOVN




Juno,

Sure make sense. I will have ovs/ovn in rough shape by end of week (hopefully) 
that will allow you to call the interfaces from networking-ovn. Ryan has asked 
that we submit WIP patches etc so hopefully that will kickstart the review 
process.
Also, hopefully some of the networking-sfc team will also be able to help – I 
will let them speak for themselves.

Regards

John

From: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>
Date: Wednesday, June 1, 2016 at 7:02 PM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, OpenStack 
Development Mailing List 
<

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

[John McDowall]

Juno

Whatever gets it done faster- let me get the three repos aligned. I need to get 
the ovs/ovn work done so networking-ovn can call it, and the networking-sfc can 
call networking-ovn.

Hopefully I will have it done tomorrow or over the weekend - let's touch base 
Monday or Sunday night.

Regards

John

Sent from my iPhone

On Jun 2, 2016, at 6:30 PM, Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>> 
wrote:

Hi John,

I agree with submitting WIP patches to community, because you already did many 
works on networking-sfc and networking-ovn, it is better that you submit the 
initial patches about networking-sfc and networking-ovn, then me and Srilatha 
take over the patches. Do you have time to do it? if not, me and Srilatha can 
help to do it and you are always the co-author.




Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com<mailto:na...@cn.ibm.com>
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, 
Shanghai, China (201203)



From:    John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
To:Na Zhu/China/IBM@IBMCN
Cc:"disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, "OpenStack 
Development Mailing List" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>, Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>
Date:2016/06/03 00:08
Subject:Re: [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC 
andOVN




Juno,

Sure make sense. I will have ovs/ovn in rough shape by end of week (hopefully) 
that will allow you to call the interfaces from networking-ovn. Ryan has asked 
that we submit WIP patches etc so hopefully that will kickstart the review 
process.
Also, hopefully some of the networking-sfc team will also be able to help – I 
will let them speak for themselves.

Regards

John

From: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>
Date: Wednesday, June 1, 2016 at 7:02 PM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, OpenStack 
Development Mailing List 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>, Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>
Subject: Re: [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

Hi John,

Thanks your reply.

Seems you have covered everything :)
The development work can be broken down in 3 parts:
1, add ovn driver to networking-sfc
2, provide APIs in networking-ovn for networking-sfc
3, implement the sfc in ovn

So what about we take part 1 and part 2, and you take part 3? because we are 
familiar with networking-sfc and networking-ovn and we can do it faster:)





Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com<mailto:na...@cn.ibm.com>
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, 
Shanghai, China (201203)



From:John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
To:Na Zhu/China/IBM@IBMCN
Cc:Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>, OpenStack 
Development Mailing List 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
"disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>
Date:2016/06/01 23:26
Subject:Re: [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC 
andOVN




Na/Srilatha,

Great, I am working from three repos:

https://github.com/doonhammer/networking-sfc<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_doonhammer_networking-2Dsfc=CwMFoQ=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo=vZ6VUDaavDpfOdPQrz1ED54jEjvAE36A8TVJroVlrOQ=lb7sZo6o-vFSQLHy4n1Z15SjFlZHXBjYRDDXk9di20M=-ddZLbnKqv3LwRqTTveuebbVLL9e2A1xRCQBQO--nc0=>
https://github.com/doonhammer/networking-ovn<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_doonhammer_networking-2Dovn=CwMFoQ=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo=vZ6VUDaavDpfOdPQrz1ED54jEjvAE36A8TVJroVlrOQ=lb7sZo6o-vFSQLHy4n1Z15SjFlZHXBjYRDDXk9di20M=4XnntcfVxo4fQdni-WOsfqIeRA0x8jagW77y_XgPyUQ=>
https://github.com/doonhammer/

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

[John McDowall]

Juno,

Sure make sense. I will have ovs/ovn in rough shape by end of week (hopefully) 
that will allow you to call the interfaces from networking-ovn. Ryan has asked 
that we submit WIP patches etc so hopefully that will kickstart the review 
process.
Also, hopefully some of the networking-sfc team will also be able to help – I 
will let them speak for themselves.

Regards

John

From: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>
Date: Wednesday, June 1, 2016 at 7:02 PM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, OpenStack 
Development Mailing List 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>, Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>
Subject: Re: [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

Hi John,

Thanks your reply.

Seems you have covered everything :)
The development work can be broken down in 3 parts:
1, add ovn driver to networking-sfc
2, provide APIs in networking-ovn for networking-sfc
3, implement the sfc in ovn

So what about we take part 1 and part 2, and you take part 3? because we are 
familiar with networking-sfc and networking-ovn and we can do it faster:)





Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com<mailto:na...@cn.ibm.com>
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, 
Shanghai, China (201203)



From:John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
To:Na Zhu/China/IBM@IBMCN
Cc:Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>, OpenStack 
Development Mailing List 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
"disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>
Date:2016/06/01 23:26
Subject:Re: [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC 
andOVN




Na/Srilatha,

Great, I am working from three repos:

https://github.com/doonhammer/networking-sfc<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_doonhammer_networking-2Dsfc=CwMFoQ=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo=vZ6VUDaavDpfOdPQrz1ED54jEjvAE36A8TVJroVlrOQ=lb7sZo6o-vFSQLHy4n1Z15SjFlZHXBjYRDDXk9di20M=-ddZLbnKqv3LwRqTTveuebbVLL9e2A1xRCQBQO--nc0=>
https://github.com/doonhammer/networking-ovn<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_doonhammer_networking-2Dovn=CwMFoQ=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo=vZ6VUDaavDpfOdPQrz1ED54jEjvAE36A8TVJroVlrOQ=lb7sZo6o-vFSQLHy4n1Z15SjFlZHXBjYRDDXk9di20M=4XnntcfVxo4fQdni-WOsfqIeRA0x8jagW77y_XgPyUQ=>
https://github.com/doonhammer/ovs<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_doonhammer_ovs=CwMFoQ=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo=vZ6VUDaavDpfOdPQrz1ED54jEjvAE36A8TVJroVlrOQ=lb7sZo6o-vFSQLHy4n1Z15SjFlZHXBjYRDDXk9di20M=vPrUbDdQZ1mIswNv5U8VorIkCU_J5Aze8xGz5DLn_s8=>

I had an original prototype working that used an API I created. Since then, 
based on feedback from everyone I have been moving the API to the 
networking-sfc model and then supporting that API in networking-ovn and 
ovs/ovn. I have created a new driver in networking-sfc for ovn.

I am in the process of moving networking-ovn and ovs to support the sfc model. 
Basically I am intending to pass a deep copy of the port-chain (sample 
attached, sfc_dict.py) from the ovn driver in networking-sfc to networking-ovn. 
 This , as Ryan pointed out will minimize the dependancies between 
networking-sfc and networking-ovn. I have created additional schema for ovs/ovn 
(attached) that will provide the linkage between networking-ovn and ovs/ovn. I 
have the schema in ovs/ovn and I am in the process of  updating my code to 
support it.

Not sure where you guys want to jump in – but I can help in any way you need.

Regards

John

From: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>
Date: Tuesday, May 31, 2016 at 9:02 PM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>, OpenStack 
Development Mailing List 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
"disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, Srilatha Tangirala 
<srila..

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

[John McDowall]

Ryan,

Sure - may need some help and it will probably be next week before I get to it.

Regards

John

From: Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
Date: Wednesday, June 1, 2016 at 1:25 PM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: Ben Pfaff <b...@ovn.org<mailto:b...@ovn.org>>, 
"disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, Justin Pettit 
<jpet...@ovn.org<mailto:jpet...@ovn.org>>, OpenStack Development Mailing List 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
Russell Bryant <russ...@ovn.org<mailto:russ...@ovn.org>>
Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN


John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>> wrote 
on 05/31/2016 07:57:02 PM:

> From: John McDowall 
> <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: Ben Pfaff <b...@ovn.org<mailto:b...@ovn.org>>, 
> "disc...@openvswitch.org<mailto:disc...@openvswitch.org>"
> <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, Justin Pettit 
> <jpet...@ovn.org<mailto:jpet...@ovn.org>>,
> "OpenStack Development Mailing List"  d...@lists.openstack.org<mailto:d...@lists.openstack.org>>, Russell Bryant 
> <russ...@ovn.org<mailto:russ...@ovn.org>>
> Date: 05/31/2016 07:57 PM
> Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN
>
> Ryan,
>
> More help is always great :-). As far as who to collaborate, what
> ever Is easiest for everyone - I am pretty flexible.
>
> Regards
>
> John

Ok, then I'll ask that we go the submit WIP patches to each of
networking-sfc and networking-ovn and an RFC patch to 
d...@openvswitch.org<mailto:d...@openvswitch.org>
and iterate through review.openstack.org and patchworks.

Could you submit the initial patches today or tomorrow? I'd rather
go that route since you have the lion's share of the work so far
and credit where credit is due...

Ryan
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

[John McDowall]

Na/Srilatha,

Great, I am working from three repos:

https://github.com/doonhammer/networking-sfc
https://github.com/doonhammer/networking-ovn
https://github.com/doonhammer/ovs

I had an original prototype working that used an API I created. Since then, 
based on feedback from everyone I have been moving the API to the 
networking-sfc model and then supporting that API in networking-ovn and 
ovs/ovn. I have created a new driver in networking-sfc for ovn.

I am in the process of moving networking-ovn and ovs to support the sfc model. 
Basically I am intending to pass a deep copy of the port-chain (sample 
attached, sfc_dict.py) from the ovn driver in networking-sfc to networking-ovn. 
 This , as Ryan pointed out will minimize the dependancies between 
networking-sfc and networking-ovn. I have created additional schema for ovs/ovn 
(attached) that will provide the linkage between networking-ovn and ovs/ovn. I 
have the schema in ovs/ovn and I am in the process of  updating my code to 
support it.

Not sure where you guys want to jump in – but I can help in any way you need.

Regards

John

From: Na Zhu <na...@cn.ibm.com<mailto:na...@cn.ibm.com>>
Date: Tuesday, May 31, 2016 at 9:02 PM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>, OpenStack 
Development Mailing List 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
"disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, Srilatha Tangirala 
<srila...@us.ibm.com<mailto:srila...@us.ibm.com>>
Subject: Re: [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

+ Add Srilatha.



Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com<mailto:na...@cn.ibm.com>
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, 
Shanghai, China (201203)



From:Na Zhu/China/IBM
To:John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc:Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>, OpenStack 
Development Mailing List 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
"disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>
Date:2016/06/01 12:01
Subject:Re: [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC 
andOVN



John,

Thanks.

Me and Srilatha (srila...@us.ibm.com<mailto:srila...@us.ibm.com>) want to 
working together with you, I know you already did some development works.
Can you tell me what you have done and put the latest code in your private repo?
Can we work out a plan and the remaining work?




Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com<mailto:na...@cn.ibm.com>
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, 
Shanghai, China (201203)




From:John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
To:Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
Cc:OpenStack Development Mailing List 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
"disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>
Date:2016/06/01 08:58
Subject:Re: [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC 
andOVN
Sent by:"discuss" 
<discuss-boun...@openvswitch.org<mailto:discuss-boun...@openvswitch.org>>
____



Ryan,

More help is always great :-). As far as who to collaborate, what ever Is 
easiest for everyone – I am pretty flexible.

Regards

John

From: Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
Date: Tuesday, May 31, 2016 at 1:59 PM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: Ben Pfaff <b...@ovn.org<mailto:b...@ovn.org>>, 
"disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, Justin Pettit 
<jpet...@ovn.org<mailto:jpet...@ovn.org>>, OpenStack Development Mailing List 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
Russell Bryant <russ...@ovn.org<mailto:russ...@ovn.org>>
Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN

John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow.

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

[John McDowall]

Ryan,

More help is always great :-). As far as who to collaborate, what ever Is 
easiest for everyone – I am pretty flexible.

Regards

John

From: Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
Date: Tuesday, May 31, 2016 at 1:59 PM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: Ben Pfaff <b...@ovn.org<mailto:b...@ovn.org>>, 
"disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, Justin Pettit 
<jpet...@ovn.org<mailto:jpet...@ovn.org>>, OpenStack Development Mailing List 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
Russell Bryant <russ...@ovn.org<mailto:russ...@ovn.org>>
Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN


John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>> wrote 
on 05/31/2016 03:21:30 PM:

> From: John McDowall 
> <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: Ben Pfaff <b...@ovn.org<mailto:b...@ovn.org>>, 
> "disc...@openvswitch.org<mailto:disc...@openvswitch.org>"
> <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, Justin Pettit 
> <jpet...@ovn.org<mailto:jpet...@ovn.org>>,
> "OpenStack Development Mailing List"  d...@lists.openstack.org<mailto:d...@lists.openstack.org>>, Russell Bryant 
> <russ...@ovn.org<mailto:russ...@ovn.org>>
> Date: 05/31/2016 03:22 PM
> Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN
>
> Ryan,
>
> Let me add the tables to OVN for SFC. That will give us a working
> system to prototype the flow classifier approach on. Hopefully I can
> get something done by end of week.
>
> Regards
>
> John

I've got some internal folks that are willing to help with writing code (as
I will be once I clear my current firefights) so the question of how to
collaborate with code now arises...

Are you comfortable with putting the changes on r.o.o as WiP and patchworks
as RFC and work through the review process or would you rather work via
forks and pull requests in github?

Ryan

> From: Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
> Date: Tuesday, May 31, 2016 at 10:17 AM
> To: John McDowall 
> <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
> Cc: Ben Pfaff <b...@ovn.org<mailto:b...@ovn.org>>, 
> "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" <
> disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, Justin Pettit 
> <jpet...@ovn.org<mailto:jpet...@ovn.org>>, OpenStack
> Development Mailing List 
> <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>,
>  Russell Bryant <
> russ...@ovn.org<mailto:russ...@ovn.org>>
> Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN
>
> John McDowall 
> <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>> wrote 
> on 05/26/2016
> 11:08:43 AM:
>
> > From: John McDowall 
> > <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
> > To: Ryan Moats/Omaha/IBM@IBMUS
> > Cc: Ben Pfaff <b...@ovn.org<mailto:b...@ovn.org>>, 
> > "disc...@openvswitch.org<mailto:disc...@openvswitch.org>"
> > <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, Justin Pettit 
> > <jpet...@ovn.org<mailto:jpet...@ovn.org>>,
> > "OpenStack Development Mailing List"  > d...@lists.openstack.org<mailto:d...@lists.openstack.org>>, Russell Bryant 
> > <russ...@ovn.org<mailto:russ...@ovn.org>>
> > Date: 05/26/2016 11:09 AM
> > Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN
> >
> > Ryan,
> >
> > My (incomplete) throughts about the flow-classifier are:
> >
> > 1)  ACL’s are more about denying access, while the flow classifier
> > is more about steering selected traffic to a path, so we would need
> > to deny-all except allowed flows.
> > 2)  The networking-sfc team has done a nice job with the drivers so
> > ovn has its own flow-classifier driver which allows us to align the
> > flow-classifier with the matches supported in ovs/ovn, which could
> > be an advantage.
>
> The ACL table has a very simple flow-classifier structure and I'd
> like to see if that can be re-used for the purpose of the SFC classifier
> (read that I feel the Logical_Flow_Classifier table is to

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

[John McDowall]

Ryan,

Let me add the tables to OVN for SFC. That will give us a working system to 
prototype the flow classifier approach on. Hopefully I can get something done 
by end of week.

Regards

John

From: Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
Date: Tuesday, May 31, 2016 at 10:17 AM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: Ben Pfaff <b...@ovn.org<mailto:b...@ovn.org>>, 
"disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, Justin Pettit 
<jpet...@ovn.org<mailto:jpet...@ovn.org>>, OpenStack Development Mailing List 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
Russell Bryant <russ...@ovn.org<mailto:russ...@ovn.org>>
Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN


John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>> wrote 
on 05/26/2016 11:08:43 AM:

> From: John McDowall 
> <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: Ben Pfaff <b...@ovn.org<mailto:b...@ovn.org>>, 
> "disc...@openvswitch.org<mailto:disc...@openvswitch.org>"
> <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, Justin Pettit 
> <jpet...@ovn.org<mailto:jpet...@ovn.org>>,
> "OpenStack Development Mailing List"  d...@lists.openstack.org<mailto:d...@lists.openstack.org>>, Russell Bryant 
> <russ...@ovn.org<mailto:russ...@ovn.org>>
> Date: 05/26/2016 11:09 AM
> Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN
>
> Ryan,
>
> My (incomplete) throughts about the flow-classifier are:
>
> 1)  ACL’s are more about denying access, while the flow classifier
> is more about steering selected traffic to a path, so we would need
> to deny-all except allowed flows.
> 2)  The networking-sfc team has done a nice job with the drivers so
> ovn has its own flow-classifier driver which allows us to align the
> flow-classifier with the matches supported in ovs/ovn, which could
> be an advantage.

The ACL table has a very simple flow-classifier structure and I'd
like to see if that can be re-used for the purpose of the SFC classifier
(read that I feel the Logical_Flow_Classifier table is too complex).
My initial thoughts were to look at extending the action column and
using the external-ids field to differentiate between legacy ACLs and
those that are used to intercept traffic and route it to an SFC.

>
> What were your thoughts on the schema it adds a lot of tables and a
> lot of commands – cannot think of anyway around it

In this case, I think that the other tables are reasonable and I'm
uncomfortable trying to stretch the existing tables to cover that
information...

Ryan

>
> Regards
>
> John
>
> From: Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
> Date: Wednesday, May 25, 2016 at 9:12 PM
> To: John McDowall 
> <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
> Cc: Ben Pfaff <b...@ovn.org<mailto:b...@ovn.org>>, 
> "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" <
> disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, Justin Pettit 
> <jpet...@ovn.org<mailto:jpet...@ovn.org>>, OpenStack
> Development Mailing List 
> <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>,
>  Russell Bryant <
> russ...@ovn.org<mailto:russ...@ovn.org>>
> Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN
>
> John McDowall 
> <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>> wrote 
> on 05/25/2016
> 07:27:46 PM:
>
> > From: John McDowall 
> > <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
> > To: Ryan Moats/Omaha/IBM@IBMUS
> > Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
> > <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, "OpenStack
> > Development Mailing List" 
> > <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>,
> >  Ben
> > Pfaff <b...@ovn.org<mailto:b...@ovn.org>>, Justin Pettit 
> > <jpet...@ovn.org<mailto:jpet...@ovn.org>>, Russell Bryant
> > <russ...@ovn.org<mailto:russ...@ovn.org>>
> > Date: 05/25/2016 07:28 PM
> > Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN
> >
> > Ryan,
> >
> > Ok – I will let the exp

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

[John McDowall]

Ryan,

Hopefully – just wanted to make sure it was there.

Regards

John

From: Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
Date: Tuesday, May 31, 2016 at 10:02 AM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: Ben Pfaff <b...@ovn.org<mailto:b...@ovn.org>>, 
"disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, Justin Pettit 
<jpet...@ovn.org<mailto:jpet...@ovn.org>>, OpenStack Development Mailing List 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
Russell Bryant <russ...@ovn.org<mailto:russ...@ovn.org>>
Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN


John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>> wrote 
on 05/26/2016 10:59:48 AM:

> From: John McDowall 
> <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
> To: Ryan Moats/Omaha/IBM@IBMUS, Ben Pfaff <b...@ovn.org<mailto:b...@ovn.org>>
> Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
> <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, Justin
> Pettit <jpet...@ovn.org<mailto:jpet...@ovn.org>>, OpenStack Development 
> Mailing List
> <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>,
>  Russell Bryant <russ...@ovn.org<mailto:russ...@ovn.org>>
> Date: 05/26/2016 11:00 AM
> Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN
>
> Ryan,
>
> Agree with your description of the problem. The only thing I would
> add is that in the case of bi-directional chains the return flows
> need to go through the same VNF(Port-pair).

I'm pretty sure that is caught automagically, isn't it?

Ryan

>
> Regards
>
> John
>
> From: Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
> Date: Wednesday, May 25, 2016 at 9:29 PM
> To: Ben Pfaff <b...@ovn.org<mailto:b...@ovn.org>>
> Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
> <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, John McDowall <
> jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>, 
> Justin Pettit <jpet...@ovn.org<mailto:jpet...@ovn.org>>,
> OpenStack Development Mailing List 
> <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>
> >, Russell Bryant <russ...@ovn.org<mailto:russ...@ovn.org>>
> Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN
>
> Ben Pfaff <b...@ovn.org<mailto:b...@ovn.org>> wrote on 05/25/2016 07:44:43 PM:
>
> > From: Ben Pfaff <b...@ovn.org<mailto:b...@ovn.org>>
> > To: Ryan Moats/Omaha/IBM@IBMUS
> > Cc: John McDowall 
> > <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>,
> > "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
> > <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, OpenStack
> > Development Mailing List 
> > <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>,
> >  Justin
> > Pettit <jpet...@ovn.org<mailto:jpet...@ovn.org>>, Russell Bryant 
> > <russ...@ovn.org<mailto:russ...@ovn.org>>
> > Date: 05/25/2016 07:44 PM
> > Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN
> >
> > On Wed, May 25, 2016 at 09:27:31AM -0500, Ryan Moats wrote:
> > > As I understand it, Table 0 identifies the logical port and logical
> > > flow. I'm worried that this means we'll end up with separate bucket
> > > rules for each ingress port of the port pairs that make up a port
> > > group, leading to a cardinality product in the number of rules.
> > > I'm trying to think of a way where Table 0 could identify the packet
> > > as being part of a particular port group, and then I'd only need one
> > > set of bucket rules to figure out the egress side.  However, the
> > > amount of free metadata space is limited and so before we go down
> > > this path, I'm going to pull Justin, Ben and Russell in to see if
> > > they buy into this idea or if they can think of an alternative.
> >
> > I've barely been following the discussion, so a recap of the question
> > here would help a lot.
> >
>
> Sure (and John gets to correct me where I'm wrong) - the SFC proposal
> is to carry a chain as a ordered set of port groups, where each group
> consists of mu

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

[John McDowall]

Ryan,

My (incomplete) throughts about the flow-classifier are:

1)  ACL’s are more about denying access, while the flow classifier is more 
about steering selected traffic to a path, so we would need to deny-all except 
allowed flows.
2)  The networking-sfc team has done a nice job with the drivers so ovn has its 
own flow-classifier driver which allows us to align the flow-classifier with 
the matches supported in ovs/ovn, which could be an advantage.

What were your thoughts on the schema it adds a lot of tables and a lot of 
commands – cannot think of anyway around it

Regards

John

From: Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
Date: Wednesday, May 25, 2016 at 9:12 PM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: Ben Pfaff <b...@ovn.org<mailto:b...@ovn.org>>, 
"disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, Justin Pettit 
<jpet...@ovn.org<mailto:jpet...@ovn.org>>, OpenStack Development Mailing List 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
Russell Bryant <russ...@ovn.org<mailto:russ...@ovn.org>>
Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN


John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>> wrote 
on 05/25/2016 07:27:46 PM:

> From: John McDowall 
> <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
> <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, "OpenStack
> Development Mailing List" 
> <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>,
>  Ben
> Pfaff <b...@ovn.org<mailto:b...@ovn.org>>, Justin Pettit 
> <jpet...@ovn.org<mailto:jpet...@ovn.org>>, Russell Bryant
> <russ...@ovn.org<mailto:russ...@ovn.org>>
> Date: 05/25/2016 07:28 PM
> Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN
>
> Ryan,
>
> Ok – I will let the experts weigh in on load balancing.
>
> In the meantime I have attached a couple of files to show where I am
> going. The first is sfc_dict.py and is a representation of the dict
> I am passing from SFC to OVN. This will then translate to the
> attached ovn-nb schema file.
>
> One of my concerns is that SFC almost doubles the size of the ovn-nb
> schema but I could not think of any other way of doing it.
>
> Thoughts?
>
> John

The dictionary looks fine for a starting point, and the more I look
at the classifier, the more I wonder if we can't do something with
the current ACL table to avoid duplication in the NB database
definition...

Ryan

> From: Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
> Date: Wednesday, May 25, 2016 at 7:27 AM
> To: John McDowall 
> <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
> Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
> <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, OpenStack
> Development Mailing List 
> <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>,
>  Ben Pfaff <
> b...@ovn.org<mailto:b...@ovn.org>>, Justin Pettit 
> <jpet...@ovn.org<mailto:jpet...@ovn.org>>, Russell Bryant 
> <russ...@ovn.org<mailto:russ...@ovn.org>
> >
> Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN
>
> John McDowall 
> <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>> wrote 
> on 05/24/2016
> 06:33:05 PM:
>
> > From: John McDowall 
> > <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
> > To: Ryan Moats/Omaha/IBM@IBMUS
> > Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
> > <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, "OpenStack
> > Development Mailing List" 
> > <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
> > Date: 05/24/2016 06:33 PM
> > Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN
> >
> > Ryan,
> >
> > Thanks for getting back to me and pointing me in a more OVS like
> > direction. What you say makes sense, let me hack something together.
> > I have been a little distracted getting some use cases together. The
> > other area is how to better map the flow-classifier I have been
> > thinking about it a little, but I wil

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

[John McDowall]

Ryan,

Ok – I will let the experts weigh in on load balancing.

In the meantime I have attached a couple of files to show where I am going. The 
first is sfc_dict.py and is a representation of the dict I am passing from SFC 
to OVN. This will then translate to the attached ovn-nb schema file.

One of my concerns is that SFC almost doubles the size of the ovn-nb schema but 
I could not think of any other way of doing it.

Thoughts?

John

From: Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
Date: Wednesday, May 25, 2016 at 7:27 AM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, OpenStack 
Development Mailing List 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, 
Ben Pfaff <b...@ovn.org<mailto:b...@ovn.org>>, Justin Pettit 
<jpet...@ovn.org<mailto:jpet...@ovn.org>>, Russell Bryant 
<russ...@ovn.org<mailto:russ...@ovn.org>>
Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN


John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>> wrote 
on 05/24/2016 06:33:05 PM:

> From: John McDowall 
> <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
> <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, "OpenStack
> Development Mailing List" 
> <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
> Date: 05/24/2016 06:33 PM
> Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN
>
> Ryan,
>
> Thanks for getting back to me and pointing me in a more OVS like
> direction. What you say makes sense, let me hack something together.
> I have been a little distracted getting some use cases together. The
> other area is how to better map the flow-classifier I have been
> thinking about it a little, but I will leave it till after we get
> the chains done.
>
> Your load-balancing comment was very interesting – I saw some
> patches for load-balancing a few months ago but nothing since. It
> would be great if we could align with load-balancing as that would
> make a really powerful solution.
>
> Regards
>
> John

John-

For the load balancing, I believe that you'll want to look at
openvswitch's select group, as that should let you set up multiple
buckets for each egress port in the port pairs that make up a port
group.

As I understand it, Table 0 identifies the logical port and logical
flow. I'm worried that this means we'll end up with separate bucket
rules for each ingress port of the port pairs that make up a port
group, leading to a cardinality product in the number of rules.
I'm trying to think of a way where Table 0 could identify the packet
as being part of a particular port group, and then I'd only need one
set of bucket rules to figure out the egress side.  However, the
amount of free metadata space is limited and so before we go down
this path, I'm going to pull Justin, Ben and Russell in to see if
they buy into this idea or if they can think of an alternative.

Ryan

>
> From: Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
> Date: Monday, May 23, 2016 at 9:06 PM
> To: John McDowall 
> <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
> Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
> <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, OpenStack
> Development Mailing List 
> <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
> Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN
>
> John McDowall 
> <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>> wrote 
> on 05/18/2016
> 03:55:14 PM:
>
> > From: John McDowall 
> > <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
> > To: Ryan Moats/Omaha/IBM@IBMUS
> > Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
> > <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, "OpenStack
> > Development Mailing List" 
> > <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
> > Date: 05/18/2016 03:55 PM
> > Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN
> >
> > Ryan,
> >
> > OK all three repos and now aligned with their masters. I have done
> > some simple level sy

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

[John McDowall]

Ryan,

Thanks for getting back to me and pointing me in a more OVS like direction. 
What you say makes sense, let me hack something together. I have been a little 
distracted getting some use cases together. The other area is how to better map 
the flow-classifier I have been thinking about it a little, but I will leave it 
till after we get the chains done.

Your load-balancing comment was very interesting - I saw some patches for 
load-balancing a few months ago but nothing since. It would be great if we 
could align with load-balancing as that would make a really powerful solution.

Regards

John

From: Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
Date: Monday, May 23, 2016 at 9:06 PM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, OpenStack 
Development Mailing List 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN


John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>> wrote 
on 05/18/2016 03:55:14 PM:

> From: John McDowall 
> <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
> <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, "OpenStack
> Development Mailing List" 
> <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
> Date: 05/18/2016 03:55 PM
> Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN
>
> Ryan,
>
> OK all three repos and now aligned with their masters. I have done
> some simple level system tests and I can steer traffic to a single
> VNF.  Note: some additional changes to networking-sfc to catch-up
> with their changes.
>
> https://github.com/doonhammer/networking-sfc<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_doonhammer_networking-2Dsfc=CwMFAg=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo=vZ6VUDaavDpfOdPQrz1ED54jEjvAE36A8TVJroVlrOQ=X45gSToRX1EVBP46eiE4I1RVkHHGNs1au5VI5t81C28=4rDDNTnH__xTc1IzAFZc8Uj2MT4ptJqbknR5Y48CFVQ=>
> https://github.com/doonhammer/networking-ovn<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_doonhammer_networking-2Dovn=CwMFAg=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo=vZ6VUDaavDpfOdPQrz1ED54jEjvAE36A8TVJroVlrOQ=X45gSToRX1EVBP46eiE4I1RVkHHGNs1au5VI5t81C28=VMEOCnJuSfOXTVqu9kDOICcoXk6Ch-kH3CA2XJh6uug=>
> https://github.com/doonhammer/ovs<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_doonhammer_ovs=CwMFAg=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo=vZ6VUDaavDpfOdPQrz1ED54jEjvAE36A8TVJroVlrOQ=X45gSToRX1EVBP46eiE4I1RVkHHGNs1au5VI5t81C28=gTurnZdJqSewDIP5xIznZdOvsX53iWIjKTsu0gDyCYM=>
>
> The next tasks I see are:
>
> 1. Decouple networking-sfc and networking-ovn. I am thinking that I
> will pass a nested port-chain dictionary holding port-pairs/port-
> pair-groups/flow-classifiers from networking-sfc to networking-ovn.
> 2. Align the interface between networking-ovn and ovs/ovn to match
> the nested dictionary in 1.
> 3. Modify the ovn-nb schema and ovn-northd.c to march the port-chain model.
> 4. Add ability to support chain of port-pairs
> 5. Think about flow-classifiers and how best to map them, today I
> just map the logical-port and ignore everything else.
>
> Any other suggestions/feedback?
>
> Regards
>
> John

John-

(Sorry for sending this twice, but I forgot that text/html is not liked
by the mailing lists ...)

My apologies for not answering this sooner - I was giving a two day
training on Tues/Wed last week and came back to my son graduating
from HS the next day, so things have been a bit of a whirlwind here.

Looking at the github repos, I like the idea of passing a dictionary
from networking-sfc to networking-ovn. The flow classifiers should
be relatively straightforward to map to ovs match rules (famous last
words)...

I've probably missed an orbit here, but in the ovn-northd implementation,
I was expecting to find service chains in the egress and router pipelines
in addition to the ingress pipeline (see below for why I think a service
chain stage in the egress pipeline makes sense ...)

Also, in the ovn-northd implementation, I'm a little disturbed to see the
ingress side of the service chain sending packets to output ports - I
think that a more scalable (and more "ovs-like" approach) would be to
match the egress side of a port pair in the chaining stage of the
ingress pipeline, with an action that  set the input port register.
Then the egress pipeline 

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

[John McDowall]

Ryan,

OK all three repos and now aligned with their masters. I have done some simple 
level system tests and I can steer traffic to a single VNF.  Note: some 
additional changes to networking-sfc to catch-up with their changes.

https://github.com/doonhammer/networking-sfc
https://github.com/doonhammer/networking-ovn
https://github.com/doonhammer/ovs

The next tasks I see are:



  1.  Decouple networking-sfc and networking-ovn. I am thinking that I will 
pass a nested port-chain dictionary holding 
port-pairs/port-pair-groups/flow-classifiers from networking-sfc to 
networking-ovn.
  2.  Align the interface between networking-ovn and ovs/ovn to match the 
nested dictionary in 1.
  3.  Modify the ovn-nb schema and ovn-northd.c to march the port-chain model.
  4.  Add ability to support chain of port-pairs
  5.  Think about flow-classifiers and how best to map them, today I just map 
the logical-port and ignore everything else.

Any other suggestions/feedback?

Regards

John

From: Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
Date: Wednesday, May 11, 2016 at 1:39 PM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, OpenStack 
Development Mailing List 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN


John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>> wrote 
on 05/11/2016 12:37:40 PM:

> From: John McDowall 
> <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
> <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, "OpenStack
> Development Mailing List" 
> <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
> Date: 05/11/2016 12:37 PM
> Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN
>
> Ryan,
>
> I have done networking-sfc the files that I see as changed/added are:
>
> devstack/settings   Modified Runtime setting to pick up OVN Driver
> networking_sfc/db/migration/alembic_migrations/versions/mitaka/
> expand/5a475fc853e6_ovs_data_model.py Hack to work around
> flow_classifier issue - need to resolve with SFC team.
> networking_sfc/services/sfc/drivers/ovn/__init__.py   Added for OVN Driver
> networking_sfc/services/sfc/drivers/ovn/driver.py Added ovn driver file
> setup.cfg Inserted OVN driver entry
>
> I am currently working to clean up ovs/ovn.
>
> Regards
>
> John

I can confirm that the networking-sfc rebase goes in clean against
master for me :) - Looking forward to ovs ...

Ryan
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

[John McDowall]

Ryan,

Looks good apart from:

networking_ovn/common/extensions.py

There should be no changes to that file, I removed them as they are from an 
older prototype.

Regards

John

From: Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
Date: Wednesday, May 11, 2016 at 9:59 AM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, OpenStack 
Development Mailing List 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN


John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>> wrote 
on 05/11/2016 11:30:07 AM:

> From: John McDowall 
> <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
> <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, "OpenStack
> Development Mailing List" 
> <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
> Date: 05/11/2016 11:30 AM
> Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN
>
> Ryan,
>
> Apologies for missing the _init_.py files – removed them and
> remerged. When I do a compare from my repo to main I see three files
> changed (which I think is correct):
>
> networking_ovn/ovsdb/commands.py
> networking_ovn/ovsdb/impl_idl_ovn.py
> networking_ovn/ovsdb/ovn_api.py
>
> I could be doing something wrong as not an expert at merging repos.
> If I am doing something wrong let me know and I will fix it.
>
> Regards
>
> John

So the change I made to common/extensions.py was to avoid a merge
conflict, and I double checked and yes, the changes I had to
plugin.py are spurious, so here is an updated/corrected patch for
you to check against:

>From eb93dc3984145f1b82be15d204c2f0790c1429bd Mon Sep 17 00:00:00 2001
From: RYAN D. MOATS <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
Date: Wed, 11 May 2016 09:10:18 -0500
Subject: [PATCH] test

Signed-off-by: RYAN D. MOATS <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
---
networking_ovn/common/extensions.py  |1 +
networking_ovn/ovsdb/commands.py |   78 ++
networking_ovn/ovsdb/impl_idl_ovn.py |   18 
networking_ovn/ovsdb/ovn_api.py  |   49 +
4 files changed, 146 insertions(+), 0 deletions(-)

diff --git a/networking_ovn/common/extensions.py 
b/networking_ovn/common/extensions.py
index c171e11..55fc147 100644
--- a/networking_ovn/common/extensions.py
+++ b/networking_ovn/common/extensions.py
@@ -37,4 +37,5 @@ SUPPORTED_API_EXTENSIONS = [
'subnet_allocation',
'port-security',
'allowed-address-pairs',
+'sfi',
]
diff --git a/networking_ovn/ovsdb/commands.py b/networking_ovn/ovsdb/commands.py
index 7ea7a6f..68a747f 100644
--- a/networking_ovn/ovsdb/commands.py
+++ b/networking_ovn/ovsdb/commands.py
@@ -164,6 +164,84 @@ class DelLogicalPortCommand(BaseCommand):
setattr(lswitch, 'ports', ports)
self.api._tables['Logical_Port'].rows[lport.uuid].delete()

+class AddLogicalServiceCommand(BaseCommand):
+def __init__(self, api, lservice, lswitch, may_exist, **columns):
+super(AddLogicalServiceCommand, self).__init__(api)
+self.lservice = lservice
+self.lswitch = lswitch
+self.may_exist = may_exist
+self.columns = columns
+
+def run_idl(self, txn):
+try:
+lswitch = idlutils.row_by_value(self.api.idl, 'Logical_Switch',
+'name', self.lswitch)
+services= getattr(lswitch, 'services', [])
+except idlutils.RowNotFound:
+msg = _("Logical Switch %s does not exist") % self.lswitch
+raise RuntimeError(msg)
+if self.may_exist:
+service = idlutils.row_by_value(self.api.idl,
+ 'Logical_Service', 'name',
+ self.lservice, None)
+if service:
+return
+
+lswitch.verify('services')
+
+service = txn.insert(self.api._tables['Logical_Service'])
+service.name = self.lservice
+for col, val in self.columns.items():
+setattr(service, col, val)
+# add the newly created service to existing lswitch
+services.append(service.uuid)
+setattr(lswitch, 'services', services)
+
+class SetLogicalServiceCommand(BaseCommand):
+def __init__(self, api, lservice, if_exists, **columns):
+super(SetLogicalServi

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

[John McDowall]

Ryan,

Apologies for missing the _init_.py files – removed them and remerged. When I 
do a compare from my repo to main I see three files changed (which I think is 
correct):

networking_ovn/ovsdb/commands.py
networking_ovn/ovsdb/impl_idl_ovn.py
networking_ovn/ovsdb/ovn_api.py

I could be doing something wrong as not an expert at merging repos. If I am 
doing something wrong let me know and I will fix it.

Regards

John

From: Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
Date: Wednesday, May 11, 2016 at 7:12 AM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, OpenStack 
Development Mailing List 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN


John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>> wrote 
on 05/10/2016 11:11:57 AM:

> From: John McDowall 
> <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
> <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, "OpenStack
> Development Mailing List" 
> <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
> Date: 05/10/2016 11:12 AM
> Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN
>
> Ryan,
>
> Let me do that – I assume adding them to plugin.py is the right approach.
>
> I have cleaned up 
> https://github.com/doonhammer/networking-ovn<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_doonhammer_networking-2Dovn=CwMGaQ=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo=vZ6VUDaavDpfOdPQrz1ED54jEjvAE36A8TVJroVlrOQ=OnZUOTNe2_owNOAk55Ngsx_q6nlfnk5q4cKw_8EZYUk=bP5OEAy91qoSaK3krK_S9J-Mh1hsS9O8drNgQeWIUQA=>
>  and
> did a merge so it should be a lot easier to see the changes. I am
> going to cleanup ovs/ovn next. Once I have everything cleaned up and
> make sure it is still working I will move the code over to the port-
> pair/port-chain model.
>
> Let me know if that works for you.
>
> Regards
>
> John
>
> From: Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
> Date: Tuesday, May 10, 2016 at 7:38 AM
> To: John McDowall 
> <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
> Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
> <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, OpenStack
> Development Mailing List 
> <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
> Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN
>
> John McDowall 
> <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>> wrote 
> on 05/09/2016
> 10:46:41 AM:
>
> > From: John McDowall 
> > <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
> > To: Ryan Moats/Omaha/IBM@IBMUS
> > Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
> > <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, "OpenStack
> > Development Mailing List" 
> > <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
> > Date: 05/09/2016 10:46 AM
> > Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN
> >
> > Ryan,
> >
> > Thanks – let me try and get the code cleaned up and rebased. One
> > area that I could use your insight on is the interface to
> > networking-ovn and how it should look.
> >
> > Regards
> >
> > John
>
> Looking at this, the initial code that I think should move over are
> _create_ovn_vnf and _delete_ovn_vnf and maybe rename them to
> create_vnf and delete_vnf.
>
> What I haven't figured out at this point is:
> 1) Is the above enough?
> 2) Do we need to refactor some of OVNPlugin's calls to provide hooks
> for the SFC
>driver to use for when the OVNPlugin inheritance goes away.
>
> Ryan

I like the idea, but unfortunately, I'm still not able to apply the series
cleanly to openstack:master:
- the list of supported extensions has moved from plugin.py to
  commons/extensions.py
- the patches that create extensions/__init__.py and
  networking_ovn/db/migration/__init__.py complain of garbage
- the patch that adds Logging on fixed ips doesn't align with the new
  code structure for handling same
- the pat

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

[John McDowall]

Ryan,

Let me do that - I assume adding them to plugin.py is the right approach.

I have cleaned up https://github.com/doonhammer/networking-ovn and did a merge 
so it should be a lot easier to see the changes. I am going to cleanup ovs/ovn 
next. Once I have everything cleaned up and make sure it is still working I 
will move the code over to the port-pair/port-chain model.

Let me know if that works for you.

Regards

John

From: Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
Date: Tuesday, May 10, 2016 at 7:38 AM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, OpenStack 
Development Mailing List 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN


John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>> wrote 
on 05/09/2016 10:46:41 AM:

> From: John McDowall 
> <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
> <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, "OpenStack
> Development Mailing List" 
> <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
> Date: 05/09/2016 10:46 AM
> Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN
>
> Ryan,
>
> Thanks - let me try and get the code cleaned up and rebased. One
> area that I could use your insight on is the interface to
> networking-ovn and how it should look.
>
> Regards
>
> John

Looking at this, the initial code that I think should move over are
_create_ovn_vnf and _delete_ovn_vnf and maybe rename them to
create_vnf and delete_vnf.

What I haven't figured out at this point is:
1) Is the above enough?
2) Do we need to refactor some of OVNPlugin's calls to provide hooks for the SFC
   driver to use for when the OVNPlugin inheritance goes away.

Ryan
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

[John McDowall]

Ryan,

Thanks - let me try and get the code cleaned up and rebased. One area that I 
could use your insight on is the interface to networking-ovn and how it should 
look.

Regards

John

From: Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
Date: Sunday, May 8, 2016 at 8:32 PM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
<disc...@openvswitch.org<mailto:disc...@openvswitch.org>>, OpenStack 
Development Mailing List 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN


John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>> wrote 
on 05/08/2016 07:34:52 PM:

> From: John McDowall 
> <jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: "disc...@openvswitch.org<mailto:disc...@openvswitch.org>" 
> <disc...@openvswitch.org<mailto:disc...@openvswitch.org>>
> Date: 05/08/2016 07:35 PM
> Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN
>
> Correcting ovs address
>
> Ryan,
>
> Thanks for taking a look at these  - really appreciate it. I will
> work on the rebasing this week and get everything current. At the
> same time I can get rid of some excess code as I went through a few
> iterations to get to this point. There are still a lot of
> unaddressed edge conditions and details that need to be thought
> through and addressed - but once we reach consensus on the approach
> we can start to address them.
>
> Thinking though the various repos in reverse order.
>
> OVS
> ===
>
> I would like to change the code to follow the model that Russell
> Bryant did in his patches see:  
> https://github.com/russellb/ovs/<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_russellb_ovs_=CwMGaQ=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo=vZ6VUDaavDpfOdPQrz1ED54jEjvAE36A8TVJroVlrOQ=_f4gjpVAKVX0PU6jpEYOKtT1OLwmrOSgMc0fjASz5JI=VyzaLKG-WTtwNtnzunX-dImm0lA0rUAiYgPMrieHJO4=>
> commits/chaining
>
> They have several advantages:
> 1. Creates a new table for chaining which should help isolate the
> code and make chaining more "atomic"
> 2. He follows the port-pair/port-chain model of SFC so integration
> should be cleaner
> 3. Following the port-pair/port-chain model makes extending the
> solution to handle a chain of VNFs fairly easy.
> If everyone is good with this I can work this into the patches and rebase.

You are anticipating where I was looking to go, so I'm on board with
this idea.

> Networking-OVN
> ===
>
> There is some old code here in plugin.py that I think comes out.
> When I added OVN as a SFC Driver there was a lot of code that I
> added to  networking-ovn that became obsolete. The IDL code would be
> modified to follow the port-pair/port-chain. model.  The biggest
> question I have from your comments is the interface between the
> networking-sfc and networking-ovn. I think I agree with you that
> networking-ovn should expose an interface that is called by
> networking-sfc and that would remove the need to subclass OVNPlugin
> in the networking-sfc OVN driver. Is that what you were intending?

Yes, I was looking at how that subclass could be avoided.

> Networking-SFC
> ==
>
> If we follow Russell's model in OVN/OVS then there very close
> alignment with the SFC model and the code will become simpler. Also
> removing the OVNPlugin dependency will also clean things up.

Yes, I was hoping that would be a side effect as well...

I like all of your proposed ideas and am looking forward to seeing
the next iteration. Please feel free to reach out if you need
another pair of hands to help with coding...

Ryan Moats
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

[John McDowall]

Ryan,

Thanks for taking a look at these  - really appreciate it. I will work on the 
rebasing this week and get everything current. At the same time I can get rid 
of some excess code as I went through a few iterations to get to this point. 
There are still a lot of unaddressed edge conditions and details that need to 
be thought through and addressed – but once we reach consensus on the approach 
we can start to address them.

Thinking though the various repos in reverse order.

OVS
===

I would like to change the code to follow the model that Russell Bryant did in 
his patches see:  https://github.com/russellb/ovs/commits/chaining

They have several advantages:

  1.  Creates a new table for chaining which should help isolate the code and 
make chaining more “atomic”
  2.  He follows the port-pair/port-chain model of SFC so integration should be 
cleaner
  3.  Following the port-pair/port-chain model makes extending the solution to 
handle a chain of VNFs fairly easy.

If everyone is good with this I can work this into the patches and rebase.

Networking-OVN
===

There is some old code here in plugin.py that I think comes out. When I added 
OVN as a SFC Driver there was a lot of code that I added to  networking-ovn 
that became obsolete. The IDL code would be modified to follow the 
port-pair/port-chain. model.  The biggest question I have from your comments is 
the interface between the networking-sfc and networking-ovn. I think I agree 
with you that networking-ovn should expose an interface that is called by 
networking-sfc and that would remove the need to subclass OVNPlugin in the 
networking-sfc OVN driver. Is that what you were intending?

Networking-SFC
==

If we follow Russell’s model in OVN/OVS then there very close alignment with 
the SFC model and the code will become simpler. Also removing the OVNPlugin 
dependency will also clean things up.


Regards

John



From: Ryan Moats <rmo...@us.ibm.com<mailto:rmo...@us.ibm.com>>
Date: Sunday, May 8, 2016 at 11:23 AM
To: John McDowall 
<jmcdow...@paloaltonetworks.com<mailto:jmcdow...@paloaltonetworks.com>>
Cc: "disc...@openvswtich.org<mailto:disc...@openvswtich.org>" 
<disc...@openvswtich.org<mailto:disc...@openvswtich.org>>, 
"openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: [OVN] [networking-ovn] [networking-sfc] SFC and OVN


First, apologies for the cross-posting, but when this topic came up last week,
I wasn't able to keep track of all the folks that asked to be included in the 
email,
so I'm doing a mass post to try and catch everybody that might be interested.

Second, John, thank you for stepping forward and mentioning that you've been
working on code for SFC and OVN!!  I took a look at your repos on github.com
(because I'm a firm believe in NOT re-inventing the wheel) and my initial
comments follow...

Networking-SFC 
(https://github.com/doonhammer/networking-sfc<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_doonhammer_networking-2Dsfc=CwMFAg=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo=vZ6VUDaavDpfOdPQrz1ED54jEjvAE36A8TVJroVlrOQ=U1Z58onycTVLkKu5lK1k6MTi8Vx_TRm7AYdfOfjzHKU=f0FHv3SjQ4uiHA5szlYScnjrn-3hXOmeL5rvvYeChGY=>)
=

This repo is the cleanest, as I was able to merge the current networking-sfc
master on top of it with no conflicts.  Looking around, I'm not entirely
comfortable with the idea of networking-sfc making direct calls to the OVN IDL
in parallel to networking-ovn.  I believe a cleaner solution would be to
add the code to configure OVN for SFC to networking-ovn itself, and expose an
API that the driver code in networking-sfc would call.

Networking-OVN 
(https://github.com/doonhammer/networking-ovn<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_doonhammer_networking-2Dovn=CwMFAg=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo=vZ6VUDaavDpfOdPQrz1ED54jEjvAE36A8TVJroVlrOQ=U1Z58onycTVLkKu5lK1k6MTi8Vx_TRm7AYdfOfjzHKU=W1GnEuKxO_aoyjJ5aMHM8vA8no-OrpSdP0hSk0AXYe4=>)
=

This repo makes me a bit nervous, as it claims to be 36 commits ahead
(and 129 commits behind) openstack-master.  That's a substantial drift, and
the first thing I wanted to do was see what merge conflicts might exist when
I try to merge the current master into it.  There are two merge conflicts
detected in networking_ovn/plugin.py, and given (as I understand it) the
direction of splitting the networking-ovn monolithic plugin back into ML2
and L3 service portions, I encourage you to rebase this commit (if you don't
have time, let me know and I'll see about fixing the merge issue).

OVS 
(https://github.com/doonhammer/ovs<https://urldefense.proofpoint.com/

Re: [openstack-dev] [neutron] Social at the summit

[John McDowall]

Kyle,

If it is open to all would like to join too.

Regards

John
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] meeting topics for 4/21/2016 networking-sfc project IRC meeting

[John McDowall]

Thursday works for me either lunch or dinner.

Regards

John

Sent from my iPhone

On Apr 19, 2016, at 5:31 PM, Cathy Zhang 
<cathy.h.zh...@huawei.com<mailto:cathy.h.zh...@huawei.com>> wrote:

Sure, good suggestion!  I am thinking we can have a lunch/dinner together. I 
will put this in Thursday's meeting agenda and let you and others know the f2f 
meeting time and place. Any specific date that is not good for you?

Thanks,
Cathy


From: John McDowall [mailto:jmcdow...@paloaltonetworks.com]
Sent: Tuesday, April 19, 2016 5:27 PM
To: Cathy Zhang
Cc: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron] meeting topics for 4/21/2016 
networking-sfc project IRC meeting

Cathy,

Thanks - is it worth while to have a f2f meeting with everyone at the summit?

Regards

John

Sent from my iPhone

On Apr 19, 2016, at 5:25 PM, Cathy Zhang 
<cathy.h.zh...@huawei.com<mailto:cathy.h.zh...@huawei.com>> wrote:
Hi John,

Thanks for the note. Great that you already have a skeleton OVN driver for 
networking-sfc.
The next step is to contribute to the detail driver specification and then work 
out the edges and details on the coding side as well as unit test and 
integration test (still a lot of work down the road:)). We can either sync up 
in the next project meeting (5/5 meeting) or sync up offline after you come 
back from the travel.

We will cancel the 4/28 project meeting since it is the OpenStack Summit week.

Thanks,
Cathy

From: John McDowall [mailto:jmcdow...@paloaltonetworks.com]
Sent: Tuesday, April 19, 2016 2:38 PM
To: Cathy Zhang; OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron] meeting topics for 4/21/2016 
networking-sfc project IRC meeting

Cathy,

I will not make the meeting on Thursday (traveling), but I have a skeleton OVN 
Driver in progress and should have it working by the end of the week with OVN 
and the current networking-sfc API. Lots of edge conditions and details to be 
worked out but the driver model make it pretty easy. Not sure of the next steps 
- contribute to the blueprint?

Regards

John

From: Cathy Zhang <cathy.h.zh...@huawei.com<mailto:cathy.h.zh...@huawei.com>>
Date: Tuesday, April 19, 2016 at 11:28 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Cc: Cathy Zhang <cathy.h.zh...@huawei.com<mailto:cathy.h.zh...@huawei.com>>
Subject: [openstack-dev] [Neutron] meeting topics for 4/21/2016 networking-sfc 
project IRC meeting

Hi everyone,
Here are some topics I have for this week's project meeting discussion(The 
meeting time is not changed, still UTC 1700 Thursday). Feel free to add more.
You can also find the meeting topics in the project wiki page.  
https://wiki.openstack.org/wiki/Meetings/ServiceFunctionChainingMeeting<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.openstack.org_wiki_Meetings_ServiceFunctionChainingMeeting=CwMFAg=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo=vZ6VUDaavDpfOdPQrz1ED54jEjvAE36A8TVJroVlrOQ=vMgCMsjn906ziN6T3iPlpzfMXRm17lPMgzesF0adY6U=AUSU1HCezI2Us9EVSu7uUxv5O8QANpGdBLLCnMJ5Bfc=>
 Meeting Info: Every Thursday 1700 UTC on #openstack-meeting-4
* Meeting time change from Thursday 1700 UTC to Friday 1700 UTC since 
no open channel for Wednesday 1700 UTC?
* Maintain the CI seriously and ensure the code in the repo pass all 
the basic static checks (needs ownership)
* Code Patches scrub
* Consistent Repository rule for networking-sfc related drivers: 
Northbound Tacker driver and Southbound ONOS driver, ODL driver, OVD driver
* new field "priority" in flow-classifier
* Move the generation of the data path chain path ID from the Driver 
component to the networking-sfc plugin component
* Define VNF type (l2 or l3) param in service-function-param
* Networking-sfc SFC driver for OVN
* Networking-sfc SFC driver for ODL
* Networking-sfc integration with ONOS completion status update
* Tacker Driver for networking-sfc
* Dynamic service chain update without service interruption


Thanks,
Cathy
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] meeting topics for 4/21/2016 networking-sfc project IRC meeting

[John McDowall]

Cathy,

Thanks - is it worth while to have a f2f meeting with everyone at the summit?

Regards

John

Sent from my iPhone

On Apr 19, 2016, at 5:25 PM, Cathy Zhang 
<cathy.h.zh...@huawei.com<mailto:cathy.h.zh...@huawei.com>> wrote:

Hi John,

Thanks for the note. Great that you already have a skeleton OVN driver for 
networking-sfc.
The next step is to contribute to the detail driver specification and then work 
out the edges and details on the coding side as well as unit test and 
integration test (still a lot of work down the road:)). We can either sync up 
in the next project meeting (5/5 meeting) or sync up offline after you come 
back from the travel.

We will cancel the 4/28 project meeting since it is the OpenStack Summit week.

Thanks,
Cathy

From: John McDowall [mailto:jmcdow...@paloaltonetworks.com]
Sent: Tuesday, April 19, 2016 2:38 PM
To: Cathy Zhang; OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron] meeting topics for 4/21/2016 
networking-sfc project IRC meeting

Cathy,

I will not make the meeting on Thursday (traveling), but I have a skeleton OVN 
Driver in progress and should have it working by the end of the week with OVN 
and the current networking-sfc API. Lots of edge conditions and details to be 
worked out but the driver model make it pretty easy. Not sure of the next steps 
- contribute to the blueprint?

Regards

John

From: Cathy Zhang <cathy.h.zh...@huawei.com<mailto:cathy.h.zh...@huawei.com>>
Date: Tuesday, April 19, 2016 at 11:28 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Cc: Cathy Zhang <cathy.h.zh...@huawei.com<mailto:cathy.h.zh...@huawei.com>>
Subject: [openstack-dev] [Neutron] meeting topics for 4/21/2016 networking-sfc 
project IRC meeting

Hi everyone,
Here are some topics I have for this week's project meeting discussion(The 
meeting time is not changed, still UTC 1700 Thursday). Feel free to add more.
You can also find the meeting topics in the project wiki page.  
https://wiki.openstack.org/wiki/Meetings/ServiceFunctionChainingMeeting<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.openstack.org_wiki_Meetings_ServiceFunctionChainingMeeting=CwMFAg=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo=vZ6VUDaavDpfOdPQrz1ED54jEjvAE36A8TVJroVlrOQ=vMgCMsjn906ziN6T3iPlpzfMXRm17lPMgzesF0adY6U=AUSU1HCezI2Us9EVSu7uUxv5O8QANpGdBLLCnMJ5Bfc=>
 Meeting Info: Every Thursday 1700 UTC on #openstack-meeting-4
* Meeting time change from Thursday 1700 UTC to Friday 1700 UTC since 
no open channel for Wednesday 1700 UTC?
* Maintain the CI seriously and ensure the code in the repo pass all 
the basic static checks (needs ownership)
* Code Patches scrub
* Consistent Repository rule for networking-sfc related drivers: 
Northbound Tacker driver and Southbound ONOS driver, ODL driver, OVD driver
* new field "priority" in flow-classifier
* Move the generation of the data path chain path ID from the Driver 
component to the networking-sfc plugin component
* Define VNF type (l2 or l3) param in service-function-param
* Networking-sfc SFC driver for OVN
* Networking-sfc SFC driver for ODL
* Networking-sfc integration with ONOS completion status update
* Tacker Driver for networking-sfc
* Dynamic service chain update without service interruption


Thanks,
Cathy
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] meeting topics for 4/21/2016 networking-sfc project IRC meeting

[John McDowall]

Cathy,

I will not make the meeting on Thursday (traveling), but I have a skeleton OVN 
Driver in progress and should have it working by the end of the week with OVN 
and the current networking-sfc API. Lots of edge conditions and details to be 
worked out but the driver model make it pretty easy. Not sure of the next steps 
- contribute to the blueprint?

Regards

John

From: Cathy Zhang >
Date: Tuesday, April 19, 2016 at 11:28 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Cc: Cathy Zhang >
Subject: [openstack-dev] [Neutron] meeting topics for 4/21/2016 networking-sfc 
project IRC meeting

Hi everyone,
Here are some topics I have for this week's project meeting discussion(The 
meeting time is not changed, still UTC 1700 Thursday). Feel free to add more.
You can also find the meeting topics in the project wiki page.  
https://wiki.openstack.org/wiki/Meetings/ServiceFunctionChainingMeeting
 Meeting Info: Every Thursday 1700 UTC on #openstack-meeting-4
· Meeting time change from Thursday 1700 UTC to Friday 1700 UTC since 
no open channel for Wednesday 1700 UTC?
· Maintain the CI seriously and ensure the code in the repo pass all 
the basic static checks (needs ownership)
· Code Patches scrub
· Consistent Repository rule for networking-sfc related drivers: 
Northbound Tacker driver and Southbound ONOS driver, ODL driver, OVD driver
· new field "priority" in flow-classifier
· Move the generation of the data path chain path ID from the Driver 
component to the networking-sfc plugin component
· Define VNF type (l2 or l3) param in service-function-param
· Networking-sfc SFC driver for OVN
· Networking-sfc SFC driver for ODL
· Networking-sfc integration with ONOS completion status update
· Tacker Driver for networking-sfc
· Dynamic service chain update without service interruption


Thanks,
Cathy
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [networking-ovn][ovn4nfv]

[John McDowall]

Gary,

Thanks for replying. I did chat briefly to one of the authors of SFC last week 
and will talk with them more.

I will admit I am coming at the general service insertion problem from a very 
specific use case; easily protecting east-west traffic between applications by 
dynamically inserting  a NGFW as a VNF; so my viewpoint is slightly slanted ;-).

To answer your specific questions:

  1.  I think the Service Chaining/Insertion API will work for this effort too 
as the concept of port-pairs fits well with what I have done. As the API I have 
created is just "syntactical sugar” changing it is not a big deal. The two 
issues I see are 1) the classifier, as the firewall is a (DPI) classifier this 
step may not be necessary or it could act as a pre-filter, and 2) the ability 
to steer traffic to a specific application through the VNF. In general though I 
think we could make it work.
  2.  There has to be some changes at the networking layer to steer traffic 
into new paths defined by the API, and as Russell points out the majority of 
the work is in OVN. The changes to Open vSwitch are only in the ovn-nb layer 
and are additive, i.e. They do not change the current behavior only layer on 
top. In Openstack I have tried to isolate the changes to follow the neutron 
plugin model. Is there a better way to do it? If OVN had a plugin model would 
that help?

Regards

John




[Palo Alto Networks Ignite 2016]
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [networking-ovn][ovn4nfv]

[John McDowall]

All,

As a VNF vendor we have been looking at ways to enable customers to simply
scale up (and down) VNF’s in complex virtual networks at scale. Our goal
is to help accelerate the deployment of SDN and VNF’s and more
specifically enable zero-trust security at scale for applications.  This
requires the easy and fast deployment of Next Generation Firewalls (and
other VNF¹s) into the traffic path of any application.

Over the last several weeks we have created a prototype that implements
a simple VNF insertion approach. Before we do additional work we have a
couple of questions for the community:

Questions
‹

1. This approach has the advantage of being very simple and works with
existing VNF¹s, does it make sense to the community?
2. If it is of interest how could it be improved and or enhanced to make
it more useful and consumable?

Design Guidelines
‹

At the start of the effort we created a set of design guidelines to
constrain the problem space.


* The goal is a Service Function Insertion (SFI) approach that is simpler
and easier to deploy than Service Function Chaining and is more applicable
to single function insertion or very short chains.
* The initial design target is DC/Enterprises where the requirements are
typically for insertion of a limited set of VNF¹s in specific network
locations to act on specific applications.
* Minimal changes to existing VNF, ours and others,
* Make the solution open to all VNF¹s.
* Leverage bump in the wire connectivity as this does not require L2 or L3
knowledge/configuration in the VNF.
* Firewalls want to inspect/classify all traffic on a link, so
pre-classifing traffic beyond ACL¹s is not necessary.
* Deploy on standard infrastructure; Openstack and Open vSwitch with
minimal changes
* Work with virtualization and containers and physical devices seamlessly.
* Insert and remove security is seconds, one of the drivers of the
requirement for speed is container deployment
* Simple to deploy and easy to debug is important - atomic insertion and
removal of VNF is an important aspect of this.


Approach


We have developed a prototype, roughly using the ovn4nfv model proposed by
Vikram Dham and others in OPNFV.  The implemented prototype of ovn4nfv is
on OpenVSwitch 2.5 and Openstack Mitaka (development branch). I would like
to stress this is a prototype and not production code. My objective was to
prove to myself (and others) that the concept would work and then ask for
feedback from the community on level of interest and how best to design a
production implementation.

I have called this effort service function insertion (SFI) to
differentiate from service function chaining (SFC). This approach is
simpler than SFC and requires minimal or no changes to existing VNF¹s that
act as a bump in the wire, but it will probably not handle long complex
chains or graphs. It can possibly handle chaining one or two VNF¹s in a
static manner, but not sure if it could go beyond that. I am open to
suggestions of how to extend/improve it.

The traffic steering is implemented by inserting 2 ingress and 2 egress
rules in the ovn-nb pipeline at ingress stage 3. These rules have a higher
priority than the default rules. The changes to OVN and rules are listed
in the implementation section.

The control plane is implemented in both Open vSwitch and in Openstack. In
Openstack there is a set of extension interfaces added to the
networking-ovn plugin. There are both CLI and REST API¹s provided for
Openstack and CLI for Open vSwitch.

The OVN model enables logical changes to the flow rules and Openstack
neutron plugin model allows separation of changes to extensions to the
networking-OVN plugin. I have however violated a few boundaries for
expediency that would need to be fixed before
this could be easily deployed.

We are happy to contribute the code back to the community, but would like
to gauge the level on interest and solicit feedback on the approach. We
are open to any and all suggestions for improvements in both
implementation and approach.

Below I have given a rough overview of the implementation and the changes
I have made to the various code bases. Just to re-iterate this was done as
a quick prototype and was a learning experience in Openstack and Open
vSwitch on the way so the quality
of the code and architecture are not production ready. Links are provide
to my github repositories with the changes.

Implementation
‹‹

The approach atomically inserts rules into ovn-nb to intercept any traffic
going to or coming from a vm or a container, requires insertion of four
new rules. There are no other changes in Open vSwitch. While the prototype
is using a firewall as the VNF there is no requirement for that to be the
case any VNF that supports ³bump in the wire mode² should work.

App-1 is the application that needs to be protected
FW-2 is the input port of the firewall
FW-1 is the egress port of the firewall
App-2 is an application talking to App-1