> > We can use the dhcp-port (and its IP address) for the distributed-port. > > The current native-dhcp proposal > (http://openvswitch.org/pipermail/dev/2016-April/069787.html) > assumes that a dhcp-server ip-address "server_id" is defined on the subnet. > > action=(dhcp_offer(offerip = 10.0.0.2, router = 10.0.0.1, > server_id = 10.0.0.2, mtu = 1300, lease_time = 3600, > > For openstack, This means that a DHCP port has been created on that > subnet in neutron. >
The networking-ovn patch for native dhcp support presently doesn't create a dhcp port in the create subnet method [1] Either this patch [1] can create the dhcp port or it can be created when the metadata changes are ready. Please let me know if you have any comments on the gerrit review [1] - https://review.openstack.org/#/c/243174/10/networking_ovn/plugin.py In the absence of a dhcp-agent, the neutron-ovn-plugin would have to > auto-create the > dhcp-port in neutron upon creation of a subnet, and then use that > port's IP address as > the "server_id" when it programs the "dhcp-options" > column of the Logical_Switch table. > > > _______________________________________________ > dev mailing list > dev@openvswitch.org > http://openvswitch.org/mailman/listinfo/dev > _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
