Sorry for the delay in getting back to this ... On Tue, Aug 15, 2017 at 4:28 AM, <[email protected]> wrote: > Taas was designed to provide tenants and service providers a means of > monitoring the traffic flowing in their Neutron provisioned virtual > networks. It is useful for network trouble-shooting, security and > analytics. The taas presentations could be found from > https://github.com/openstack/tap-as-a-service/blob/master/doc/source/presentations.rst > , and the api reference could be found from > https://github.com/openstack/tap-as-a-service/blob/master/API_REFERENCE.rst > > To support taas function, this patch add two type of logica_switch_port, > "mirror" and "taas". port with type "mirror" is used as inport for monitor > flow in logica_switch, and port with type "taas" is used as outport for > monitor flow in logica_switch. > > The ovn-controller will make the relations of the ports in tap_service and > tap_flow to mirror port and taas port. > > Signed-off-by: wang qianyu <[email protected]>
> diff --git a/ovn/ovn-nb.xml b/ovn/ovn-nb.xml > index 31303a8..5fdd045 100644 > --- a/ovn/ovn-nb.xml > +++ b/ovn/ovn-nb.xml > @@ -301,6 +301,20 @@ > <dd> > A port to a logical switch on a VTEP gateway. > </dd> > + > + <dt><code>mirror</code></dt> > + <dd> > + A port indicate the inport of mirrored flows. The user need > to > + create this port in the logical_switch. This port should one > to > + one correspondence with the the tap_flows > + </dd> > + > + <dt><code>taas</code></dt> > + <dd> > + A port indicate the outport of mirrored flows. The user need > to > + create this port in logical_switch. This port should one to > + one correspondence with the the tap_service. > + </dd> > </dl> > </column> > </group> > @@ -445,6 +459,61 @@ > interface, in bits. > </column> > </group> > + > + <group title="Options for mirror ports"> > + <p> > + These options apply when <ref column="type"/> is > + <code>mirror</code>. > + </p> > + > + <column name="options" key="source-port"> > + Required. The <ref column="name"/> of the <ref > + table="Logical_switch_Port"/> that indicates where the > + cloned flows come from. > + </column> > + > + <column name="options" key="taas-port"> > + Required. The <ref column="name"/> of the <ref > + table="Logical_switch_Port"/> with type taas. > + </column> > + > + <column name="options" key="direction"> > + <p> > + This option indicates whitch direction(from-port/to-port/all) > of > + packet will be cloned to the taas-port. The directions are > defined > + as follow: > + </p> > + <dl> > + <dt><code>from-port</code></dt> > + <dd> > + The packets from this port will be cloned to specified > mirror > + port. > + </dd> > + <dt><code>to-port</code></dt> > + <dd> > + The packets to this port will be cloned to specified mirror > + port. > + </dd> > + <dt><code>both</code></dt> > + <dd> > + The packets both from and to this port will be cloned to > + specified mirror port. > + </dd> > + </dl> > + </column> > + </group> > + > + <group title="Options for taas ports"> > + <p> > + These options apply when <ref column="type"/> is > <code>taas</code>. > + </p> > + > + <column name="options" key="target-port"> > + Required. The <ref column="name"/> of the <ref > + table="Logical_switch_Port"/> that indicates where the > + cloned flows come to. > + </column> > + </group> > </group> > > <group title="Containers"> I'm having a hard time understanding this schema. Could you expand on why both a "mirror" and "taas" port type was needed? I was hoping for only a single new port type, "mirror" for example, with options to specify what port it is receiving a mirror of traffic for. Does something like that not express everything needed here? -- Russell Bryant _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
