Thanks for the clear explanation! From: Ilya Maximets <i.maxim...@ovn.org> Date: Monday, July 10, 2023 at 5:05 AM To: Ashish Varma <ava...@vmware.com>, ovs-discuss@openvswitch.org <ovs-discuss@openvswitch.org> Cc: i.maxim...@ovn.org <i.maxim...@ovn.org> Subject: Re: [ovs-discuss] NXAST_CONTROLLER vs NXAST_CONTROLLER2 !! External Email
On 7/10/23 02:16, Ashish Varma via discuss wrote: > Hello, > > From ovs-actions man pages, the controller action is defined as: > > *The controller action* > *Syntax*: > *controller* > *controller:*/max_len/ > *controller(*/key/*[=*/value/*], ...)* > > There is no ‘controller2’ action. So, when programming a flow, can we ask OVS > to use a specific NXAST_CONTROLLER or NXAST_CONTROLLER2 action? Or it depends > on the options provided in the action? It depend on the provided options. If you're using 'userdata' or 'pause', the NXAST_CONTROLLER2 will be used. If only 'reason' and 'controller_id', then NXAST_CONTROLLER will be used. In the most basic case with 'max_len' only, it will use OUTPUT action with OFPP_CONTROLLER as a port. That's how ovs-ofctl utility translates the text form of the action into OpenFlow. If you're writing your own controller, you should be able to create a raw OpenFlow request with any action you want. Best regards, Ilya Maximets. !! External Email: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender.
_______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
