<div class="socmaildefaultfont" dir="ltr" style="font-family:Arial;font-size:10.5pt" ><div dir="ltr" >John-</div>
<div dir="ltr" > </div>
<div dir="ltr" >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.</div>
<div dir="ltr" > </div>
<div dir="ltr" >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)...</div>
<div dir="ltr" > </div>
<div dir="ltr" >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 ...)</div>
<div dir="ltr" > </div>
<div dir="ltr" >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</div>
<div dir="ltr" >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.</div>
<div dir="ltr" > </div>
<div dir="ltr" >Does that make sense?</div>
<div dir="ltr" > </div>
<div dir="ltr" >Ryan</div>
<div dir="ltr" > </div>
<blockquote data-history-content-modified="1" data-history-expanded="1" dir="ltr" style="border-left:solid #aaaaaa 2px; margin-left:5px; padding-left:5px; direction:ltr; margin-right:0px" >----- Original message -----<br>From: John McDowall <jmcdowall@paloaltonetworks.com><br>To: Ryan Moats/Omaha/IBM@IBMUS<br>Cc: "discuss@openvswitch.org" <discuss@openvswitch.org>, "OpenStack Development Mailing List" <openstack-dev@lists.openstack.org><br>Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN<br>Date: Wed, May 18, 2016 3:55 PM<br> <br><!--Notes ACF
<meta http-equiv="Content-Type" content="text/html; charset=utf8" >-->
<div>Ryan,</div>
<div> </div>
<div>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.</div>
<div> </div>
<div><a href="https://github.com/doonhammer/networking-sfc" target="_blank" >https://github.com/doonhammer/networking-sfc</a> </div>
<div><a href="https://github.com/doonhammer/networking-ovn" target="_blank" >https://github.com/doonhammer/networking-ovn</a></div>
<div><a href="https://github.com/doonhammer/ovs" target="_blank" >https://github.com/doonhammer/ovs</a> </div>
<div> </div>
<div>The next tasks I see are:</div>
<div> </div>
<div> </div>
<ol> <li>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.</li> <li>Align the interface between networking-ovn and ovs/ovn to match the nested dictionary in 1.</li> <li>Modify the ovn-nb schema and ovn-northd.c to march the port-chain model.</li> <li>Add ability to support chain of port-pairs</li> <li>Think about flow-classifiers and how best to map them, today I just map the logical-port and ignore everything else.</li></ol>
<div> </div>
<div>Any other suggestions/feedback?</div>
<div> </div>
<div>Regards</div>
<div> </div>
<div>John</div>
<div> </div><span id="OLK_SRC_BODY_SECTION" > </span>
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt" ><span id="OLK_SRC_BODY_SECTION" ><span style="font-weight:bold" >From: </span>Ryan Moats <<a href="mailto:rmoats@us.ibm.com" target="_blank" >rmoats@us.ibm.com</a>><br><span style="font-weight:bold" >Date: </span>Wednesday, May 11, 2016 at 1:39 PM<br><span style="font-weight:bold" >To: </span>John McDowall <<a href="mailto:jmcdowall@paloaltonetworks.com" target="_blank" >jmcdowall@paloaltonetworks.com</a>><br><span style="font-weight:bold" >Cc: </span>"<a href="mailto:discuss@openvswitch.org" target="_blank" >discuss@openvswitch.org</a>" <<a href="mailto:discuss@openvswitch.org" target="_blank" >discuss@openvswitch.org</a>>, OpenStack Development Mailing List <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank" >openstack-dev@lists.openstack.org</a>><br><span style="font-weight:bold" >Subject: </span>Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN</span></div><span id="OLK_SRC_BODY_SECTION" > </span>
<div> </div><span id="OLK_SRC_BODY_SECTION" > </span>
<div><div><p><span id="OLK_SRC_BODY_SECTION" ><tt>John McDowall <<a href="mailto:jmcdowall@paloaltonetworks.com" target="_blank" >jmcdowall@paloaltonetworks.com</a>> wrote on 05/11/2016 12:37:40 PM:<br><br>> From: John McDowall <<a href="mailto:jmcdowall@paloaltonetworks.com" target="_blank" >jmcdowall@paloaltonetworks.com</a>></tt><br><tt>> To: Ryan Moats/Omaha/IBM@IBMUS</tt><br><tt>> Cc: "<a href="mailto:discuss@openvswitch.org" target="_blank" >discuss@openvswitch.org</a>" <<a href="mailto:discuss@openvswitch.org" target="_blank" >discuss@openvswitch.org</a>>, "OpenStack<br>> Development Mailing List" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank" >openstack-dev@lists.openstack.org</a>></tt><br><tt>> Date: 05/11/2016 12:37 PM</tt><br><tt>> Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN</tt><br><tt>><br>> Ryan,</tt><br><tt>><br>> I have done networking-sfc the files that I see as changed/added are:</tt><br><tt>><br>> devstack/settings Modified Runtime setting to pick up OVN Driver</tt><br><tt>> networking_sfc/db/migration/alembic_migrations/versions/mitaka/<br>> expand/5a475fc853e6_ovs_data_model.py Hack to work around<br>> flow_classifier issue – need to resolve with SFC team.</tt><br><tt>> networking_sfc/services/sfc/drivers/ovn/__init__.py Added for OVN Driver</tt><br><tt>> networking_sfc/services/sfc/drivers/ovn/driver.py Added ovn driver file</tt><br><tt>> setup.cfg Inserted OVN driver entry</tt><br><tt>><br>> I am currently working to clean up ovs/ovn.</tt><br><tt>><br>> Regards</tt><br><tt>><br>> John</tt><br><br><tt>I can confirm that the networking-sfc rebase goes in clean against</tt><br><tt>master for me :) - Looking forward to ovs ...</tt><br><br><tt>Ryan</tt></span></p></div></div><span id="OLK_SRC_BODY_SECTION" > </span></blockquote>
<div dir="ltr" > </div></div><BR>