[openstack-dev] [neutron][ml2] - heads up for mechanism drivers that don't use in tree DHCP agent
neil at tigera.io
Fri Mar 31 10:39:45 UTC 2017
Thanks for the heads up, Kevin!
Is this still necessary if a deployment disables the Neutron server's DHCP
On Fri, Mar 31, 2017 at 12:52 AM Kevin Benton <kevin at benton.pub> wrote:
> Once  merges, a port will not transition to ACTIVE on a subnet with
> enable_dhcp=True unless something clears the DHCP provisioning block.
> If your mechanism driver uses the in-tree DHCP agent, there is nothing you
> need to do. However, if you do not utilize the DHCP agent in your
> deployment scenarios and you offload DHCP to something else, your mechanism
> driver must now explicitly acknowledge that DHCP has been provisioned for
> that port.
> Acknowledging that DHCP is ready for a port is a one-line call to the
> provisioning_blocks module. For more information on provisioning blocks,
> see .
> 1. https://review.openstack.org/452009
> Kevin Benton
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev