<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;">
<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);">
In-line</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">
<div style="font-family: Calibri; font-size: 11pt; color: black; text-align: left; border-width: 1pt medium medium; border-style: solid none none; padding: 3pt 0in 0in; border-top-color: rgb(181, 196, 223);">
<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>Tuesday, June 14, 2016 at 9:42 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>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>>, "OpenStack Development Mailing List (not for usage questions)" <<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>
<span style="font-weight:bold">Subject: </span>Re: [ovs-discuss] [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC andOVN<br>
</div>
<div style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">
<br>
</div>
<div>
<div>
<p><tt style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">"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>></tt><br>
<tt style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">> To: Na Zhu <<a href="mailto:nazhu@cn.ibm.com">nazhu@cn.ibm.com</a>></tt><br>
<tt style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">> 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>></tt><br>
<tt style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">> Date: 06/14/2016 10:48 PM</tt><br>
<tt style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">> Subject: Re: [ovs-discuss] [openstack-dev] [OVN] [networking-ovn]
<br>
> [networking-sfc] SFC andOVN</tt><br>
<tt style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">> Sent by: "discuss" <<a href="mailto:discuss-bounces@openvswitch.org">discuss-bounces@openvswitch.org</a>></tt><br>
<tt style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">>
<br>
> Juno,</tt><br>
<tt style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">>
<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 </tt><br>
<br>
<tt style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">I agree that there could be more than one port-chain per switch, determined</tt><br>
<tt style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">by the flow classifier. </tt><br>
<br>
<tt style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">What I'm confused by is:</tt><br>
<br>
<tt style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">1. Why are items only recorded in logical switches? I would think</tt><br>
<tt style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">that I could also attach an SFC to a logical router - although I admit</tt><br>
<tt style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">that the current neutron model for ports doesn't really allow that</tt><br>
<tt style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">easily. Couple that with the change of name from Logical_Port to</tt><br>
<tt style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">Logical_Switch_Port, and I'm left wondering if we aren't better off</tt><br>
<tt style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">with the following "weak" links instead:
</tt><br>
<tt style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">-the Port_Chain includes the logical switch as an external_id</tt><br>
<tt style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">-each Port_Pair_Group includes the Port_Chain as an external_id</tt><br>
<tt style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">-each Port_Pair includes the PPG as an external_id</tt><br>
<tt style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">-each Logical_Switch_Port includes the PP as an external_id</tt><br>
<br>
<tt style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">I *think* that *might* allow me (in the future) to attach a port chain</tt><br>
<tt style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">to a logical router by setting the logical router as an external_id and</tt><br>
<tt style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">using Logical_Router_Ports to make up the PPs...</tt><br>
<br>
<font color="#007f00"><font face="Calibri,sans-serif">JED> If there are “port-chain” tables for switches and routers I think I agree. Not sure how this is impacted by the type of VNF (see the last email to Juno). I struggle a bit with imagining the flows.</font></font></p>
</div>
</div>
</span><span id="OLK_SRC_BODY_SECTION" style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">
<div>
<div>
<p><tt>2. I still don't see what Logical_Flow_Classifier is buying me that</tt><br>
<tt>ACL doesn't - I can codify all of the classifiers given in the match</tt><br>
<tt>criteria of an ACL entry and codify the first PPG of the SFC as</tt><br>
<tt>the action of the ACL entry...</tt><br>
</p>
</div>
</div>
</span>
<div><font color="#007f00">JED> Flow classifiers do map to an ACL entry – just need additional metadata, I.e. Action of the ACL and wether the rules should be uni or bi-directional. Though that information could be in the port-chain.</font></div>
<span id="OLK_SRC_BODY_SECTION" style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">
<div>
<div>
<p><tt>Ryan</tt><br>
</p>
</div>
</div>
</span>
</body>
</html>