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

; Date: 06/17/2016 05:25 PM > Subject: Re: [ovs-discuss] [openstack-dev] [OVN] [networking-ovn] > [networking-sfc] SFC andOVN > Sent by: "discuss" > > Hi Juno, > > Here is an example. > > SrcSF DST > | | | | > 1

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

ss , Na Zhu , > "OpenStack Development Mailing List (not for usage questions)" < > openstack-...@lists.openstack.org>, Srilatha Tangirala > Subject: Re: [ovs-discuss] [openstack-dev] [OVN] [networking-ovn] > [networking-sfc] SFC andOVN > > Apologies for being delayed on rep

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

, "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-...@lists.openstack.org>>, discuss mailto:discuss@openvswitch.org>> Subject: Re: [ovs-discuss] [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC andOVN In-line below "discuss"

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

evelopment Mailing List (not for usage questions)" mailto:openstack-...@lists.openstack.org>>, Srilatha Tangirala mailto:srila...@us.ibm.com>> Subject: Re: [ovs-discuss] [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC andOVN Apologies for being delayed on replying

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

6/15/2016 05:51 PM > Subject: Re: [ovs-discuss] [openstack-dev] [OVN] [networking-ovn] > [networking-sfc] SFC andOVN > Sent by: "discuss" > > Juno, > > Apologies – I see your issue now, also I have got nothing done today > – got sucked into an all day meeting.

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

st (not for usage > questions)" , discuss > > Date: 06/15/2016 05:58 PM > Subject: Re: [ovs-discuss] [openstack-dev] [OVN] [networking-ovn] > [networking-sfc] SFC andOVN > > Ryan, > > In-line > > Regards > > John > > From: Ryan Moats > Date: Tuesday,

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

ack Development Mailing List (not for usage questions)" mailto:openstack-...@lists.openstack.org>>, discuss mailto:discuss@openvswitch.org>> Subject: Re: [ovs-discuss] [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC andOVN "discuss" mailto:discuss-bo

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

ech 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-...@lists.openstack.org>, discuss Date:

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

h.org" Date: 2016/06/15 13:59 Subject: Re: [ovs-discuss] [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC andOVN Sent by:"discuss" Hi Juno, Each flow-classifier has a mandatory logical-source port (mandatory for OVS driver). If it is mandatory for

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

Tangirala , "OpenStack Development     Mailing List \(not for usage questions\)"     , discuss Subject: Re: [ovs-discuss] [openstack-dev] [OVN] [networking-ovn]     [networking-sfc] SFC andOVN Message-ID:     Content-Type: text/plain; charset="gb2312" John, Here is the ste

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

" 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.

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

6 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.

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

m 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)" < op

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

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

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

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 (n

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

velopment Mailing List (not for usage questions)" < openstack-...@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

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

Mailing List (not for usage questions)" < openstack-...@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

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

ngirala mailto:srila...@us.ibm.com>>, "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-...@lists.openstack.org>>, discuss mailto:discuss@openvswitch.org>> Date:2016/06/09 00:53 Subject:Re: [ovs-discuss] [openstack-dev] [OVN] [n

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

John McDowall mailto:jmcdow...@paloaltonetworks.com>> To:Amitabha Biswas mailto:azbis...@gmail.com>> Cc:Na Zhu/China/IBM@IBMCN, Srilatha Tangirala mailto:srila...@us.ibm.com>>, "OpenStack Development Mailing List (not for usage questions)

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

Tangirala , "OpenStack Development Mailing List (not for usage questions)" < openstack-...@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 .

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

Na Zhu/China/IBM@IBMCN, Srilatha Tangirala , "OpenStack Development Mailing List (not for usage questions)" < openstack-...@lists.openstack.org>, discuss Date: 2016/06/09 00:53 Subject: Re: [ovs-discuss] [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC andOVN A

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

mail.com>> Cc:Na Zhu/China/IBM@IBMCN, Srilatha Tangirala mailto:srila...@us.ibm.com>>, "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-...@lists.openstack.org>>, discuss mailto:discuss@openvswitch.org>> Date:

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

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

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

: 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]

Re: [ovs-discuss] [openstack-dev] [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

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

Juno, Ok added the code and I have port-chains creating up to the IDL networking-sfc->networking-ovn then I have an issue with my IDL I need to fix. So we have a model for creating port-chains all the way through, updated the repos to reflect the changes. Thanks for your help. Regards John

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

cDowall <mailto:jmcdow...@paloaltonetworks.com>> > Cc: Na Zhu mailto:na...@cn.ibm.com>>, Srilatha Tangirala > mailto:srila...@us.ibm.com>>, "OpenStack Development > Mailing List (not for usage questions)" <mailto:openstack-...@lists.openstack.org>>, disc

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

questions)" mailto:openstack-...@lists.openstack.org>>, discuss mailto:discuss@openvswitch.org>> Subject: Re: [ovs-discuss] [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC andOVN Hi John, Looking at the code with Srilatha, it seems like the https://github.com/doonhammer/networking<

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

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

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

Juno, Sorry jumped the gun not published yet :-(. Will send you the link when it is published. Apologies John From: Na Zhu mailto:na...@cn.ibm.com>> Date: Wednesday, June 8, 2016 at 1:41 AM To: John McDowall mailto:jmcdow...@paloaltonetworks.com>> Cc: "discuss@openvswitch.org

Re: [ovs-discuss] [openstack-dev] [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

Re: [ovs-discuss] [openstack-dev] [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

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 trans

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

Juno, Srilatha, I need some help – I have fixed most of the obvious typo’s in the three repos and merged them with mainline. There is still a problem with the build I think in mech_driver.py but I will fix it asap in the am. However I am not sure of the best way to interface between sfc and ovn

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

Srilatha, I am trying to get these resolved but my devstack is broken and I am truing to resolve it. Let me try and manual edit this and fix it – it is left over from the old API before I moved to the port-chain api. Regards John From: Srilatha Tangirala mailto:srila...@us.ibm.com>> Date: Mo

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

Hi John, To get started with adding test scripts, I was trying to workout one end to end flow with the latest code from your private repos and found the following. create_port_chain is calling _create_ovn_vnf. This is calling self._ovn.create_lservice( lservice_name = 'sfi-%s'

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

Hi John, To get started with adding test scripts, I was trying to workout one end to end flow with the latest code from your private repos and found the following. create_port_chain is calling _create_ovn_vnf. This is calling self.*_ovn.create_lservice*( lservice_name = 'sfi-%s' % ovn_info['id'],

Re: [ovs-discuss] [openstack-dev] [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 t

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

Juno, Let me check – my intention was that the networking-sfc OVNB driver would configure all aspects of the port-chain and add the parameters to the networking-sfc db. Once all the parameters were in the creation of a port-chain would call networking-ovn (passing a deep copy of the port-chain

Re: [ovs-discuss] [openstack-dev] [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 net