Re: [ovs-discuss] About the 'clone' action

[Ben Pfaff]

On Wed, Oct 25, 2017 at 06:07:41PM +0800, Hui Xiang wrote:
> I think I am finally catching a bit with the concept of 'clone' action
> after reviewing below patches in order, so the for OVN case, the new
> 'clone' action aims to drop most of the OVS patch port, and after add new
> ct_clear action, some fixes, I assume it works with NAT, and I am using
> 2.8.1 for testing, please point out the patches if I am missing any. 

I think that should work fine.  There are a few bug fixes on branch-2.8
that are not in any v2.8.x release, but I don't think that they will
affect OVN.

> One other question is Can I set bridge-mapping:physnet1:br-int? In
> other words, the br-int has vm vif, has tunnel ports(the tunnel ports
> would point to another nic), and has the external nic as local gateway
> router port, is it feasible without configuring more extra flows.

I don't think OVN contemplates br-int being using as a bridge mapping.
My guess is that that would fail.
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] About the 'clone' action

[Hui Xiang]

Thanks Ben for your info.

I think I am finally catching a bit with the concept of 'clone' action
after reviewing below patches in order, so the for OVN case, the new
'clone' action aims to drop most of the OVS patch port, and after add new
ct_clear action, some fixes, I assume it works with NAT, and I am using
2.8.1 for testing, please point out the patches if I am missing any. One
other question is Can I set bridge-mapping:physnet1:br-int? In other words,
the br-int has vm vif, has tunnel ports(the tunnel ports would point to
another nic), and has the external nic as local gateway router port, is it
feasible without configuring more extra flows.


[ovs-dev] [RFC PATCH] ofp-actions: Add clone action.
https://mail.openvswitch.org/pipermail/ovs-dev/2016-November/325542.html

ovn-controller: Drop most uses of OVS patch ports.
https://github.com/openvswitch/ovs/commit/f1a8bd06d58f2c5312622fbaeacbc6ce7576e347https://github.com/openvswitch/ovs/commit/f1a8bd06d58f2c5312622fbaeacbc6ce7576e347

[ovs-dev] [PATCH 2/3] dpif-netdev: Add clone action
https://mail.openvswitch.org/pipermail/ovs-dev/2017-January/327633.html

[ovs-dev] Issues with the use of the clone action for resubmission to the
pipeline
https://mail.openvswitch.org/pipermail/ovs-dev/2017-January/326981.html

[ovs-dev] ovn ping from VM to external gateway IP failed.
https://mail.openvswitch.org/pipermail/ovs-dev/2016-December/326936.html

[ovs-dev] [PATCH v2 0/4] Fix some "clone"-related issues
https://mail.openvswitch.org/pipermail/ovs-dev/2017-January/327251.html

[ovs-dev] [PATCH v2 3/4] New action "ct_clear".
https://mail.openvswitch.org/pipermail/ovs-dev/2017-January/327268.html

[ovs-dev] [PATCH v2 4/4] ovn-controller: Clear conntrack state inside clone
action.
https://mail.openvswitch.org/pipermail/ovs-dev/2017-January/327255.html

On Tue, Oct 24, 2017 at 12:21 AM, Ben Pfaff  wrote:

> On Mon, Oct 23, 2017 at 04:28:53PM +0800, Hui Xiang wrote:
> > I am trying to understand clone action deeply and checking the patch
> > related with 'clone'[1], where said "The clone action provides an action
> > envelope to enclose an action list." and "The clone action is very
> similar
> > with the OpenFlow clone action recently added", but sorry I am not able
> to
> > find any "clone" action definition in the OpenFlow spec[2], or any
> envelope
> > 's kind of phrases, it just referred some clone(copy) of piple, am I
> > looking in a wrong place?
>
> Open vSwitch has two kinds of actions.  First, there are OpenFlow
> actions, which include both standard actions and extension actions.
> "clone" is an OpenFlow extension action implemented by Open vSwitch.
> Second, there are datapath actions, which are an implementation detail
> of Open vSwitch.  Open vSwitch has a datapath action also called
> "clone", which does something similar to the OpenFlow extension "clone"
> action but at the datapath level.
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] About the 'clone' action

[Ben Pfaff]

On Mon, Oct 23, 2017 at 04:28:53PM +0800, Hui Xiang wrote:
> I am trying to understand clone action deeply and checking the patch
> related with 'clone'[1], where said "The clone action provides an action
> envelope to enclose an action list." and "The clone action is very similar
> with the OpenFlow clone action recently added", but sorry I am not able to
> find any "clone" action definition in the OpenFlow spec[2], or any envelope
> 's kind of phrases, it just referred some clone(copy) of piple, am I
> looking in a wrong place?

Open vSwitch has two kinds of actions.  First, there are OpenFlow
actions, which include both standard actions and extension actions.
"clone" is an OpenFlow extension action implemented by Open vSwitch.
Second, there are datapath actions, which are an implementation detail
of Open vSwitch.  Open vSwitch has a datapath action also called
"clone", which does something similar to the OpenFlow extension "clone"
action but at the datapath level.
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss