On Tue, Dec 15, 2015 at 05:58:14PM +0000, Frances, Margaret wrote: > 2. OpenFlow¹s Goto instruction directs a frame from one table to the next. > A redirection in this sense must be to a higher-numbered table, which is > to say that OF pipeline processing can only go forward (see p.18, para.2 > of the 1.4.1 spec > <https://www.opennetworking.org/images/stories/downloads/sdn-resources/onf- > specifications/openflow/openflow-switch-v1.4.1.pdf>). However, OvS (at > least v2.0.2) implements a resubmit action, which re-searches another > table‹higher-, lower-, or even same-numbered‹and executes any actions > found there in addition to any subsequent actions in the current flow > entry. It is by using resubmit that the proposed design could work, as > shown in the ovs-ofctl command posted here > <https://review.openstack.org/#/c/251738/1/neutron/agent/common/ovs_lib.py> > . (Maybe there are other ways, too.) The resubmit action is a Nicira > vendor extension that at least at one point, and maybe still, was known to > be implemented only by OvS. I mention this because I wonder if the > proposed design (and my sample command) calls for flow traversal in a > manner not explicitly supported by OpenFlow and so may not work in future > versions of OvS.
OVS has has "resubmit" for a long time and it's heavily used by lots of projects. It's not going to go away. __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev