Re: [openstack-dev] Change in openstack/networking-sfc[master]: Networking-sfc / OVN Driver
Thanks your response. Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: na...@cn.ibm.com 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: Cathy Zhang To: Na Zhu/China/IBM@IBMCN Cc: Farhad Sunavala , John McDowall , Henry Fourie , Kyle Mestery , "OpenStack Development Mailing List (not for usage questions)" , Russell Bryant , Ryan Moats , Richard Theis , Stephen Wong , "Vikram Choudhary" Date: 2016/06/29 09:21 Subject:RE: Change in openstack/networking-sfc[master]: Networking-sfc / OVN Driver Please see inline. Cathy From: Na Zhu [mailto:na...@cn.ibm.com] Sent: Monday, June 27, 2016 9:56 PM To: Cathy Zhang Cc: Farhad Sunavala; John McDowall; Henry Fourie; Kyle Mestery; OpenStack Development Mailing List (not for usage questions); Russell Bryant; Ryan Moats; Richard Theis; Stephen Wong; Vikram Choudhary Subject: RE: Change in openstack/networking-sfc[master]: Networking-sfc / OVN Driver Hi Cathy, Thanks your response. Another question, how to create different port-chains for different tenants, and these chains consist of the same port pair group. In my test scenario, port-pair-group created by tenant A is not visible for tenant B. Cathy> Each port pair group has an associated tenant ID, so it belongs to a tenant, that is why it is not visible. The same tenant can have multiple chains, eg. One for voice, one for video, one for data, and these chains can share the port pair group. But different tenants can not share the port pair group. Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: na...@cn.ibm.com 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:Cathy Zhang To:Na Zhu/China/IBM@IBMCN, Henry Fourie , "OpenStack Development Mailing List (not for usage questions)" < openstack-dev@lists.openstack.org> Cc:Ryan Moats , Kyle Mestery < mest...@mestery.com>, Russell Bryant , Richard Theis < rth...@us.ibm.com>, Stephen Wong , Vikram Choudhary , Farhad Sunavala , "John McDowall" Date:2016/06/28 12:29 Subject:RE: Change in openstack/networking-sfc[master]: Networking-sfc / OVN Driver Hi Na, Please see inline for my reply. Cathy -Original Message- From: Na Zhu (Code Review) [mailto:rev...@openstack.org] Sent: Monday, June 27, 2016 8:08 PM To: Henry Fourie Cc: Ryan Moats; Na Zhu; Kyle Mestery; Russell Bryant; Richard Theis; Stephen Wong; Cathy Zhang; Vikram Choudhary; Farhad Sunavala; John McDowall Subject: Change in openstack/networking-sfc[master]: Networking-sfc / OVN Driver Na Zhu has posted comments on this change. Change subject: Networking-sfc / OVN Driver .. Patch Set 1: (1 comment) https://review.openstack.org/#/c/333172/1/doc/source/sfc_ovn_driver.rst File doc/source/sfc_ovn_driver.rst: Line 88: +-+ +-+ outport +===+ > Agree that it is better to clarify these points. Hi Cathy, I try to create multiple port-chains with the same port-pair-group, it failed. I think it is not allowed to do what you said, right? (neutron) port-chain-create --flow-classifier fc --port-pair-group pg1 pc1 Port Pair Group(s) [u'17c9a0a5-a38f-4a75-834e-9aa213cd431f'] in use by Port Chain f3af530f-210a-4c51-9a02-f1835d5b1d85. Neutron server returns request_ids: ['req-47e6a39b-677a-4ce3-9976-5dfcee0ac47f'] (neutron) Cathy> when a port pair group is shared by multiple chains, these chains should be different, which means these chains should consist of different sequences of port pair groups. For example, chain 1 consists of and chain 2 consists of "port-pair-group1, port-pair-group3, port-pair-group4>. But if the two chains are the same, i.e. they consist of the same sequence of port-pair-groups (e.g. the two chains both consist of ), then it is not allowed since it does not make sense to create the same chain twice. Maybe your test scenario falls into the second case? -- To view, visit https://review.openstack.org/333172 To unsubscribe, visit https://review.openstack.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I5c1827dcc81e48983a41120ec08983c571c5b2e9 Gerrit-PatchSet: 1 Gerrit-Project: openstack/networking-sfc Gerrit-Branch: master Gerrit-Owner: Louis Fourie Gerrit-Reviewer: Farhad Sunavala Gerrit-Reviewer: Jenkins Gerrit-Reviewer: John McDowall Gerrit-Reviewer: Kyle Mestery Gerrit-Reviewer: Louis Fourie Gerrit-Reviewer: Na Zhu Gerrit-Reviewer: Richard Theis Gerrit-Reviewer: Russell Bryant Gerrit-Reviewer: Ryan Moats Gerrit-Reviewer: Stephen Wong Gerrit-Reviewer: cathy Gerrit-Reviewer: vikram.choudhary Gerrit-HasComments: Yes ___
Re: [openstack-dev] Change in openstack/networking-sfc[master]: Networking-sfc / OVN Driver
Hi Cathy, Thanks your response. Another question, how to create different port-chains for different tenants, and these chains consist of the same port pair group. In my test scenario, port-pair-group created by tenant A is not visible for tenant B. Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: na...@cn.ibm.com 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: Cathy Zhang To: Na Zhu/China/IBM@IBMCN, Henry Fourie , "OpenStack Development Mailing List (not for usage questions)" Cc: Ryan Moats , Kyle Mestery , Russell Bryant , Richard Theis , Stephen Wong , Vikram Choudhary , Farhad Sunavala , "John McDowall" Date: 2016/06/28 12:29 Subject:RE: Change in openstack/networking-sfc[master]: Networking-sfc / OVN Driver Hi Na, Please see inline for my reply. Cathy -Original Message- From: Na Zhu (Code Review) [mailto:rev...@openstack.org] Sent: Monday, June 27, 2016 8:08 PM To: Henry Fourie Cc: Ryan Moats; Na Zhu; Kyle Mestery; Russell Bryant; Richard Theis; Stephen Wong; Cathy Zhang; Vikram Choudhary; Farhad Sunavala; John McDowall Subject: Change in openstack/networking-sfc[master]: Networking-sfc / OVN Driver Na Zhu has posted comments on this change. Change subject: Networking-sfc / OVN Driver .. Patch Set 1: (1 comment) https://review.openstack.org/#/c/333172/1/doc/source/sfc_ovn_driver.rst File doc/source/sfc_ovn_driver.rst: Line 88: +-+ +-+ outport +===+ > Agree that it is better to clarify these points. Hi Cathy, I try to create multiple port-chains with the same port-pair-group, it failed. I think it is not allowed to do what you said, right? (neutron) port-chain-create --flow-classifier fc --port-pair-group pg1 pc1 Port Pair Group(s) [u'17c9a0a5-a38f-4a75-834e-9aa213cd431f'] in use by Port Chain f3af530f-210a-4c51-9a02-f1835d5b1d85. Neutron server returns request_ids: ['req-47e6a39b-677a-4ce3-9976-5dfcee0ac47f'] (neutron) Cathy> when a port pair group is shared by multiple chains, these chains should be different, which means these chains should consist of different sequences of port pair groups. For example, chain 1 consists of and chain 2 consists of "port-pair-group1, port-pair-group3, port-pair-group4>. But if the two chains are the same, i.e. they consist of the same sequence of port-pair-groups (e.g. the two chains both consist of ), then it is not allowed since it does not make sense to create the same chain twice. Maybe your test scenario falls into the second case? -- To view, visit https://review.openstack.org/333172 To unsubscribe, visit https://review.openstack.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I5c1827dcc81e48983a41120ec08983c571c5b2e9 Gerrit-PatchSet: 1 Gerrit-Project: openstack/networking-sfc Gerrit-Branch: master Gerrit-Owner: Louis Fourie Gerrit-Reviewer: Farhad Sunavala Gerrit-Reviewer: Jenkins Gerrit-Reviewer: John McDowall Gerrit-Reviewer: Kyle Mestery Gerrit-Reviewer: Louis Fourie Gerrit-Reviewer: Na Zhu Gerrit-Reviewer: Richard Theis Gerrit-Reviewer: Russell Bryant Gerrit-Reviewer: Ryan Moats Gerrit-Reviewer: Stephen Wong Gerrit-Reviewer: cathy Gerrit-Reviewer: vikram.choudhary Gerrit-HasComments: Yes __ 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-sfc: unable to use SFC (ovs driver) with multiple networks
Hi MartinX, I think you can move p2 to net1 and p3 to net4, or you can put p1, p2, p3 and p4 in the same network. Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: na...@cn.ibm.com 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: Cathy Zhang To: "OpenStack Development Mailing List (not for usage questions)" , "martinx.bans...@intel.com" Date: 2016/06/22 02:36 Subject:Re: [openstack-dev] networking-sfc: unable to use SFC (ovs driver) with multiple networks Hi MartinX, I sent you a reply on 6/14. Cathy -Original Message- From: Banszel, MartinX [mailto:martinx.bans...@intel.com] Sent: Thursday, June 16, 2016 4:49 AM To: 'openstack-dev@lists.openstack.org' Subject: [openstack-dev] networking-sfc: unable to use SFC (ovs driver) with multiple networks Hello, I'd need some help with using the SFC implementation in openstack. I use liberty version of devstack + liberty branch of networking-sfc. It's not clear to me if the SFC instance and it's networks should be separated from the remaining virtual network topology or if it should be connected to it. E.g. consider the following topology, where SFC and its networks net2 and net3 (one for ingress port, one for egress port) are connected to the tenants networks. I know that all three instances can share one network but a use case I am trying to implement requires that every instance has it's separated network and there is a different network for ingress and egress port of the SF. +---+ +-+ +---+ | VMSRC | | VMSFC | | VMDST | +---+---+ +--+---+--+ +---+---+ | p1 (1.1.1.1) p2| |p3 |p4 (4.4.4.4) || || -++--- net1 | | --+---+- net4 | | || | ---+-+---) net2 | | ---)--+--+ net3 | | | | | | +--+--+--+| +--+ ROUTER ++ ++ All networks are connected to a single router ROUTER. I created a flow classifier that matches all traffic going from VMSRC to VMDST (--logical-source-port p1 --source-ip-prefix=1.1.1.1/32 --destination-ip-prefix=4.4.4.4/32), port pair p2,p3, a port pair group containing this port pair and a port chain containing this port pair group and flow classifier. If I try to ping from VMSRC the 5.4.4.4 address, it is correctly steered through the VMSFC (where just the ip_forwarding is set to 1) and forwarded back through the p3 port to the ROUTER. The router finds out that there are packets with source address 1.1.1.1 coming from port where is should not (the router expects those packets from the net1 interface), they don't pass the reverse path filter and the router drops them. It works when I set the rp_filter off via sysctl command in the router namespace on the controller. But I don't want to do this -- I expect the sfc to work without such changes. Is such topology supported? What should the topology look like? I have noticed, that when I disconnect the net2 and net3 from the ROUTER, and add new routers ROUTER2 and ROUTER3 to the net2 and net3 networks respectivelly and don't connect them anyhow to the ROUTER nor the rest of the topology, the OVS is able to send the traffic to the p2 port on the ingress side. However, on the egress side the packet is routed to the ROUTER3 which drops it as it doesn't have any route for it. Thanks for any hints! Best regards Martin Banszel -- Intel Research and Development Ireland Limited Registered in Ireland Registered Office: Collinstown Industrial Park, Leixlip, County Kildare Registered Number: 308263 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. __ 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 - Message from Cathy Zhang on Wed, 15 Jun 2016 00:58:33 + - To: "OpenStack Development Mailing List (not for usage questions)" cc: Cathy Zhang Subject: RE: networking-sfc: unable to use SFC (ovs driver) with multiple networks Hi Banszel, Please see inline. Than
Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN
Hi John, I update the networking-sfc and networking-ovn for the new schema. I think the most important now is nail down the ovsdb schema for SFC, as you know, it is not hard to implement networking-sfc and networking-ovn, but if the schema changes, we have to update networking-sfc and networking-ovn, the schema is the basic, it is better to finalize it at the beginning. Ryan has some comments one the new version. We need to discuss together and finalize it which we all agree with. Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: na...@cn.ibm.com 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: John McDowall To: Na Zhu/China/IBM@IBMCN Cc: discuss , "OpenStack Development Mailing List (not for usage questions)" , "Srilatha Tangirala" Date: 2016/06/15 09:35 Subject:Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN Juno, Thanks really appreciate the help Regards John Sent from my iPhone On Jun 14, 2016, at 6:12 PM, Na Zhu wrote: John, OK, I will change networking-ovn IDL to align with the new schema. Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: na...@cn.ibm.com 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:John McDowall To:Na Zhu/China/IBM@IBMCN Cc:discuss , "OpenStack Development Mailing List (not for usage questions)" , "Srilatha Tangirala" Date:2016/06/15 08:30 Subject:Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN 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 �C 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 Date: Monday, June 13, 2016 at 9:57 PM To: John McDowall Cc: discuss , "OpenStack Development Mailing List (not for usage questions)" , Srilatha Tangirala 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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:John McDowall To:Na Zhu/China/IBM@IBMCN Cc:"OpenStack Development Mailing List (not for usage questions)" , discuss , Srilatha Tangirala 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 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 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 Cc:Srilatha Tangirala , "OpenStack Development Mailing List \(not for usage questions\)" < openstack-dev@lists.openstack.org>, discuss 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,
Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN
Ryan, Thanks your really helpful comments. If the lswitch is determined by flow classifier, I think no need to record in logical router, ovn creates patch port pair for router interface, one patch port connects logical switch, the other connects logical router. The one connects logical switch is neutron router interface. We still can record port chain on logical switch for the logical-source-port is router interface, right? Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: na...@cn.ibm.com 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: Ryan Moats/Omaha/IBM To: John McDowall Cc: Na Zhu , Srilatha Tangirala/San Francisco/IBM@IBMUS, "OpenStack Development Mailing List \(not for usage questions\)" , discuss Date: 2016/06/15 12:42 Subject:Re: [ovs-discuss] [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC andOVN "discuss" wrote on 06/14/2016 10:31:40 PM: > From: John McDowall > To: Na Zhu > Cc: Srilatha Tangirala/San Francisco/IBM@IBMUS, "OpenStack > Development Mailing List \(not for usage questions\)" d...@lists.openstack.org>, discuss > Date: 06/14/2016 10:48 PM > Subject: Re: [ovs-discuss] [openstack-dev] [OVN] [networking-ovn] > [networking-sfc] SFC andOVN > Sent by: "discuss" > > 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... 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... 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, Here is the steps to configure sfc, 1, create flow-classifer 2, create port-pairs 3, create port-pair-group with port-pairs 4, create port-chain with flow-classifer and port-pair-groups You can see that the port-chain is not related to network, my question is how to get the lswitch for networking-sfc and write it to database? Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: na...@cn.ibm.com 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: John McDowall To: Na Zhu/China/IBM@IBMCN Cc: discuss , "OpenStack Development Mailing List (not for usage questions)" , "Srilatha Tangirala" Date: 2016/06/15 11:31 Subject:Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN 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 Regards John Sent from my iPhone On Jun 14, 2016, at 8:09 PM, Na Zhu wrote: Hi John, Another question, I think port-chain is irrelevant with lswitch, one port-chain includes multiple port-pair-groups and one flow-classifier, how to get the lswitch by port-chain? Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: na...@cn.ibm.com 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:John McDowall To:Na Zhu/China/IBM@IBMCN Cc:discuss , "OpenStack Development Mailing List (not for usage questions)" , "Srilatha Tangirala" Date:2016/06/15 11:04 Subject:Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN The reason I did that was to be able to create reusable VNF's Regards John Sent from my iPhone On Jun 14, 2016, at 7:15 PM, Na Zhu wrote: John, Since you have port-chain as child of lswitch, do you need port-pairs as child of lswitch any more? Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: 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 Cc:discuss , "OpenStack Development Mailing List (not for usage questions)" , "Srilatha Tangirala" Date:2016/06/15 09:11 Subject:Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN John, OK, I will change networking-ovn IDL to align with the new schema. Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: na...@cn.ibm.com 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:John McDowall To:Na Zhu/China/IBM@IBMCN Cc:discuss , "OpenStack Development Mailing List (not for usage questions)" , "Srilatha Tangirala" Date:2016/06/15 08:30 Subject:Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN 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 �C 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 Date: Monday, June 13, 2016 at 9:57 PM To: John McDowall Cc: discuss , "OpenStack Development Mailing List (not for usage questions)" , Srilatha Tangirala 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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:John McDowall To:Na Zhu/China/IBM@IBMCN Cc:"OpenStack Development Mailing List (not for usage questions)" , discuss , Srilatha Tangirala Date:2016/06/14 12:17 Subject:R
Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN
Hi John, Another question, I think port-chain is irrelevant with lswitch, one port-chain includes multiple port-pair-groups and one flow-classifier, how to get the lswitch by port-chain? Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: na...@cn.ibm.com 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: John McDowall To: Na Zhu/China/IBM@IBMCN Cc: discuss , "OpenStack Development Mailing List (not for usage questions)" , "Srilatha Tangirala" Date: 2016/06/15 11:04 Subject:Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN The reason I did that was to be able to create reusable VNF's Regards John Sent from my iPhone On Jun 14, 2016, at 7:15 PM, Na Zhu wrote: John, Since you have port-chain as child of lswitch, do you need port-pairs as child of lswitch any more? Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: 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 Cc:discuss , "OpenStack Development Mailing List (not for usage questions)" , "Srilatha Tangirala" Date:2016/06/15 09:11 Subject:Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN John, OK, I will change networking-ovn IDL to align with the new schema. Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: na...@cn.ibm.com 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:John McDowall To:Na Zhu/China/IBM@IBMCN Cc:discuss , "OpenStack Development Mailing List (not for usage questions)" , "Srilatha Tangirala" Date:2016/06/15 08:30 Subject:Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN 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 �C 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 Date: Monday, June 13, 2016 at 9:57 PM To: John McDowall Cc: discuss , "OpenStack Development Mailing List (not for usage questions)" , Srilatha Tangirala 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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:John McDowall To:Na Zhu/China/IBM@IBMCN Cc:"OpenStack Development Mailing List (not for usage questions)" , discuss , Srilatha Tangirala 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 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 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 Cc:Srilatha Tangirala , "OpenStack Dev
Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN
John, Since you have port-chain as child of lswitch, do you need port-pairs as child of lswitch any more? Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: 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 Cc: discuss , "OpenStack Development Mailing List (not for usage questions)" , "Srilatha Tangirala" Date: 2016/06/15 09:11 Subject:Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN John, OK, I will change networking-ovn IDL to align with the new schema. Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: na...@cn.ibm.com 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: John McDowall To: Na Zhu/China/IBM@IBMCN Cc: discuss , "OpenStack Development Mailing List (not for usage questions)" , "Srilatha Tangirala" Date: 2016/06/15 08:30 Subject:Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN 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 �C 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 Date: Monday, June 13, 2016 at 9:57 PM To: John McDowall Cc: discuss , "OpenStack Development Mailing List (not for usage questions)" , Srilatha Tangirala 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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:John McDowall To:Na Zhu/China/IBM@IBMCN Cc:"OpenStack Development Mailing List (not for usage questions)" , discuss , Srilatha Tangirala 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 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 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 Cc:Srilatha Tangirala , "OpenStack Development Mailing List \(not for usage questions\)" < openstack-dev@lists.openstack.org>, discuss 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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:John McDowall To:Na Zhu/China/IBM@IBMCN Cc:discuss , Srilatha Tangirala < srila...@us.ibm.com>, "OpenStack Development Mailing List (not for usage questions)&q
Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN
John, OK, I will change networking-ovn IDL to align with the new schema. Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: na...@cn.ibm.com 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: John McDowall To: Na Zhu/China/IBM@IBMCN Cc: discuss , "OpenStack Development Mailing List (not for usage questions)" , "Srilatha Tangirala" Date: 2016/06/15 08:30 Subject:Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN 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 �C 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 Date: Monday, June 13, 2016 at 9:57 PM To: John McDowall Cc: discuss , "OpenStack Development Mailing List (not for usage questions)" , Srilatha Tangirala 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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:John McDowall To:Na Zhu/China/IBM@IBMCN Cc:"OpenStack Development Mailing List (not for usage questions)" , discuss , Srilatha Tangirala 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 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 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 Cc:Srilatha Tangirala , "OpenStack Development Mailing List \(not for usage questions\)" < openstack-dev@lists.openstack.org>, discuss 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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:John McDowall To:Na Zhu/China/IBM@IBMCN Cc:discuss , Srilatha Tangirala < srila...@us.ibm.com>, "OpenStack Development Mailing List (not for usage questions)" 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 �C 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 �C 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 Date: Monday, June 13, 2016 at 6:
Re: [openstack-dev] [neutron][SFC]
Hi Mohan, Thanks your information. I see there is restriction check in OVS flow classifier driver, but you can see that in the flow classifier table, the column logical_source_port nullable is false, this affects every driver. Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: na...@cn.ibm.com 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: Mohan Kumar To: "OpenStack Development Mailing List (not for usage questions)" Date: 2016/06/13 15:49 Subject:Re: [openstack-dev] [neutron][SFC] Hi Alioune / nazhu, Logical-source-port is not mandatory in API , you can create Flow_classifier without logical-source-port , This restriction is moved to OVS driver . Please refer review link https://review.openstack.org/#/c/313801/5 If your back end driver is OVS , you need to specify the logical-source-port is much needed as per design to avoid the return packet to reclassified . Thanks., Mohankumar.N On Mon, Jun 13, 2016 at 7:49 AM, Na Zhu wrote: I find this issue also, I filed a bug about it https://bugs.launchpad.net/networking-sfc/+bug/1586721 I think logical-source-port can be optional. Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: na...@cn.ibm.com 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:Alioune To:"OpenStack Development Mailing List (not for usage questions)" Date:2016/06/10 22:28 Subject:Re: [openstack-dev] [neutron][SFC] Hi Mohan, Even if I clone the master branch of networking-sfc project,I get the following errir when creating flow-classifier, therefore I do precise the logical-source-port. 2016-06-10 05:34:05.693 10799 ERROR neutron.api.v2.resource DBError: (pymysql.err.IntegrityError) (1048, u"Column 'logical_source_port' cannot be null") I'm trying the example in [1] Here is a "ovs-ofctl dump-flows" on br-int ofter creating port-chain, I expected to see vxlan or gre tunnel encapsulation entries as explained in [1], may I know why there is no tunnel entry in br-int ? sudo ovs-ofctl dump-flows br-int NXST_FLOW reply (xid=0x4): cookie=0x90444f3c8fabcbe0, duration=2840.983s, table=0, n_packets=0, n_bytes=0, idle_age=2840, priority=10,icmp6,in_port=16,icmp_type=136 actions=resubmit(,24) cookie=0x90444f3c8fabcbe0, duration=2837.039s, table=0, n_packets=0, n_bytes=0, idle_age=2837, priority=10,icmp6,in_port=17,icmp_type=136 actions=resubmit(,24) cookie=0x90444f3c8fabcbe0, duration=2831.688s, table=0, n_packets=0, n_bytes=0, idle_age=2831, priority=10,icmp6,in_port=19,icmp_type=136 actions=resubmit(,24) cookie=0x90444f3c8fabcbe0, duration=2831.038s, table=0, n_packets=0, n_bytes=0, idle_age=2831, priority=10,icmp6,in_port=18,icmp_type=136 actions=resubmit(,24) cookie=0x90444f3c8fabcbe0, duration=2801.555s, table=0, n_packets=0, n_bytes=0, idle_age=2801, priority=10,icmp6,in_port=20,icmp_type=136 actions=resubmit(,24) cookie=0x90444f3c8fabcbe0, duration=2840.605s, table=0, n_packets=8, n_bytes=336, idle_age=2591, priority=10,arp,in_port=16 actions=resubmit(,24) cookie=0x90444f3c8fabcbe0, duration=2836.759s, table=0, n_packets=0, n_bytes=0, idle_age=2836, priority=10,arp,in_port=17 actions=resubmit(,24) cookie=0x90444f3c8fabcbe0, duration=2831.485s, table=0, n_packets=0, n_bytes=0, idle_age=2831, priority=10,arp,in_port=19 actions=resubmit(,24) cookie=0x90444f3c8fabcbe0, duration=2830.816s, table=0, n_packets=21, n_bytes=882, idle_age=1605, priority=10,arp,in_port=18 actions=resubmit(,24) cookie=0x90444f3c8fabcbe0, duration=2801.309s, table=0, n_packets=10, n_bytes=420, idle_age=545, priority=10,arp,in_port=20 actions=resubmit(,24) cookie=0x90444f3c8fabcbe0, duration=15755.073s, table=0, n_packets=3241, n_bytes=366555, idle_age=545, priority=0 actions=NORMAL cookie=0x90444f3c8fabcbe0, duration=15754.687s, table=23, n_packets=0, n_bytes=0, idle_age=15754, priority=0 actions=drop cookie=0x90444f3c8fabcbe0, duration=2841.201s, table=24, n_packets=0, n_bytes=0, idle_age=2841, priority=2,icmp6,in_port=16,icmp_type=136,nd_target=fe80::f816:3eff:fe2d:c29d actions=NORMAL cookie=0x90444f3c8fabcbe0, duration=2837.177s, table=24, n_packets=0, n_bytes=0, idle_age=2837, priority=2,icmp6,in_port=17,icmp_type=136,nd_target=fe80::f816:3eff:fee0:f8ca actions=NORMAL cookie=0x90444f3c8fabcbe0, duration=2831.794s, table=24, n_packets=0, n_bytes=0, idle_age=2831, priority=2,icmp6,in_port=19,icmp_type=136,nd_target=fe80::f816:3eff:fe86:a668 actions=NORMAL cookie=0x90444f3c8fabcbe0, duration=2831.150s, table=24, n_packets=0, n_bytes=0, idle_age=2831, priority=2,icmp6,in_port=18,icmp_type=136,nd_target=fe80::f816:3eff:feb4:965f actions=NORMAL cookie=0x90444f3c8fabcbe0, duration=2801.675s, table=24, n_packets=0, n_bytes=0, idle_age=2801, priorit
Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN
Hi John, I submit one patch to every private repo, the create port chain can work now. Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: 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 Cc: Srilatha Tangirala , "OpenStack Development Mailing List \(not for usage questions\)" , discuss Date: 2016/06/14 13:03 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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: John McDowall To:Na Zhu/China/IBM@IBMCN Cc:"OpenStack Development Mailing List (not for usage questions)" , discuss , Srilatha Tangirala 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 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 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 Cc:Srilatha Tangirala , "OpenStack Development Mailing List \(not for usage questions\)" < openstack-dev@lists.openstack.org>, discuss 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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:John McDowall To:Na Zhu/China/IBM@IBMCN Cc:discuss , Srilatha Tangirala < srila...@us.ibm.com>, "OpenStack Development Mailing List (not for usage questions)" 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 �C 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 �C 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 Date: Monday, June 13, 2016 at 6:25 AM To: John McDowall Cc: discuss , Srilatha Tangirala < srila...@us.ibm.com>, "OpenStack Development Mailing List (not for usage questions)" 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 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 Cc:Srilatha Tangirala , "OpenStack Development Mailing List \(not for usage questions\)" < openstack-dev@lists.openstack.org>, discuss Date:2016/06/09 16:18 Subject:Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN Hi John, I know most
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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: John McDowall To: Na Zhu/China/IBM@IBMCN Cc: "OpenStack Development Mailing List (not for usage questions)" , discuss , Srilatha Tangirala 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 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 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 Cc:Srilatha Tangirala , "OpenStack Development Mailing List \(not for usage questions\)" < openstack-dev@lists.openstack.org>, discuss 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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:John McDowall To:Na Zhu/China/IBM@IBMCN Cc:discuss , Srilatha Tangirala < srila...@us.ibm.com>, "OpenStack Development Mailing List (not for usage questions)" 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 �C 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 �C 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 Date: Monday, June 13, 2016 at 6:25 AM To: John McDowall Cc: discuss , Srilatha Tangirala < srila...@us.ibm.com>, "OpenStack Development Mailing List (not for usage questions)" 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 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 Cc:Srilatha Tangirala , "OpenStack Development Mailing List \(not for usage questions\)" < openstack-dev@lists.openstack.org>, discuss 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
Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN
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 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 Cc: Srilatha Tangirala , "OpenStack Development Mailing List \(not for usage questions\)" , discuss 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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: John McDowall To:Na Zhu/China/IBM@IBMCN Cc:discuss , Srilatha Tangirala , "OpenStack Development Mailing List (not for usage questions)" 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 �C 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 �C 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 Date: Monday, June 13, 2016 at 6:25 AM To: John McDowall Cc: discuss , Srilatha Tangirala < srila...@us.ibm.com>, "OpenStack Development Mailing List (not for usage questions)" 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 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 Cc:Srilatha Tangirala , "OpenStack Development Mailing List \(not for usage questions\)" < openstack-dev@lists.openstack.org>, discuss 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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:John McDowall To:Amitabha Biswas Cc:Na Zhu/China/IBM@IBMCN, Srilatha Tangirala , "OpenStack Development Mailing List (not for usage questions)" < openstack-dev@lists.openstack.org>, discuss 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 refac
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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: John McDowall To: Na Zhu/China/IBM@IBMCN Cc: discuss , Srilatha Tangirala , "OpenStack Development Mailing List (not for usage questions)" 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 �C 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 �C 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 Date: Monday, June 13, 2016 at 6:25 AM To: John McDowall Cc: discuss , Srilatha Tangirala < srila...@us.ibm.com>, "OpenStack Development Mailing List (not for usage questions)" 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 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 Cc:Srilatha Tangirala , "OpenStack Development Mailing List \(not for usage questions\)" < openstack-dev@lists.openstack.org>, discuss 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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:John McDowall To:Amitabha Biswas Cc:Na Zhu/China/IBM@IBMCN, Srilatha Tangirala , "OpenStack Development Mailing List (not for usage questions)" < openstack-dev@lists.openstack.org>, discuss 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 Date: Tuesday, June 7, 2016 at 11:36 PM To: John McDowall Cc: Na Zhu , Srilatha Tangirala , "OpenStack Development Mailing List (not for usage questions)" < openstack-dev@lists.openstack.org>, discuss 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-ovnrepo 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 duplicat
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 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 Cc: Srilatha Tangirala , "OpenStack Development Mailing List \(not for usage questions\)" , discuss 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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:John McDowall To:Amitabha Biswas Cc: Na Zhu/China/IBM@IBMCN, Srilatha Tangirala , "OpenStack Development Mailing List (not for usage questions)" , discuss 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 Date: Tuesday, June 7, 2016 at 11:36 PM To: John McDowall Cc: Na Zhu , Srilatha Tangirala , "OpenStack Development Mailing List (not for usage questions)" < openstack-dev@lists.openstack.org>, discuss 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-ovnrepo 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-sfcrepo. 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 wrote: Juno, Srilatha, I need some help �C 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 Date: Monday, June 6, 2016 at 7:54 PM To: John McDowall , Ryan Moats < rmo...@us.ibm.com> Cc: "disc...@openvswitch.org" , "OpenStack Development Mailing List (not for usage questions)" < openstack-dev@lists.openstack.org>, Srilatha Tangirala < srila...@us.ibm.com> Subject: Re: [openst
Re: [openstack-dev] [neutron][SFC]
I find this issue also, I filed a bug about it https://bugs.launchpad.net/networking-sfc/+bug/1586721 I think logical-source-port can be optional. Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: na...@cn.ibm.com 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: Alioune To: "OpenStack Development Mailing List (not for usage questions)" Date: 2016/06/10 22:28 Subject:Re: [openstack-dev] [neutron][SFC] Hi Mohan, Even if I clone the master branch of networking-sfc project,I get the following errir when creating flow-classifier, therefore I do precise the logical-source-port. 2016-06-10 05:34:05.693 10799 ERROR neutron.api.v2.resource DBError: (pymysql.err.IntegrityError) (1048, u"Column 'logical_source_port' cannot be null") I'm trying the example in [1] Here is a "ovs-ofctl dump-flows" on br-int ofter creating port-chain, I expected to see vxlan or gre tunnel encapsulation entries as explained in [1], may I know why there is no tunnel entry in br-int ? sudo ovs-ofctl dump-flows br-int NXST_FLOW reply (xid=0x4): cookie=0x90444f3c8fabcbe0, duration=2840.983s, table=0, n_packets=0, n_bytes=0, idle_age=2840, priority=10,icmp6,in_port=16,icmp_type=136 actions=resubmit(,24) cookie=0x90444f3c8fabcbe0, duration=2837.039s, table=0, n_packets=0, n_bytes=0, idle_age=2837, priority=10,icmp6,in_port=17,icmp_type=136 actions=resubmit(,24) cookie=0x90444f3c8fabcbe0, duration=2831.688s, table=0, n_packets=0, n_bytes=0, idle_age=2831, priority=10,icmp6,in_port=19,icmp_type=136 actions=resubmit(,24) cookie=0x90444f3c8fabcbe0, duration=2831.038s, table=0, n_packets=0, n_bytes=0, idle_age=2831, priority=10,icmp6,in_port=18,icmp_type=136 actions=resubmit(,24) cookie=0x90444f3c8fabcbe0, duration=2801.555s, table=0, n_packets=0, n_bytes=0, idle_age=2801, priority=10,icmp6,in_port=20,icmp_type=136 actions=resubmit(,24) cookie=0x90444f3c8fabcbe0, duration=2840.605s, table=0, n_packets=8, n_bytes=336, idle_age=2591, priority=10,arp,in_port=16 actions=resubmit(,24) cookie=0x90444f3c8fabcbe0, duration=2836.759s, table=0, n_packets=0, n_bytes=0, idle_age=2836, priority=10,arp,in_port=17 actions=resubmit(,24) cookie=0x90444f3c8fabcbe0, duration=2831.485s, table=0, n_packets=0, n_bytes=0, idle_age=2831, priority=10,arp,in_port=19 actions=resubmit(,24) cookie=0x90444f3c8fabcbe0, duration=2830.816s, table=0, n_packets=21, n_bytes=882, idle_age=1605, priority=10,arp,in_port=18 actions=resubmit(,24) cookie=0x90444f3c8fabcbe0, duration=2801.309s, table=0, n_packets=10, n_bytes=420, idle_age=545, priority=10,arp,in_port=20 actions=resubmit(,24) cookie=0x90444f3c8fabcbe0, duration=15755.073s, table=0, n_packets=3241, n_bytes=366555, idle_age=545, priority=0 actions=NORMAL cookie=0x90444f3c8fabcbe0, duration=15754.687s, table=23, n_packets=0, n_bytes=0, idle_age=15754, priority=0 actions=drop cookie=0x90444f3c8fabcbe0, duration=2841.201s, table=24, n_packets=0, n_bytes=0, idle_age=2841, priority=2,icmp6,in_port=16,icmp_type=136,nd_target=fe80::f816:3eff:fe2d:c29d actions=NORMAL cookie=0x90444f3c8fabcbe0, duration=2837.177s, table=24, n_packets=0, n_bytes=0, idle_age=2837, priority=2,icmp6,in_port=17,icmp_type=136,nd_target=fe80::f816:3eff:fee0:f8ca actions=NORMAL cookie=0x90444f3c8fabcbe0, duration=2831.794s, table=24, n_packets=0, n_bytes=0, idle_age=2831, priority=2,icmp6,in_port=19,icmp_type=136,nd_target=fe80::f816:3eff:fe86:a668 actions=NORMAL cookie=0x90444f3c8fabcbe0, duration=2831.150s, table=24, n_packets=0, n_bytes=0, idle_age=2831, priority=2,icmp6,in_port=18,icmp_type=136,nd_target=fe80::f816:3eff:feb4:965f actions=NORMAL cookie=0x90444f3c8fabcbe0, duration=2801.675s, table=24, n_packets=0, n_bytes=0, idle_age=2801, priority=2,icmp6,in_port=20,icmp_type=136,nd_target=fe80::f816:3eff:fe5a:3097 actions=NORMAL cookie=0x90444f3c8fabcbe0, duration=2840.794s, table=24, n_packets=8, n_bytes=336, idle_age=2591, priority=2,arp,in_port=16,arp_spa=55.55.55.3 actions=NORMAL cookie=0x90444f3c8fabcbe0, duration=2836.901s, table=24, n_packets=0, n_bytes=0, idle_age=2836, priority=2,arp,in_port=17,arp_spa=55.55.55.4 actions=NORMAL cookie=0x90444f3c8fabcbe0, duration=2831.587s, table=24, n_packets=0, n_bytes=0, idle_age=2831, priority=2,arp,in_port=19,arp_spa=55.55.55.6 actions=NORMAL cookie=0x90444f3c8fabcbe0, duration=2830.933s, table=24, n_packets=21, n_bytes=882, idle_age=1605, priority=2,arp,in_port=18,arp_spa=55.55.55.5 actions=NORMAL cookie=0x90444f3c8fabcbe0, duration=2801.431s, table=24, n_packets=10, n_bytes=420, idle_age=545, priority=2,arp,in_port=20,arp_spa=55.55.55.8 actions=NORMAL cookie=0x90444f3c8fabcbe0, duration=15754.273s, table=24, n_packets=0, n_bytes=0, idle_age=15754, priority=0 actions=drop is there a link that explains how pipelines are created by SFC in br-int to compare with my flows entries ? Does the flow-classifier refer
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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: John McDowall To: Amitabha Biswas Cc: Na Zhu/China/IBM@IBMCN, Srilatha Tangirala , "OpenStack Development Mailing List (not for usage questions)" , discuss 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 Date: Tuesday, June 7, 2016 at 11:36 PM To: John McDowall Cc: Na Zhu , Srilatha Tangirala , "OpenStack Development Mailing List (not for usage questions)" < openstack-dev@lists.openstack.org>, discuss 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-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 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 wrote: Juno, Srilatha, I need some help �C 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 Date: Monday, June 6, 2016 at 7:54 PM To: John McDowall , Ryan Moats < rmo...@us.ibm.com> Cc: "disc...@openvswitch.org" , "OpenStack Development Mailing List (not for usage questions)" < openstack-dev@lists.openstack.org>, Srilatha Tangirala < 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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:John McDowall To:Na Zhu/China/IBM@IBMCN Cc:"disc...@openvswitch.org" , Ryan Moats , Srilatha Tangirala , "OpenStack Development Mailing List (not for usage
Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN
Hi John, Thanks your effort, So the next plan is you submit the WIP patches, then I submit test script about your code changes, do you think it is ok? Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: na...@cn.ibm.com 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: John McDowall To: Na Zhu/China/IBM@IBMCN Cc: "disc...@openvswitch.org" , "OpenStack Development Mailing List (not for usage questions)" , Srilatha Tangirala Date: 2016/06/09 00:48 Subject:Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN Juni, Thanks �C 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 Date: Wednesday, June 8, 2016 at 12:44 AM To: John McDowall Cc: "disc...@openvswitch.org" , "OpenStack Development Mailing List (not for usage questions)" < openstack-dev@lists.openstack.org>, Srilatha Tangirala < 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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:John McDowall To:Na Zhu/China/IBM@IBMCN, Srilatha Tangirala Cc:"disc...@openvswitch.org" , "OpenStack Development Mailing List (not for usage questions)" < 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 �C 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 Date: Monday, June 6, 2016 at 7:54 PM To: John McDowall , Ryan Moats < rmo...@us.ibm.com> Cc: "disc...@openvswitch.org" , "OpenStack Development Mailing List (not for usage questions)" < openstack-dev@lists.openstack.org>, Srilatha Tangirala < 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 creat
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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: John McDowall To: Na Zhu/China/IBM@IBMCN, Srilatha Tangirala Cc: "disc...@openvswitch.org" , "OpenStack Development Mailing List (not for usage questions)" 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 �C 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 Date: Monday, June 6, 2016 at 7:54 PM To: John McDowall , Ryan Moats < rmo...@us.ibm.com> Cc: "disc...@openvswitch.org" , "OpenStack Development Mailing List (not for usage questions)" < openstack-dev@lists.openstack.org>, Srilatha Tangirala < 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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:John McDowall To:Na Zhu/China/IBM@IBMCN Cc:"disc...@openvswitch.org" , Ryan Moats , Srilatha Tangirala , "OpenStack Development Mailing List (not for usage questions)" < 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 �C 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 �C 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 Date: Monday, June 6, 2016 at 5:49 AM To: John McDowall Cc: "disc...@openvswitch.org" , Ryan Moats < rmo...@us.ibm.com>, Srilatha Tangirala , "OpenStack Development Mailing List (not for usage questions)" < openstack-dev@lists.openstack.
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 If not, can you send me the link? Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: na...@cn.ibm.com 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: John McDowall To: Na Zhu/China/IBM@IBMCN, Srilatha Tangirala Cc: "disc...@openvswitch.org" , "OpenStack Development Mailing List (not for usage questions)" 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 �C 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 Date: Monday, June 6, 2016 at 7:54 PM To: John McDowall , Ryan Moats < rmo...@us.ibm.com> Cc: "disc...@openvswitch.org" , "OpenStack Development Mailing List (not for usage questions)" < openstack-dev@lists.openstack.org>, Srilatha Tangirala < 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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:John McDowall To:Na Zhu/China/IBM@IBMCN Cc:"disc...@openvswitch.org" , Ryan Moats , Srilatha Tangirala , "OpenStack Development Mailing List (not for usage questions)" < 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 �C 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 �C 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 Date: Monday, June 6, 2016 at 5:49 AM To: John McDowall Cc: "disc...@openvswitch.org" , Ryan Moats < rmo...@us.ibm.com>, Srilatha Tangirala , "OpenStack Development Mailing List (not for usage questions)" < 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 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 Cc:Srilatha Tangirala , OpenStack Development Mailing List , Ryan Moats < rmo...@us.ibm.com>, "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 pa
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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: John McDowall To: Na Zhu/China/IBM@IBMCN Cc: "disc...@openvswitch.org" , Ryan Moats , Srilatha Tangirala , "OpenStack Development Mailing List (not for usage questions)" Date: 2016/06/06 23:36 Subject:Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN Juno, Let me check �C 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 �C 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 Date: Monday, June 6, 2016 at 5:49 AM To: John McDowall Cc: "disc...@openvswitch.org" , Ryan Moats < rmo...@us.ibm.com>, Srilatha Tangirala , "OpenStack Development Mailing List (not for usage questions)" < 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 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 Cc:Srilatha Tangirala , OpenStack Development Mailing List , Ryan Moats < rmo...@us.ibm.com>, "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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:John McDowall To:Na Zhu/China/IBM@IBMCN Cc:"disc...@openvswitch.org" , "OpenStack Development Mailing List" , Ryan Moats , Srilatha Tangirala 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 �C 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 Date: Saturday, June 4, 2016 at 6:30 AM To: John McDowall Cc: "disc...@openvswitch.org" , OpenStack Development Mailing List , Ryan Moats < rmo...@us.ibm.com>, Srilatha Tangirala 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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Par
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 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 Cc: Srilatha Tangirala , OpenStack Development Mailing List , Ryan Moats , "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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:John McDowall To: Na Zhu/China/IBM@IBMCN Cc:"disc...@openvswitch.org" , "OpenStack Development Mailing List" , Ryan Moats , Srilatha Tangirala 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 �C 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 Date: Saturday, June 4, 2016 at 6:30 AM To: John McDowall Cc: "disc...@openvswitch.org" , OpenStack Development Mailing List , Ryan Moats < rmo...@us.ibm.com>, Srilatha Tangirala 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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:John McDowall To:Na Zhu/China/IBM@IBMCN Cc:"disc...@openvswitch.org" , "OpenStack Development Mailing List" , Ryan Moats , Srilatha Tangirala 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 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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:John McDowall To:Na Zhu/China/IBM@IBMCN Cc:"disc...@openvswitch.org" , "OpenStack Development Mailing List" , Ryan Moats , Srilatha Tangirala 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
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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: John McDowall To: Na Zhu/China/IBM@IBMCN Cc: "disc...@openvswitch.org" , "OpenStack Development Mailing List" , Ryan Moats , Srilatha Tangirala 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 �C 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 Date: Saturday, June 4, 2016 at 6:30 AM To: John McDowall Cc: "disc...@openvswitch.org" , OpenStack Development Mailing List , Ryan Moats < rmo...@us.ibm.com>, Srilatha Tangirala 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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: John McDowall To:Na Zhu/China/IBM@IBMCN Cc:"disc...@openvswitch.org" , "OpenStack Development Mailing List" , Ryan Moats , Srilatha Tangirala 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 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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:John McDowall To:Na Zhu/China/IBM@IBMCN Cc:"disc...@openvswitch.org" , "OpenStack Development Mailing List" , Ryan Moats , Srilatha Tangirala 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 �C I will let them speak for themselves. Regards John From: Na Zhu Date: Wednesday, June 1, 2016 at 7:02 PM To: John McDowall Cc: "disc...@openvswitch.org" , OpenStack Development Mailing List , Ryan Moats < rmo...@us.ibm.com>, Srilatha Tangirala 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:)
Re: [openstack-dev] [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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: John McDowall To: Na Zhu/China/IBM@IBMCN Cc: "disc...@openvswitch.org" , "OpenStack Development Mailing List" , Ryan Moats , Srilatha Tangirala 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 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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:John McDowall To:Na Zhu/China/IBM@IBMCN Cc:"disc...@openvswitch.org" , "OpenStack Development Mailing List" , Ryan Moats , Srilatha Tangirala 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 �C I will let them speak for themselves. Regards John From: Na Zhu Date: Wednesday, June 1, 2016 at 7:02 PM To: John McDowall Cc: "disc...@openvswitch.org" , OpenStack Development Mailing List , Ryan Moats < rmo...@us.ibm.com>, Srilatha Tangirala 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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:John McDowall To:Na Zhu/China/IBM@IBMCN Cc:Ryan Moats , OpenStack Development Mailing List , "disc...@openvswitch.org" < disc...@openvswitch.org>, Srilatha Tangirala 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://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 �C but I can help in any way you need. Regards John From: Na Zhu Date: Tuesday, May 31, 2016 at 9:02 PM To: John McDowall Cc: Ryan Moats , OpenStack Development Mailing List < openstack-dev@lists.openstack.org>, "disc...@openvswitch.org" < disc...@openvswitch.org>, Srilatha Tangirala 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.c
Re: [openstack-dev] [networking-sfc] how to install networking-sfc on compute node
Yes, but networking-sfc rewrite the q-agt binary file, when i install networking-sfc in allinone mode, the q-aget binary file is: juno@sfc:~/devstack$ cat /usr/local/bin/neutron-openvswitch-agent #!/usr/bin/python # PBR Generated from u'console_scripts' import sys from networking_sfc.services.sfc.agent.agent import main if __name__ == "__main__": sys.exit(main()) steve@sfc:~/devstack$ Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: na...@cn.ibm.com 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: Vikram Choudhary To: "OpenStack Development Mailing List (not for usage questions)" Date: 2016/06/03 15:05 Subject:Re: [openstack-dev] [networking-sfc] how to install networking-sfc on compute node On Thu, Jun 2, 2016 at 9:11 PM, Na Zhu wrote: Hi, >From this link https://github.com/openstack/networking-sfc/tree/master/devstack, it is about installing networking-sfc together with neutron-server, I want to install networking-sfc on compute node, can anyone tell me how to set the local.conf? networking-sfc support is only required on the controller node as it uses q-agt (ovs driver implementation) for downloading flows to the ovs. By default, we already run q-agt on the compute node. Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: na...@cn.ibm.com 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) __ 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 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 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
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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: John McDowall To: Na Zhu/China/IBM@IBMCN Cc: "disc...@openvswitch.org" , "OpenStack Development Mailing List" , Ryan Moats , Srilatha Tangirala 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 �C I will let them speak for themselves. Regards John From: Na Zhu Date: Wednesday, June 1, 2016 at 7:02 PM To: John McDowall Cc: "disc...@openvswitch.org" , OpenStack Development Mailing List , Ryan Moats < rmo...@us.ibm.com>, Srilatha Tangirala 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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: John McDowall To:Na Zhu/China/IBM@IBMCN Cc:Ryan Moats , OpenStack Development Mailing List , "disc...@openvswitch.org" < disc...@openvswitch.org>, Srilatha Tangirala 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://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 �C but I can help in any way you need. Regards John From: Na Zhu Date: Tuesday, May 31, 2016 at 9:02 PM To: John McDowall Cc: Ryan Moats , OpenStack Development Mailing List < openstack-dev@lists.openstack.org>, "disc...@openvswitch.org" < disc...@openvswitch.org>, Srilatha Tangirala 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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:Na Zhu/China/IBM To:John McDowall Cc:Ryan Moats , OpenStack Development Mailing List , "disc...@openvswitch.org" < 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) 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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:John McDowall To:Ryan Moats Cc:OpenSta
[openstack-dev] [networking-sfc] how to install networking-sfc on compute node
Hi, >From this link https://github.com/openstack/networking-sfc/tree/master/devstack, it is about installing networking-sfc together with neutron-server, I want to install networking-sfc on compute node, can anyone tell me how to set the local.conf? Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: na...@cn.ibm.com 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) __ 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
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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: John McDowall To: Na Zhu/China/IBM@IBMCN Cc: Ryan Moats , OpenStack Development Mailing List , "disc...@openvswitch.org" , Srilatha Tangirala 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://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 �C but I can help in any way you need. Regards John From: Na Zhu Date: Tuesday, May 31, 2016 at 9:02 PM To: John McDowall Cc: Ryan Moats , OpenStack Development Mailing List < openstack-dev@lists.openstack.org>, "disc...@openvswitch.org" < disc...@openvswitch.org>, Srilatha Tangirala 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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:Na Zhu/China/IBM To:John McDowall Cc:Ryan Moats , OpenStack Development Mailing List , "disc...@openvswitch.org" < 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) 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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From:John McDowall To:Ryan Moats Cc:OpenStack Development Mailing List < openstack-dev@lists.openstack.org>, "disc...@openvswitch.org" < disc...@openvswitch.org> Date:2016/06/01 08:58 Subject:Re: [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN Sent by:"discuss" Ryan, More help is always great :-). As far as who to collaborate, what ever Is easiest for everyone �C I am pretty flexible. Regards John From: Ryan Moats Date: Tuesday, May 31, 2016 at 1:59 PM To: John McDowall Cc: Ben Pfaff , "disc...@openvswitch.org" < disc...@openvswitch.org>, Justin Pettit , OpenStack Development Mailing List , Russell Bryant Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN John McDowall wrote on 05/31/2016 03:21:30 PM: > From: John McDowall > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: Ben Pfaff , "disc...@openvswitch.org" > , Justin Pettit , > "OpenStack Development Mailing List" d...@lists.openstack.org>, Russell Bryant > 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 wi
Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN
John, Thanks. Me and Srilatha (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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: John McDowall To: Ryan Moats Cc: OpenStack Development Mailing List , "disc...@openvswitch.org" Date: 2016/06/01 08:58 Subject:Re: [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC and OVN Sent by:"discuss" Ryan, More help is always great :-). As far as who to collaborate, what ever Is easiest for everyone �C I am pretty flexible. Regards John From: Ryan Moats Date: Tuesday, May 31, 2016 at 1:59 PM To: John McDowall Cc: Ben Pfaff , "disc...@openvswitch.org" < disc...@openvswitch.org>, Justin Pettit , OpenStack Development Mailing List , Russell Bryant Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN John McDowall wrote on 05/31/2016 03:21:30 PM: > From: John McDowall > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: Ben Pfaff , "disc...@openvswitch.org" > , Justin Pettit , > "OpenStack Development Mailing List" d...@lists.openstack.org>, Russell Bryant > 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 > Date: Tuesday, May 31, 2016 at 10:17 AM > To: John McDowall > Cc: Ben Pfaff , "disc...@openvswitch.org" < > disc...@openvswitch.org>, Justin Pettit , OpenStack > Development Mailing List , Russell Bryant < > russ...@ovn.org> > Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN > > John McDowall wrote on 05/26/2016 > 11:08:43 AM: > > > From: John McDowall > > To: Ryan Moats/Omaha/IBM@IBMUS > > Cc: Ben Pfaff , "disc...@openvswitch.org" > > , Justin Pettit , > > "OpenStack Development Mailing List" > d...@lists.openstack.org>, Russell Bryant > > 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 �C 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 > > Date: Wednesday, May 25, 2016 at 9:12 PM > > To: John McDowall > > Cc: Ben Pfaff , "disc...@openvswitch.org" < > > disc...@openvswitch.org>, Justin Pettit , OpenStack > > Development Mailing List , > Russell Bryant < > > russ...@ovn.org> > > Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN > > > > John McDowall wrote on 05/25/2016 > > 07:27:46 PM: > > > > > From: John McDowall > > > To: Ryan Moats/Omaha/IBM@IBMUS > > > Cc: "disc...@openvswitch.org" , "OpenStack > > > Development Mailing List" , Ben > > > Pfaff , Justin Pettit , Russell Bryant > > > > > > Date: 05/25/2016 07:28 PM > > > Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN > > > > > > Ryan, > > > > > > Ok �C 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 repre
Re: [openstack-dev] [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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: Na Zhu/China/IBM To: John McDowall Cc: Ryan Moats , OpenStack Development Mailing List , "disc...@openvswitch.org" Date: 2016/06/01 12:01 Subject:Re: [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC and OVN John, Thanks. Me and Srilatha (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 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: John McDowall To: Ryan Moats Cc: OpenStack Development Mailing List , "disc...@openvswitch.org" Date: 2016/06/01 08:58 Subject:Re: [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC and OVN Sent by:"discuss" Ryan, More help is always great :-). As far as who to collaborate, what ever Is easiest for everyone �C I am pretty flexible. Regards John From: Ryan Moats Date: Tuesday, May 31, 2016 at 1:59 PM To: John McDowall Cc: Ben Pfaff , "disc...@openvswitch.org" < disc...@openvswitch.org>, Justin Pettit , OpenStack Development Mailing List , Russell Bryant Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN John McDowall wrote on 05/31/2016 03:21:30 PM: > From: John McDowall > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: Ben Pfaff , "disc...@openvswitch.org" > , Justin Pettit , > "OpenStack Development Mailing List" d...@lists.openstack.org>, Russell Bryant > 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 > Date: Tuesday, May 31, 2016 at 10:17 AM > To: John McDowall > Cc: Ben Pfaff , "disc...@openvswitch.org" < > disc...@openvswitch.org>, Justin Pettit , OpenStack > Development Mailing List , Russell Bryant < > russ...@ovn.org> > Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN > > John McDowall wrote on 05/26/2016 > 11:08:43 AM: > > > From: John McDowall > > To: Ryan Moats/Omaha/IBM@IBMUS > > Cc: Ben Pfaff , "disc...@openvswitch.org" > > , Justin Pettit , > > "OpenStack Development Mailing List" > d...@lists.openstack.org>, Russell Bryant > > 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 �C 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 >
Re: [openstack-dev] [neutron] OSC transition
Hi Darek, Thanks your information, but the BGP commands are not list in here https://etherpad.openstack.org/p/osc-neutron-support :( Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: na...@cn.ibm.com 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: Darek Smigiel To: "OpenStack Development Mailing List (not for usage questions)" Date: 2016/05/05 02:34 Subject:Re: [openstack-dev] [neutron] OSC transition On May 4, 2016, at 6:10 AM, Na Zhu wrote: Hi Richard, I read the contents in the link, I think the discussion in Austin summit have not updated to the webpage. But from here https://etherpad.openstack.org/p/newton-neutron-future-neutron-client, it mentions python-neutronclient provides OSC plugin for neutron-*aas, does it mean all neutron-*aas CLIs still live in python-neutronclient repo? If yes, should every neutron-*aas owner updates the CLIs from neutron to openstack? I found Dean Troyer set the [Blueprint neutron-client] implement neutron commandsstate to obsolete, does the OSC transition continue move along? Transition is in progress. Here you have spec for it [1]. Probably the most important thing for you is this [2] where all required commands are described. [1] http://docs.openstack.org/developer/python-neutronclient/devref/transition_to_osc.html [2] https://etherpad.openstack.org/p/osc-neutron-support Darek Smigiel (dasm) __ 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 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] OSC transition
Hi Richard, So what is the conclusion of where to put *aas CLI? Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: na...@cn.ibm.com 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: Richard Theis To: "OpenStack Development Mailing List \(not for usage questions\)" Date: 2016/04/26 22:32 Subject:Re: [openstack-dev] [neutron] OSC transition Hi, The latest devref [1] would place it in python-neutronclient as Henry noted. But stay tuned for results from the summit session. [1] https://github.com/openstack/python-neutronclient/blob/master/doc/source/devref/transition_to_osc.rst - Richard "Na Zhu" wrote on 04/26/2016 08:29:21 AM: > From: "Na Zhu" > To: hen...@gessau.net > Cc: "OpenStack Development Mailing List \(not for usage questions\)" > > Date: 04/26/2016 08:34 AM > Subject: Re: [openstack-dev] [neutron] OSC transition > > Hi Henry, > > Thanks your information, why you think neutron-dynamic-routing CLI > should live in python-neutronclient? > From this link http://docs.openstack.org/developer/python- > neutronclient/devref/transition_to_osc.htmlsection "Where does my CLI belong? > ", *aas CLI belongs to their own project, not project python- > neutronclient. BGP is also service like *aas, so I think BGP CLIs > should live in neutron-dynamic-routing, or a separate repo named > python-*client. Pls correct me if I am wrong, thanks. > > > > Regards, > Juno Zhu > IBM China Development Labs (CDL) Cloud IaaS Lab > Email: na...@cn.ibm.com > 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong > New District, Shanghai, China (201203) > > > > From:Henry Gessau > To:"OpenStack Development Mailing List (not for usage > questions)" > Date:2016/04/26 21:09 > Subject:Re: [openstack-dev] [neutron] OSC transition > > > > Adding the [neutron] tag. > > I believe that the OSC extension for neutron-dynamic-routing should live in > the python-neutronclient repo. Keep in touch with Richard Theis as he is the > one leading the transition to OSC. He is rtheis on IRC. > > See: > http://lists.openstack.org/pipermail/openstack-dev/2016-April/093139.html > https://review.openstack.org/309587 > > > Na Zhu wrote: > > Dear All, > > > > > > I have a question about OSC transition, recently, the community approves > > moving bgp out of neutron, as a service like other *aas. The BGP > CLIs need be > > removed from neutronclient. Because of OSC transition, I can not > just move the > > BGP CLIs code from python-neutronclient repo to neutron-dynamic- > routing repo. > > I have to refactor the code and do transition to OSC plugin system. > > > > From the > > link _http://docs.openstack.org/developer/python-openstackclient/ > plugins.html_, the > > client has a separate repo, take designate as example, the CLI repo is > > python-designateclient, the project repo is designate. So for BGP, should I > > create a repo for CLI, or leverage project repo neutron-dynamic-routing? > > > > > > > > > > Regards, > > Juno Zhu > > IBM China Development Labs (CDL) Cloud IaaS Lab > > Email: na...@cn.ibm.com > > 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New > > District, Shanghai, China (201203) > > > > > > __ > > 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 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 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 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 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] OSC transition
Hi Henry, Thanks your information, why you think neutron-dynamic-routing CLI should live in python-neutronclient? >From this link http://docs.openstack.org/developer/python-neutronclient/devref/transition_to_osc.html section "Where does my CLI belong? ", *aas CLI belongs to their own project, not project python-neutronclient. BGP is also service like *aas, so I think BGP CLIs should live in neutron-dynamic-routing, or a separate repo named python-*client. Pls correct me if I am wrong, thanks. Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: na...@cn.ibm.com 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) From: Henry Gessau To: "OpenStack Development Mailing List (not for usage questions)" Date: 2016/04/26 21:09 Subject:Re: [openstack-dev] [neutron] OSC transition Adding the [neutron] tag. I believe that the OSC extension for neutron-dynamic-routing should live in the python-neutronclient repo. Keep in touch with Richard Theis as he is the one leading the transition to OSC. He is rtheis on IRC. See: http://lists.openstack.org/pipermail/openstack-dev/2016-April/093139.html https://review.openstack.org/309587 Na Zhu wrote: > Dear All, > > > I have a question about OSC transition, recently, the community approves > moving bgp out of neutron, as a service like other *aas. The BGP CLIs need be > removed from neutronclient. Because of OSC transition, I can not just move the > BGP CLIs code from python-neutronclient repo to neutron-dynamic-routing repo. > I have to refactor the code and do transition to OSC plugin system. > > From the > link _http://docs.openstack.org/developer/python-openstackclient/plugins.html_, the > client has a separate repo, take designate as example, the CLI repo is > python-designateclient, the project repo is designate. So for BGP, should I > create a repo for CLI, or leverage project repo neutron-dynamic-routing? > > > > > Regards, > Juno Zhu > IBM China Development Labs (CDL) Cloud IaaS Lab > Email: na...@cn.ibm.com > 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New > District, Shanghai, China (201203) > > > __ > 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 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 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] OSC transition
Dear All, I have a question about OSC transition, recently, the community approves moving bgp out of neutron, as a service like other *aas. The BGP CLIs need be removed from neutronclient. Because of OSC transition, I can not just move the BGP CLIs code from python-neutronclient repo to neutron-dynamic-routing repo. I have to refactor the code and do transition to OSC plugin system. >From the link http://docs.openstack.org/developer/python-openstackclient/plugins.html, the client has a separate repo, take designate as example, the CLI repo is python-designateclient, the project repo is designate. So for BGP, should I create a repo for CLI, or leverage project repo neutron-dynamic-routing? Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: na...@cn.ibm.com 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New District, Shanghai, China (201203) __ 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] Why need br-int and br-tun in openstack neutron
Dear, When OVS plugin is used with GRE option in Neutron, I see that each compute node has br-tun and br-int bridges created. I'm trying to understand why we need the additional br-tun bridge here. Can't we create tunneling ports in br-int bridge, and have br-int relay traffic between VM ports and tunneling ports directly? Why do we have to introduce another br-tun bridge? Regards, Juno Zhu Staff Software Engineer, System Networking China Systems and Technology Lab (CSTL), IBM Wuxi Email: na...@cn.ibm.com__ 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