<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">
Ryan,</div>
<div style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">
See inline</div>
<div style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">
Regards</div>
<div style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">
John</div>
<div style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">
<br>
</div>
<span id="OLK_SRC_BODY_SECTION" style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">
<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>Friday, June 17, 2016 at 7:26 AM<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>discuss <<a href="mailto:discuss@openvswitch.org">discuss@openvswitch.org</a>>, Na Zhu <<a href="mailto:nazhu@cn.ibm.com">nazhu@cn.ibm.com</a>>, "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>>,
Srilatha Tangirala <<a href="mailto:srilatta@us.ibm.com">srilatta@us.ibm.com</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [ovs-discuss] [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC andOVN<br>
</div>
<div><br>
</div>
<div>
<div>
<p><tt>Apologies for being delayed on replying and in-line back as well</tt><br>
<br>
<tt>Ryan</tt><br>
<br>
<tt>John McDowall <<a href="mailto:jmcdowall@paloaltonetworks.com">jmcdowall@paloaltonetworks.com</a>> wrote on 06/15/2016 05:58:35 PM:<br>
</tt><tt><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: Na Zhu <<a href="mailto:nazhu@cn.ibm.com">nazhu@cn.ibm.com</a>>, Srilatha Tangirala/San Francisco/<br>
> IBM@IBMUS, "OpenStack Development Mailing List (not for usage <br>
> questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>>, discuss
<br>
> <<a href="mailto:discuss@openvswitch.org">discuss@openvswitch.org</a>></tt><br>
<tt>> Date: 06/15/2016 05:58 PM</tt><br>
<tt>> Subject: Re: [ovs-discuss] [openstack-dev] [OVN] [networking-ovn] <br>
> [networking-sfc] SFC andOVN</tt><br>
<tt>> <br>
> Ryan,</tt><br>
<tt>> <br>
> In-line</tt><br>
<tt>> <br>
> Regards</tt><br>
<tt>> <br>
> John</tt><br>
<tt>> <br>
> From: Ryan Moats <<a href="mailto:rmoats@us.ibm.com">rmoats@us.ibm.com</a>><br>
> Date: Tuesday, June 14, 2016 at 9:42 PM<br>
> To: John McDowall <<a href="mailto:jmcdowall@paloaltonetworks.com">jmcdowall@paloaltonetworks.com</a>><br>
> Cc: Na Zhu <<a href="mailto:nazhu@cn.ibm.com">nazhu@cn.ibm.com</a>>, Srilatha Tangirala <<a href="mailto:srilatta@us.ibm.com">srilatta@us.ibm.com</a><br>
> >, "OpenStack Development Mailing List (not for usage questions)" <<br>
> <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>>, discuss <<a href="mailto:discuss@openvswitch.org">discuss@openvswitch.org</a>><br>
> Subject: Re: [ovs-discuss] [openstack-dev] [OVN] [networking-ovn] <br>
> [networking-sfc] SFC andOVN</tt><br>
<tt>> <br>
> "discuss" <<a href="mailto:discuss-bounces@openvswitch.org">discuss-bounces@openvswitch.org</a>> wrote on 06/14/2016 10:31:40 PM:<br>
> <br>
> > From: John McDowall <<a href="mailto:jmcdowall@paloaltonetworks.com">jmcdowall@paloaltonetworks.com</a>><br>
> > To: Na Zhu <<a href="mailto:nazhu@cn.ibm.com">nazhu@cn.ibm.com</a>><br>
> > Cc: Srilatha Tangirala/San Francisco/IBM@IBMUS, "OpenStack <br>
> > Development Mailing List \(not for usage questions\)" <openstack-<br>
> > <a href="mailto:dev@lists.openstack.org">dev@lists.openstack.org</a>>, discuss <<a href="mailto:discuss@openvswitch.org">discuss@openvswitch.org</a>><br>
> > Date: 06/14/2016 10:48 PM<br>
> > Subject: Re: [ovs-discuss] [openstack-dev] [OVN] [networking-ovn] <br>
> > [networking-sfc] SFC andOVN<br>
> > Sent by: "discuss" <<a href="mailto:discuss-bounces@openvswitch.org">discuss-bounces@openvswitch.org</a>><br>
> > <br>
> > Juno,<br>
> > <br>
> > It is a container for port-pair-groups and flow-classifier. I <br>
> > imagine there could be more the than one port-chain per switch. Also<br>
> > we may want to extend the model beyond a single lswitch <br>
> <br>
> I agree that there could be more than one port-chain per switch, determined<br>
> by the flow classifier. <br>
> <br>
> What I'm confused by is:<br>
> <br>
> 1. Why are items only recorded in logical switches? I would think<br>
> that I could also attach an SFC to a logical router - although I admit<br>
> that the current neutron model for ports doesn't really allow that<br>
> easily. Couple that with the change of name from Logical_Port to<br>
> Logical_Switch_Port, and I'm left wondering if we aren't better off<br>
> with the following "weak" links instead: <br>
> -the Port_Chain includes the logical switch as an external_id<br>
> -each Port_Pair_Group includes the Port_Chain as an external_id<br>
> -each Port_Pair includes the PPG as an external_id<br>
> -each Logical_Switch_Port includes the PP as an external_id<br>
> <br>
> I *think* that *might* allow me (in the future) to attach a port chain<br>
> to a logical router by setting the logical router as an external_id and<br>
> using Logical_Router_Ports to make up the PPs...<br>
> <br>
> JED> If there are “port-chain” tables for switches and routers I <br>
> think I agree. Not sure how this is impacted by the type of VNF (see<br>
> the last email to Juno). I struggle a bit with imagining the flows.</tt><br>
<br>
<tt>RM> Back in the day when we discussed this internally here, SFCs could</tt><br>
<tt>RM> be inserted as BiW (which we do a good job with currently) and at</tt><br>
<tt>RM> network boundaries (which I'm not sure how I could do with the</tt><br>
<tt>RM> current model) - my router question is more one of leaving the</tt><br>
<tt>RM> door open for the boundary case (sorry for the pun) in the future.</tt></p>
</div>
</div>
</span>
<div style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, sans-serif; font-size: 14px;"><font color="#007f00">JED> Lets leave the door open and see what we can do once we have the basic model working?</font></div>
<span id="OLK_SRC_BODY_SECTION">
<div>
<div>
<p><br>
<tt style="font-family: Calibri, sans-serif; font-size: 14px;">> 2. I still don't see what Logical_Flow_Classifier is buying me that<br>
> ACL doesn't - I can codify all of the classifiers given in the match<br>
> criteria of an ACL entry and codify the first PPG of the SFC as<br>
> the action of the ACL entry...</tt><br>
<tt style="font-family: Calibri, sans-serif; font-size: 14px;">> JED> Flow classifiers do map to an ACL entry – just need additional
<br>
> metadata, I.e. Action of the ACL and wether the rules should be uni <br>
> or bi-directional. Though that information could be in the port-chain.</tt><br>
<br>
<tt style="font-family: Calibri, sans-serif; font-size: 14px;">RM> yes and I see the action field of the ACL table being extended</tt><br>
<tt style="font-family: Calibri, sans-serif; font-size: 14px;">RM> to include "enter port chain <blah>" to cover that metadata.</tt><br>
<tt style="font-family: Calibri, sans-serif; font-size: 14px;">RM> Why couldn't bidirectional Flow Classifiers at SFC just be</tt><br>
<tt style="font-family: Calibri, sans-serif; font-size: 14px;">RM> implemented as a pair of uni-directional ACLs in the NB DB?</tt><br>
<tt style="font-family: Calibri, sans-serif; font-size: 14px;">RM> I'll back off on this point if I can see an example of an flow</tt><br>
<tt style="font-family: Calibri, sans-serif; font-size: 14px;">RM> classifier that can't be made to fit in the ACL table, but to</tt><br>
<tt style="font-family: Calibri, sans-serif; font-size: 14px;">RM> date, I've not been able to construct such a beast.</tt><br>
<br>
<font color="#007f00"><font face="Calibri,sans-serif">JED> I would actually go a little further, the requirement on the flow-classifier is that </font></font></p>
</div>
</div>
</span><span id="OLK_SRC_BODY_SECTION">
<div>
<div>
<p><span style="color: rgb(0, 127, 0);">JED> matches are supported by the switch/router. So the matches supported by the switch define the scope</span></p>
</div>
</div>
</span>
<div><font color="#007f00">JED> of the flow-classifier. If I set the action of the ACL (defined by the flow-classifier) to send traffic the first port-pair</font></div>
<div><font color="#007f00">Input port – would that work?</font></div>
<div><font color="#007f00"><br>
</font></div>
<div><font color="#007f00"><br>
</font></div>
</body>
</html>