On 3 March 2016 at 05:40, Russell Bryant <russ...@ovn.org> wrote: > On Wed, Mar 2, 2016 at 8:31 PM, Han Zhou <zhou...@gmail.com> wrote: > >> >> >> On Wed, Mar 2, 2016 at 1:43 PM, Russell Bryant <russ...@ovn.org> wrote: >> > >> > Update the "ct_commit;" logical flow action to optionally take a >> > parameter, setting the value of "ct_mark" to a 32-bit integer. >> > Supported ct_commit syntax now includes: >> > >> > ct_commit; >> > ct_commit(); >> > ct_commit(ct_mark=1); >> > >> > Setting ct_mark via this type of logical flow results in an OpenFlow >> > flow that looks like: >> > >> > >> actions=ct(commit,zone=NXM_NX_REG5[0..15],exec(set_field:0x1->ct_mark)) >> >> Russell, I have a question regarding this syntax. Is "commit" required for >> setting the mark/label for an existed item in conntrack table >> > > Yes, the documentation at least specifies that it is required. The > ovs-ofctl man page says "The commit parameter should be specified to use > exec(...)."
I think I may have loosened the wording on this in the documentation recently, but the OpenFlow ct action parsing enforces this strictly. There's some potential to loosen this restriction in future if necessary (though, if the connection isn't committed at some point then obviously the mark/label won't be stored.) _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
