<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Ryan,</div>
<div><br>
</div>
<div>Thanks – let me try and get the code cleaned up and rebased. One area that I could use your insight on is the interface to networking-ovn and how it should look. </div>
<div><br>
</div>
<div>Regards</div>
<div><br>
</div>
<div>John</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<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 style="font-weight:bold">From: </span>Ryan Moats <<a href="mailto:rmoats@us.ibm.com">rmoats@us.ibm.com</a>><br>
<span style="font-weight:bold">Date: </span>Sunday, May 8, 2016 at 8:32 PM<br>
<span style="font-weight:bold">To: </span>John McDowall <<a href="mailto:jmcdowall@paloaltonetworks.com">jmcdowall@paloaltonetworks.com</a>><br>
<span style="font-weight:bold">Cc: </span>"<a href="mailto:discuss@openvswitch.org">discuss@openvswitch.org</a>" <<a href="mailto:discuss@openvswitch.org">discuss@openvswitch.org</a>>, OpenStack Development Mailing List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN<br>
</div>
<div><br>
</div>
<div>
<div>
<p><tt>John McDowall <<a href="mailto:jmcdowall@paloaltonetworks.com">jmcdowall@paloaltonetworks.com</a>> wrote on 05/08/2016 07:34:52 PM:<br>
<br>
> From: John McDowall <<a href="mailto:jmcdowall@paloaltonetworks.com">jmcdowall@paloaltonetworks.com</a>></tt><br>
<tt>> To: Ryan Moats/Omaha/IBM@IBMUS</tt><br>
<tt>> Cc: "<a href="mailto:discuss@openvswitch.org">discuss@openvswitch.org</a>" <<a href="mailto:discuss@openvswitch.org">discuss@openvswitch.org</a>></tt><br>
<tt>> Date: 05/08/2016 07:35 PM</tt><br>
<tt>> Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN</tt><br>
<tt>> <br>
> Correcting ovs address</tt><br>
<tt>> <br>
> Ryan,</tt><br>
<tt>> <br>
> Thanks for taking a look at these - really appreciate it. I will <br>
> work on the rebasing this week and get everything current. At the <br>
> same time I can get rid of some excess code as I went through a few <br>
> iterations to get to this point. There are still a lot of <br>
> unaddressed edge conditions and details that need to be thought <br>
> through and addressed – but once we reach consensus on the approach <br>
> we can start to address them.</tt><br>
<tt>> <br>
> Thinking though the various repos in reverse order.</tt><br>
<tt>> <br>
> OVS</tt><br>
<tt>> ===</tt><br>
<tt>> <br>
> I would like to change the code to follow the model that Russell <br>
> Bryant did in his patches see: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_russellb_ovs_&d=CwMGaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=vZ6VUDaavDpfOdPQrz1ED54jEjvAE36A8TVJroVlrOQ&m=_f4gjpVAKVX0PU6jpEYOKtT1OLwmrOSgMc0fjASz5JI&s=VyzaLKG-WTtwNtnzunX-dImm0lA0rUAiYgPMrieHJO4&e=">https://github.com/russellb/ovs/</a><br>
> commits/chaining</tt><br>
<tt>> <br>
> They have several advantages:</tt><br>
<tt>> 1. Creates a new table for chaining which should help isolate the <br>
> code and make chaining more “atomic” </tt><br>
<tt>> 2. He follows the port-pair/port-chain model of SFC so integration <br>
> should be cleaner</tt><br>
<tt>> 3. Following the port-pair/port-chain model makes extending the <br>
> solution to handle a chain of VNFs fairly easy.</tt><br>
<tt>> If everyone is good with this I can work this into the patches and rebase.</tt><br>
<br>
<tt>You are anticipating where I was looking to go, so I'm on board with</tt><br>
<tt>this idea.</tt><br>
<br>
<tt>> Networking-OVN</tt><br>
<tt>> ===============</tt><br>
<tt>> <br>
> There is some old code here in plugin.py that I think comes out. <br>
> When I added OVN as a SFC Driver there was a lot of code that I <br>
> added to networking-ovn that became obsolete. The IDL code would be<br>
> modified to follow the port-pair/port-chain. model. The biggest <br>
> question I have from your comments is the interface between the <br>
> networking-sfc and networking-ovn. I think I agree with you that <br>
> networking-ovn should expose an interface that is called by <br>
> networking-sfc and that would remove the need to subclass OVNPlugin <br>
> in the networking-sfc OVN driver. Is that what you were intending?</tt><br>
<br>
<tt>Yes, I was looking at how that subclass could be avoided.</tt><br>
<br>
<tt>> Networking-SFC</tt><br>
<tt>> ==============</tt><br>
<tt>> <br>
> If we follow Russell’s model in OVN/OVS then there very close <br>
> alignment with the SFC model and the code will become simpler. Also <br>
> removing the OVNPlugin dependency will also clean things up.</tt><br>
<br>
<tt>Yes, I was hoping that would be a side effect as well...</tt><br>
<br>
<tt>I like all of your proposed ideas and am looking forward to seeing</tt><br>
<tt>the next iteration. Please feel free to reach out if you need</tt><br>
<tt>another pair of hands to help with coding...</tt><br>
<br>
<tt>Ryan Moats</tt><br>
</p>
</div>
</div>
</span>
</body>
</html>