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

Mon, 23 May 2016 20:01:31 -0700

John-
 
My apologies for not answering this sooner - I was giving a two day training on Tues/Wed last week and came back to my son graduating from HS the next day, so thiings have been a bit of a whirlwind here.
 
Looking at the github repos, I like the idea of passing a dictionary from networking-sfc to networking-ovn.  The flow classifiers should be relatively straightforward to map to ovs match rules (famous last words)...
 
I've probably missed an orbit here, but in the ovn-northd implementation, I was expecting to find service chains in the egress and router pipelines in addition to the ingress pipeline (see below for why I think a service chain stage in the egress pipeline makes sense ...)
 
Also, in the ovn-northd implementation, I'm a little disturbed to see the ingress side of the service chain sending packets to output ports - I think that a more
scalable (and more "ovs" approach) would be to match the egress side of a port pair in the chaining stage of the ingress pipeline, with an action that  set the input port register.  Then the egress pipeline would have a chaining stage where the output port register would be set based on the ingress port of the next port pair in the chain and the packet being punted to the proper output port in the last table.  That should automagically build your function chain and provider the bases for bucketizing multiple ingress ports for the next port group to support hash based load balancing.
 
Does that make sense?
 
Ryan
 
----- Original message -----
From: John McDowall <[email protected]>
To: Ryan Moats/Omaha/IBM@IBMUS
Cc: "[email protected]" <[email protected]>, "OpenStack Development Mailing List" <[email protected]>
Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN
Date: Wed, May 18, 2016 3:55 PM
 
Ryan,
 
OK all three repos and now aligned with their masters. I have done some simple level system tests and I can steer traffic to a single VNF.  Note: some additional changes to networking-sfc to catch-up with their changes.
 
 
The next tasks I see are:
 
 
  1. Decouple networking-sfc and networking-ovn. I am thinking that I will pass a nested port-chain dictionary holding port-pairs/port-pair-groups/flow-classifiers from networking-sfc to networking-ovn.
  2. Align the interface between networking-ovn and ovs/ovn to match the nested dictionary in 1.
  3. Modify the ovn-nb schema and ovn-northd.c to march the port-chain model.
  4. Add ability to support chain of port-pairs
  5. Think about flow-classifiers and how best to map them, today I just map the logical-port and ignore everything else.
 
Any other suggestions/feedback?
 
Regards
 
John
 
From: Ryan Moats <[email protected]>
Date: Wednesday, May 11, 2016 at 1:39 PM
To: John McDowall <[email protected]>
Cc: "[email protected]" <[email protected]>, OpenStack Development Mailing List <[email protected]>
Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN
 

John McDowall <[email protected]> wrote on 05/11/2016 12:37:40 PM:

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

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

Ryan

 

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to