Re: [ovs-dev] [PATCH v5 2/2] ovn: Add logical flows to support native DHCP

> The reason for not adding the flow in IN_ACL is because the CMS can add > flows to allow or drop DHCP traffic on a logical port if it wants to. In > the case of OpenStack networking-ovn, it is adding the below flows for each > logical port. > > table=4( ls_in_acl), priority= 2002,

Re: [ovs-dev] [PATCH v5 2/2] ovn: Add logical flows to support native DHCP

On Tue, May 17, 2016 at 4:05 AM, Ramu Ramamurthy wrote: > Tested-by: Ramu Ramamurthy > > I tested v5 of this patchset to work end-to-end with openstack (using > your openstack changes which are also under review). The options tested >

Re: [ovs-dev] [PATCH v5 2/2] ovn: Add logical flows to support native DHCP

Tested-by: Ramu Ramamurthy I tested v5 of this patchset to work end-to-end with openstack (using your openstack changes which are also under review). The options tested include dns-server and classless-static-route. A question I have is why you program these out-acl

[ovs-dev] [PATCH v5 2/2] ovn: Add logical flows to support native DHCP

OVN implements a native DHCP support which caters to the common use case of providing an IP address to a booting instance by providing stateless replies to DHCP requests based on statically configured address mappings. To do this it allows a short list of DHCP options to be configured and applied