<div dir="ltr">Yes. The code will still require something to acknowledge that DHCP has been wired for a port whether or not the agent extension is present.</div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 31, 2017 at 3:39 AM, Neil Jerram <span dir="ltr"><<a href="mailto:neil@tigera.io" target="_blank">neil@tigera.io</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Thanks for the heads up, Kevin!<div><br></div><div>Is this still necessary if a deployment disables the Neutron server's DHCP scheduling, with</div><div><br></div><div><div>            self._supported_extension_<wbr>aliases.remove("dhcp_agent_<wbr>scheduler")</div></div><div><br></div><div>?</div><div><br></div><div>Thanks,</div><div>      Neil</div><div><br></div></div><br><div class="gmail_quote"><div><div class="h5"><div dir="ltr">On Fri, Mar 31, 2017 at 12:52 AM Kevin Benton <kevin@benton.pub> wrote:<br></div></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr" class="m_462897149994260122gmail_msg">Hi,<div class="m_462897149994260122gmail_msg"><br class="m_462897149994260122gmail_msg"></div><div class="m_462897149994260122gmail_msg">Once [1] merges, a port will not transition to ACTIVE on a subnet with enable_dhcp=True unless something clears the DHCP provisioning block.</div><div class="m_462897149994260122gmail_msg"><br class="m_462897149994260122gmail_msg"></div><div class="m_462897149994260122gmail_msg">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.</div><div class="m_462897149994260122gmail_msg"><br class="m_462897149994260122gmail_msg"></div><div class="m_462897149994260122gmail_msg">Acknowledging that DHCP is ready for a port is a one-line call to the provisioning_blocks module[2]. For more information on provisioning blocks, see [3].</div><div class="m_462897149994260122gmail_msg"><br class="m_462897149994260122gmail_msg"></div><div class="m_462897149994260122gmail_msg">1. <a href="https://review.openstack.org/452009" class="m_462897149994260122gmail_msg" target="_blank">https://review.openstack.<wbr>org/452009</a></div><div class="m_462897149994260122gmail_msg">2. <a href="https://github.com/openstack/neutron/blob/4ed53a880714fd33280064c58e6f91b9ecd3823e/neutron/api/rpc/handlers/dhcp_rpc.py#L292-L294" class="m_462897149994260122gmail_msg" target="_blank">https://github.com/<wbr>openstack/neutron/blob/<wbr>4ed53a880714fd33280064c58e6f91<wbr>b9ecd3823e/neutron/api/rpc/<wbr>handlers/dhcp_rpc.py#L292-L294</a></div><div class="m_462897149994260122gmail_msg">3. <a href="https://docs.openstack.org/developer/neutron/devref/provisioning_blocks.html" class="m_462897149994260122gmail_msg" target="_blank">https://docs.openstack.org/<wbr>developer/neutron/devref/<wbr>provisioning_blocks.html</a></div><div class="m_462897149994260122gmail_msg"><br class="m_462897149994260122gmail_msg"></div><div class="m_462897149994260122gmail_msg">Cheers,<br class="m_462897149994260122gmail_msg">Kevin Benton</div><div class="m_462897149994260122gmail_msg"><br class="m_462897149994260122gmail_msg"></div></div></div></div>
______________________________<wbr>______________________________<wbr>______________<br class="m_462897149994260122gmail_msg">
OpenStack Development Mailing List (not for usage questions)<br class="m_462897149994260122gmail_msg">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" class="m_462897149994260122gmail_msg" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br class="m_462897149994260122gmail_msg">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" class="m_462897149994260122gmail_msg" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br class="m_462897149994260122gmail_msg">
</blockquote></div>
<br>______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br></blockquote></div><br></div>