Re: [ovs-dev] 答复: Re: 答复: Re: 答复: Re: 答复: Re: [PATCH v2] ovn: Support for taas(tap-as-a-service) function
I was wondering the same ... it seems odd to make it both the mirror destination and a regular port at the same time. On Sun, Sep 10, 2017 at 9:13 PM, Gao Zhenyu <sysugaozhe...@gmail.com> wrote: > A application may link to this destination port for collecting/analysing > mirror > traffic. How to distinguish a packet whether it's regular traffic or > mirror traffic if destination port receives both regular traffic and mirror > traffic? > > Thanks > Zhenyu Gao > > 2017-09-09 11:10 GMT+08:00 <wang.qia...@zte.com.cn>: > >> If destination port only receive mirrored traffic, this function do not >> need add port with new type of taas. In this situation, the mirror flag is >> needed. >> >> But, I think, destination port receive both mirrored traffic and regular >> traffic may be more flexible. >> >> Thanks >> >> >> *Takashi YAMAMOTO <yamam...@ovn.org <yamam...@ovn.org>>* >> >> 2017/09/08 20:54 >> >> 收件人：Russell Bryant <russ...@ovn.org>, >> 抄送： wang.qia...@zte.com.cn, ovs dev <d...@openvswitch.org>, >> zhou.huij...@zte.com.cn, xurong00037997 <xu.r...@zte.com.cn> >> 主题：Re: [ovs-dev] 答复: Re: 答复: Re: 答复: Re: [PATCH v2] ovn: >> Support for taas(tap-as-a-service) function >> >> >> >> >> >> On Wed, Sep 6, 2017 at 3:57 AM, Russell Bryant <*russ...@ovn.org* >> <russ...@ovn.org>> wrote: >> What if a mirror port *only* receives mirrored packets? If the only >> packets it ever receives are mirrored packets, a new flag would not be >> necessary. >> >> Do you intend for the port to operate as both a regular port *and* to >> receive a mirror of traffic for another port? >> >> in taas, a destination port is supposed to receive both of mirrored >> traffic and regular traffic. >> >> (i haven't looked at this implementation yet) >> >> >> On Thu, Aug 24, 2017 at 10:31 PM, <*wang.qia...@zte.com.cn* >> <wang.qia...@zte.com.cn>> wrote: >> >> > I know your mean. >> > The receiver need to distinguish the traffic is regular or mirror. This >> > may need some special flow table to deal with it. >> > >> > Thanks >> > >> > >> > >> > *Gao Zhenyu <*sysugaozhe...@gmail.com* <sysugaozhe...@gmail.com> < >> *sysugaozhe...@gmail.com* <sysugaozhe...@gmail.com>>>* >> > >> > 2017/08/25 10:12 >> > >> > 收件人：*wang.qia...@zte.com.cn* <wang.qia...@zte.com.cn>, >> > 抄送：ovs dev <*d...@openvswitch.org* <d...@openvswitch.org>>, >> Russell Bryant < >> > *russ...@ovn.org* <russ...@ovn.org>>, xurong00037997 < >> *xu.r...@zte.com.cn* <xu.r...@zte.com.cn>>, >> > *zhou.huij...@zte.com.cn* <zhou.huij...@zte.com.cn> >> > 主题：Re: 答复: Re: [ovs-dev] 答复: Re: [PATCH v2] ovn: Support >> > for taas(tap-as-a-service) function >> > >> > >> > I mean for regular packet, ovs should not add the geneve option, the >> new >> > geneve option is only for mirror traffic. >> > >> > Did you meant some mirror traffic has mirror flag and some would not >> have? >> > >> > Thanks >> > Zhenyu Gao >> > >> > 2017-08-25 9:44 GMT+08:00 <**wang.qia...@zte.com.cn* >> <wang.qia...@zte.com.cn>* >> > <*wang.qia...@zte.com.cn* <wang.qia...@zte.com.cn>>>: >> > Hi zhenyu, >> > Thanks for your opinion. >> > The mirror flag is not always exist, so I do not think add a new geneve >> > option is a good idea. >> > >> > Thanks. >> > >> > >> > *Gao Zhenyu <***sysugaozhe...@gmail.com* <sysugaozhe...@gmail.com>* < >> *sysugaozhe...@gmail.com* <sysugaozhe...@gmail.com>>*>* >> > >> > 2017/08/25 09:34 >> > >> > 收件人：**wang.qia...@zte.com.cn* <wang.qia...@zte.com.cn>* >> <*wang.qia...@zte.com.cn* <wang.qia...@zte.com.cn>>, >> > 抄送：Russell Bryant <**russ...@ovn.org* <russ...@ovn.org>* >> <*russ...@ovn.org* <russ...@ovn.org>>>, >> > ovs dev <**d...@openvswitch.org* <d...@openvswitch.org>* < >> *d...@openvswitch.org* <d...@openvswitch.org>>>, >> > **zhou.huij...@zte.com.cn* <zhou.huij...@zte.com.cn>* < >> *zhou.huij...@zte.com.cn* <zhou.huij...@zte.com.cn>>, xurong0003799
Re: [ovs-dev] 答复: Re: 答复: Re: 答复: Re: 答复: Re: [PATCH v2] ovn: Support for taas(tap-as-a-service) function
A application may link to this destination port for collecting/analysing mirror traffic. How to distinguish a packet whether it's regular traffic or mirror traffic if destination port receives both regular traffic and mirror traffic? Thanks Zhenyu Gao 2017-09-09 11:10 GMT+08:00 <wang.qia...@zte.com.cn>: > If destination port only receive mirrored traffic, this function do not > need add port with new type of taas. In this situation, the mirror flag is > needed. > > But, I think, destination port receive both mirrored traffic and regular > traffic may be more flexible. > > Thanks > > > *Takashi YAMAMOTO <yamam...@ovn.org <yamam...@ovn.org>>* > > 2017/09/08 20:54 > > 收件人：Russell Bryant <russ...@ovn.org>, > 抄送：wang.qia...@zte.com.cn, ovs dev <d...@openvswitch.org>, > zhou.huij...@zte.com.cn, xurong00037997 <xu.r...@zte.com.cn> > 主题： Re: [ovs-dev] 答复: Re: 答复: Re: 答复: Re: [PATCH v2] ovn: > Support for taas(tap-as-a-service) function > > > > > > On Wed, Sep 6, 2017 at 3:57 AM, Russell Bryant <*russ...@ovn.org* > <russ...@ovn.org>> wrote: > What if a mirror port *only* receives mirrored packets? If the only > packets it ever receives are mirrored packets, a new flag would not be > necessary. > > Do you intend for the port to operate as both a regular port *and* to > receive a mirror of traffic for another port? > > in taas, a destination port is supposed to receive both of mirrored > traffic and regular traffic. > > (i haven't looked at this implementation yet) > > > On Thu, Aug 24, 2017 at 10:31 PM, <*wang.qia...@zte.com.cn* > <wang.qia...@zte.com.cn>> wrote: > > > I know your mean. > > The receiver need to distinguish the traffic is regular or mirror. This > > may need some special flow table to deal with it. > > > > Thanks > > > > > > > > *Gao Zhenyu <*sysugaozhe...@gmail.com* <sysugaozhe...@gmail.com> < > *sysugaozhe...@gmail.com* <sysugaozhe...@gmail.com>>>* > > > > 2017/08/25 10:12 > > > > 收件人：*wang.qia...@zte.com.cn* <wang.qia...@zte.com.cn>, > > 抄送： ovs dev <*d...@openvswitch.org* <d...@openvswitch.org>>, > Russell Bryant < > > *russ...@ovn.org* <russ...@ovn.org>>, xurong00037997 < > *xu.r...@zte.com.cn* <xu.r...@zte.com.cn>>, > > *zhou.huij...@zte.com.cn* <zhou.huij...@zte.com.cn> > > 主题：Re: 答复: Re: [ovs-dev] 答复: Re: [PATCH v2] ovn: Support > > for taas(tap-as-a-service) function > > > > > > I mean for regular packet, ovs should not add the geneve option, the new > > geneve option is only for mirror traffic. > > > > Did you meant some mirror traffic has mirror flag and some would not > have? > > > > Thanks > > Zhenyu Gao > > > > 2017-08-25 9:44 GMT+08:00 <**wang.qia...@zte.com.cn* > <wang.qia...@zte.com.cn>* > > <*wang.qia...@zte.com.cn* <wang.qia...@zte.com.cn>>>: > > Hi zhenyu, > > Thanks for your opinion. > > The mirror flag is not always exist, so I do not think add a new geneve > > option is a good idea. > > > > Thanks. > > > > > > *Gao Zhenyu <***sysugaozhe...@gmail.com* <sysugaozhe...@gmail.com>* < > *sysugaozhe...@gmail.com* <sysugaozhe...@gmail.com>>*>* > > > > 2017/08/25 09:34 > > > > 收件人：**wang.qia...@zte.com.cn* <wang.qia...@zte.com.cn>* > <*wang.qia...@zte.com.cn* <wang.qia...@zte.com.cn>>, > > 抄送：Russell Bryant <**russ...@ovn.org* <russ...@ovn.org>* > <*russ...@ovn.org* <russ...@ovn.org>>>, > > ovs dev <**d...@openvswitch.org* <d...@openvswitch.org>* < > *d...@openvswitch.org* <d...@openvswitch.org>>>, > > **zhou.huij...@zte.com.cn* <zhou.huij...@zte.com.cn>* < > *zhou.huij...@zte.com.cn* <zhou.huij...@zte.com.cn>>, xurong00037997 < > > **xu.r...@zte.com.cn* <xu.r...@zte.com.cn>* <*xu.r...@zte.com.cn* > <xu.r...@zte.com.cn>>> > > 主题：Re: [ovs-dev] 答复: Re: [PATCH v2] ovn: Support for > > taas(tap-as-a-service) function > > > > > > > > Although adding a new geneve option is more complicate but I think it > > still worth having that. > > Once the destination chassis found that geneve option, it can tag the > > mirror flag on packet. And it make the whole process looks same no matter > > on same chassis or not. > > > > Thanks > > Zhenyu Gao > > >
[ovs-dev] 答复: Re: 答复: Re: 答复: Re: 答复: Re: [PATCH v2] ovn: Support for taas(tap-as-a-service) function
If destination port only receive mirrored traffic, this function do not
need add port with new type of taas. In this situation, the mirror flag is
needed.
But, I think, destination port receive both mirrored traffic and regular
traffic may be more flexible.
Thanks
Takashi YAMAMOTO <yamam...@ovn.org>
2017/09/08 20:54
收件人：Russell Bryant <russ...@ovn.org>,
抄送： wang.qia...@zte.com.cn, ovs dev <d...@openvswitch.org>,
zhou.huij...@zte.com.cn, xurong00037997 <xu.r...@zte.com.cn>
主题： Re: [ovs-dev] 答复: Re: 答复: Re: 答复: Re: [PATCH v2]
ovn: Support for taas(tap-as-a-service) function
On Wed, Sep 6, 2017 at 3:57 AM, Russell Bryant <russ...@ovn.org> wrote:
What if a mirror port *only* receives mirrored packets? If the only
packets it ever receives are mirrored packets, a new flag would not be
necessary.
Do you intend for the port to operate as both a regular port *and* to
receive a mirror of traffic for another port?
in taas, a destination port is supposed to receive both of mirrored
traffic and regular traffic.
(i haven't looked at this implementation yet)
On Thu, Aug 24, 2017 at 10:31 PM, <wang.qia...@zte.com.cn> wrote:
> I know your mean.
> The receiver need to distinguish the traffic is regular or mirror. This
> may need some special flow table to deal with it.
>
> Thanks
>
>
>
> *Gao Zhenyu <sysugaozhe...@gmail.com <sysugaozhe...@gmail.com>>*
>
> 2017/08/25 10:12
>
> 收件人：wang.qia...@zte.com.cn,
> 抄送：ovs dev <d...@openvswitch.org>, Russell Bryant <
> russ...@ovn.org>, xurong00037997 <xu.r...@zte.com.cn>,
> zhou.huij...@zte.com.cn
> 主题：Re: 答复: Re: [ovs-dev] 答复: Re: [PATCH v2] ovn:
Support
> for taas(tap-as-a-service) function
>
>
> I mean for regular packet, ovs should not add the geneve option, the
new
> geneve option is only for mirror traffic.
>
> Did you meant some mirror traffic has mirror flag and some would not
have?
>
> Thanks
> Zhenyu Gao
>
> 2017-08-25 9:44 GMT+08:00 <*wang.qia...@zte.com.cn*
> <wang.qia...@zte.com.cn>>:
> Hi zhenyu,
> Thanks for your opinion.
> The mirror flag is not always exist, so I do not think add a new geneve
> option is a good idea.
>
> Thanks.
>
>
> *Gao Zhenyu <**sysugaozhe...@gmail.com* <sysugaozhe...@gmail.com>*>*
>
> 2017/08/25 09:34
>
> 收件人：*wang.qia...@zte.com.cn* <wang.qia...@zte.com.cn
>,
> 抄送：Russell Bryant <*russ...@ovn.org* <russ...@ovn.org
>>,
> ovs dev <*d...@openvswitch.org* <d...@openvswitch.org>>,
> *zhou.huij...@zte.com.cn* <zhou.huij...@zte.com.cn>, xurong00037997 <
> *xu.r...@zte.com.cn* <xu.r...@zte.com.cn>>
> 主题：Re: [ovs-dev] 答复: Re: [PATCH v2] ovn: Support
for
> taas(tap-as-a-service) function
>
>
>
> Although adding a new geneve option is more complicate but I think it
> still worth having that.
> Once the destination chassis found that geneve option, it can tag the
> mirror flag on packet. And it make the whole process looks same no
matter
> on same chassis or not.
>
> Thanks
> Zhenyu Gao
>
> 2017-08-25 9:15 GMT+08:00 <*wang.qia...@zte.com.cn*
> <wang.qia...@zte.com.cn>>:
> Hi Russell,
>
> Thanks for your review.
>
> When the mirror destination is in other chassis, the mirror flag which
> used to mark the packet need be transmitted to the destination chassis.
>
> We could use the inport, geneve option or new type of out port to
indicate
> the packet as a mirrored packet.
>
> When we use inport to indicate the flag, this may need use inport as the
> match field in the egress pipeline, I think this may conflict with the
> egress pipeline.
>
> If use geneve option to deliver the mirror flag, this may be more
> complicated. So, I add a new type of port as the destination of mirror
> flow. The port types of mirror and taas corresponding to configurations
of
> tap-flow and tap-service.
>
> Thanks.
>
>
>
>
>
> Russell Bryant <*russ...@ovn.org* <russ...@ovn.org>>
> 2017/08/25 04:44
>
> 收件人：*wang.qia...@zte.com.cn* <wang.qia...@zte.com.cn
>,
> 抄送： ovs dev <*d...@openvswitch.org* <d...@openvswitch.org>>,
> *zhou.huij...@zte.com.cn* <zhou.huij...@zte.com.cn>,
> xurong00037997 <*xu.r...@zte.com.cn* <xu.r...@zte.com.cn>>
> 主题： Re: [ovs-dev] [PATCH v2] ovn: Support for
> taas(tap-as-a-service) function
>
>
> Sorry for the delay in getting back to this ...
>
> On Tue, Aug 15, 2017 at 4:28 AM, <*wang.qia...@zte.com.cn*
> <wang.qia...@zte.com.cn>> wrote:
> > Ta
[ovs-dev] 答复: Re: 答复: Re: 答复: Re: 答复: Re: [PATCH v2] ovn: Support for taas(tap-as-a-service) function
Mirror port only receives mirrored packets. I would remove the flag, and
uses inport and outport to mark the mirrored packets.
Thanks.
Russell Bryant <russ...@ovn.org>
2017/09/06 02:57
收件人：wang.qia...@zte.com.cn,
抄送： Gao Zhenyu <sysugaozhe...@gmail.com>, ovs dev
<d...@openvswitch.org>, xurong00037997 <xu.r...@zte.com.cn>,
zhou.huij...@zte.com.cn
主题： Re: 答复: Re: 答复: Re: [ovs-dev] 答复: Re: [PATCH v2]
ovn: Support for taas(tap-as-a-service) function
What if a mirror port *only* receives mirrored packets? If the only
packets it ever receives are mirrored packets, a new flag would not be
necessary.
Do you intend for the port to operate as both a regular port *and* to
receive a mirror of traffic for another port?
On Thu, Aug 24, 2017 at 10:31 PM, <wang.qia...@zte.com.cn> wrote:
I know your mean.
The receiver need to distinguish the traffic is regular or mirror. This
may need some special flow table to deal with it.
Thanks
Gao Zhenyu <sysugaozhe...@gmail.com>
2017/08/25 10:12
收件人：wang.qia...@zte.com.cn,
抄送：ovs dev <d...@openvswitch.org>, Russell Bryant <
russ...@ovn.org>, xurong00037997 <xu.r...@zte.com.cn>,
zhou.huij...@zte.com.cn
主题： Re: 答复: Re: [ovs-dev] 答复: Re: [PATCH v2] ovn:
Support for taas(tap-as-a-service) function
I mean for regular packet, ovs should not add the geneve option, the new
geneve option is only for mirror traffic.
Did you meant some mirror traffic has mirror flag and some would not have?
Thanks
Zhenyu Gao
2017-08-25 9:44 GMT+08:00 <wang.qia...@zte.com.cn>:
Hi zhenyu,
Thanks for your opinion.
The mirror flag is not always exist, so I do not think add a new geneve
option is a good idea.
Thanks.
Gao Zhenyu <sysugaozhe...@gmail.com>
2017/08/25 09:34
收件人：wang.qia...@zte.com.cn,
抄送：Russell Bryant <russ...@ovn.org>, ovs dev <
d...@openvswitch.org>, zhou.huij...@zte.com.cn, xurong00037997 <
xu.r...@zte.com.cn>
主题： Re: [ovs-dev] 答复: Re: [PATCH v2] ovn: Support for
taas(tap-as-a-service) function
Although adding a new geneve option is more complicate but I think it
still worth having that.
Once the destination chassis found that geneve option, it can tag the
mirror flag on packet. And it make the whole process looks same no matter
on same chassis or not.
Thanks
Zhenyu Gao
2017-08-25 9:15 GMT+08:00 <wang.qia...@zte.com.cn>:
Hi Russell,
Thanks for your review.
When the mirror destination is in other chassis, the mirror flag which
used to mark the packet need be transmitted to the destination chassis.
We could use the inport, geneve option or new type of out port to indicate
the packet as a mirrored packet.
When we use inport to indicate the flag, this may need use inport as the
match field in the egress pipeline, I think this may conflict with the
egress pipeline.
If use geneve option to deliver the mirror flag, this may be more
complicated. So, I add a new type of port as the destination of mirror
flow. The port types of mirror and taas corresponding to configurations of
tap-flow and tap-service.
Thanks.
Russell Bryant <russ...@ovn.org>
2017/08/25 04:44
收件人：wang.qia...@zte.com.cn,
抄送： ovs dev <d...@openvswitch.org>, zhou.huij...@zte.com.cn,
xurong00037997 <xu.r...@zte.com.cn>
主题： Re: [ovs-dev] [PATCH v2] ovn: Support for
taas(tap-as-a-service) function
Sorry for the delay in getting back to this ...
On Tue, Aug 15, 2017 at 4:28 AM, <wang.qia...@zte.com.cn> 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 <wang.qia...@zte.com.cn>
> 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 @@
>
> A port to a logical switch on a VTEP gateway.
>
