On 11/11/2015 06:44 AM, Ben Pfaff wrote:
On Fri, Oct 23, 2015 at 02:11:08PM +0530, Numan Siddique wrote:
A new table is created for controller flows. A logical flow is created
for every datapath, to submit the packets matching DHCP pattern to
the controller table.
An entry is created in the controller table by the ovn-controller to do a
packet-in on every port's MAC address that matches it's chasis id.
Signed-off-by: Numan Siddique <nusid...@redhat.com>
I'm not sure I fully understand the intent here. The concept I've been
using for OVN logical flows (which I now understand I haven't
articulated), is that whether the controller is involved in processing
should be hidden from the logical flow table. That is, instead of
"controller" as the action, the action would be whatever should actually
be done to the packet. Then ovn-controller can implement that through
the flow table, or by sending the packet to the controller, or some
other appropriate way.
Thanks Ben for the reviews.
My intention was
- if the action is "controller", the ovn-controller would resubmit the
packet to
Table 35 (OFTABLE_CONTROLLER).
- Each ovn-controller would add a flow in the table 35 to actually
forward the packet to the "controller" as packet-in for each of the
ports bound
to the chassis.
Since the dhcp packets generated by the VM ports are broadcast packets,
the desired action is to flood them - and ovn-northd already does it.
What I understand from your comments is
- there is nothing to be done in ovn-northd.
- and to add necessary rules in ovn-controller to send the packet to
the "controller" if the packet is dhcp.
Please correct me if I am wrong. Also if you have better way to do it
please let us know.
Thanks
Numan
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
