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

[ovs-discuss] With Openvswitch 2.5.0: Error while adding port to bridge

Hi Team, We were trying to integrate OpenVswitch 2.5.0 version to work with Openstack. http://openvswitch.org/releases/openvswitch-2.5.0.tar.gz After installing OVS 2.5.0, could see that we are not able to add ports to the bridge. Nova also fails due to this same error, since it is unable to a

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] ovn icmp reply part 2: how should it handle broadcast destination address?

On Wed, Jun 8, 2016 at 4:00 PM, Flaviof wrote: > > > On Wed, Jun 8, 2016 at 3:43 PM, Justin Pettit wrote: > >> >> > On Jun 8, 2016, at 11:42 AM, Flaviof wrote: >> > >> > On Wed, Jun 8, 2016 at 2:10 PM, Darrell Ball wrote: >> > >> > On Wed, Jun 8, 2016 at 6:38 AM, Flaviof wrote: >> > >> > As a

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

I didn’t see that idea earlier, +2 to it :) Regards Amitabha > On Jun 8, 2016, at 9:52 AM, John McDowall > wrote: > > 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

Re: [ovs-discuss] ovn icmp reply part 2: how should it handle broadcast destination address?

On Wed, Jun 8, 2016 at 3:43 PM, Justin Pettit wrote: > > > On Jun 8, 2016, at 11:42 AM, Flaviof wrote: > > > > On Wed, Jun 8, 2016 at 2:10 PM, Darrell Ball wrote: > > > > On Wed, Jun 8, 2016 at 6:38 AM, Flaviof wrote: > > > > As a continuation of the topic on ICMP reply rules [ml], I could not

Re: [ovs-discuss] ovn icmp reply part 2: how should it handle broadcast destination address?

> On Jun 8, 2016, at 11:42 AM, Flaviof wrote: > > On Wed, Jun 8, 2016 at 2:10 PM, Darrell Ball wrote: > > On Wed, Jun 8, 2016 at 6:38 AM, Flaviof wrote: > > As a continuation of the topic on ICMP reply rules [ml], I could not help but > notice that in the logical flow, there is a match not

Re: [ovs-discuss] ovn icmp reply part 2: how should it handle broadcast destination address?

On Wed, Jun 8, 2016 at 6:38 AM, Flaviof wrote: > [cc: Darrel, Ben, Justin] > > Hi folks, > > As a continuation of the topic on ICMP reply rules [ml], I could not help > but notice that in the logical flow, there is a match not only for the > logical routers's IP address but also for the L3 broadc

Re: [ovs-discuss] ovn icmp reply part 2: how should it handle broadcast destination address?

On Wed, Jun 8, 2016 at 2:10 PM, Darrell Ball wrote: > > > On Wed, Jun 8, 2016 at 6:38 AM, Flaviof wrote: > >> [cc: Darrel, Ben, Justin] >> >> Hi folks, >> >> As a continuation of the topic on ICMP reply rules [ml], I could not help >> but notice that in the logical flow, there is a match not onl

Re: [ovs-discuss] Persistent loglevel?

On Tue, Jun 07, 2016 at 04:50:16PM -0400, Daniel Rosenzweig wrote: > I know that I can set a runtime log-level with: > ovs-appctl vlog/set > > I know that I can manually set ovsdb-server and ovs-vswitchd with the -v > options. > > BUT - I want to have everything come up with the proper loglevel

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

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

[ovs-discuss] Persistent loglevel?

I know that I can set a runtime log-level with: ovs-appctl vlog/set I know that I can manually set ovsdb-server and ovs-vswitchd with the -v options. BUT - I want to have everything come up with the proper loglevel upon boot. I don't see any way of passing loglevels from ovs-ctl down to the da

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] OpenFlow Vendor Message

On Wed, Jun 08, 2016 at 12:06:28PM +0200, Jannis Ohms wrote: > OpenFlow provides an extension message for vendors. > The FAQ indicates that I would have to change some code and add my own. > After this, I would have to rebuild OVS. > > Since OVS is used in some white box NOS Systems like Picos I w

[ovs-discuss] ovn icmp reply part 2: how should it handle broadcast destination address?

[cc: Darrel, Ben, Justin] Hi folks, As a continuation of the topic on ICMP reply rules [ml], I could not help but notice that in the logical flow, there is a match not only for the logical routers's IP address but also for the L3 broadcast (op->bcast) of the subnet [1]. So I -- the curious cat --

Re: [ovs-discuss] [OVN] OVN chassis processes terminate problem

Han Zhou wrote on 06/07/2016 08:17:38 PM: > From: Han Zhou > To: Hui Kang/Watson/IBM@IBMUS > Cc: Ben Pfaff , "discuss@openvswitch.org" > > Date: 06/07/2016 08:17 PM > Subject: Re: [ovs-discuss] [OVN] OVN chassis processes terminate problem > > On Fri, May 27, 2016 at 9:46 AM, Hui Kang wrote

[ovs-discuss] OpenFlow Vendor Message

OpenFlow provides an extension message for vendors. The FAQ indicates that I would have to change some code and add my own. After this, I would have to rebuild OVS. Since OVS is used in some white box NOS Systems like Picos I would have to rebuild the whole OVS for my switch. It would be much

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