[ovs-dev] [PATCH 2/4] Update OVN SB documentation to use physical endpoints table and mention possible deprecation of vtep logical port options which would require other changes for HW VTEP side and cleanup of OVN NB schema

Darrell Ball dlu998 at gmail.com
Tue Mar 1 18:39:17 UTC 2016


Signed-off-by: Darrell Ball <dball at vmware.com>
---
 ovn/ovn-sb.xml | 54 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 54 insertions(+)

diff --git a/ovn/ovn-sb.xml b/ovn/ovn-sb.xml
index 1ea35d5..689d1c8 100644
--- a/ovn/ovn-sb.xml
+++ b/ovn/ovn-sb.xml
@@ -1114,6 +1114,49 @@ tcp.flags = RST;
     </group>
   </table>
 
+  <table name="Physical_Endpoint" title="Endpoints on physical access nets ">
+    <p>
+      Each row in this table identifies an endpoint on a physical access
+      network.  The <ref table="Port_Binding"/> table references physical
+      endpoints for localnet and gateways. A physical endpoint comprises
+      both a location on a chassis port and encapsulation for access.
+      A given chassis port location can have several encapsulations
+      and there physical endpoints.
+    </p>
+
+    <column name="name">
+      Unique name to reference the physical endpoint.
+    </column>
+
+    <column name="chassis">
+      The transport node the physical endpoint resides on.
+    </column>
+
+    <column name="chassis_port">
+      The port on the transport node the physical endpoint resides on.
+      Context is the associated transport node.
+    </column>
+
+    <column name="type">
+      The encapsulation type of the physical endpoint. Types include
+      single vlan for now, but later support for mpls label stack,
+      IP tunnel outer header and dual vlan. Note that encapsulations
+      are often directionally different, meaning the encapsulation
+      expected on ingress is different from the encapsulation
+      for egressing packets; mpls labels and IP tunnels being
+      two examples.
+    </column>
+
+    <column name="ingress_encap">
+      The ingress encapsulation type of the physical endpoint.
+    </column>
+
+    <column name="egress_encap">
+      The egress encapsulation type of the physical endpoint.
+    </column>
+
+  </table>
+
   <table name="Port_Binding" title="Physical-Logical Port Bindings">
     <p>
       Most rows in this table identify the physical location of a logical port.
@@ -1168,6 +1211,13 @@ tcp.flags = RST;
         <code>ovn-controller</code>/<code>ovn-controller-vtep</code>.
       </column>
 
+      <column name="phys_endpt">
+        The physical endpoint that the logical port resides on.
+        To successfully identify a phys_endpt, this column must be a
+        <ref table="Physical_Endpoint"/> record.  This is populated by a
+        <code>CMS</code> physical management component.
+      </column>
+
       <column name="tunnel_key">
         <p>
           A number that represents the logical port in the key (e.g. STT key or
@@ -1278,6 +1328,7 @@ tcp.flags = RST;
       </column>
 
       <column name="tag">
+        This column will be deprecated.
         If set, indicates that the port represents a connection to a specific
         VLAN on a locally accessible network. The VLAN ID is used to match
         incoming traffic and is also added to outgoing traffic.
@@ -1286,15 +1337,18 @@ tcp.flags = RST;
 
     <group title="VTEP Options">
       <p>
+        Will be deprecated.
         These options apply to logical ports with <ref column="type"/> of
         <code>vtep</code>.
       </p>
 
       <column name="options" key="vtep-physical-switch">
+        This column "may" be deprecated.
         Required. The name of the VTEP gateway.
       </column>
 
       <column name="options" key="vtep-logical-switch">
+        This column "may" be deprecated.
         Required.  A logical switch name connected by the VTEP gateway.  Must
         be set when <ref column="type"/> is <code>vtep</code>.
       </column>
-- 
1.9.1




More information about the dev mailing list