<div dir="ltr">Gotcha, The part that was confusing was:<div><br></div><div><div style="font-family:Calibri,sans-serif;font-size:14.399999618530273px">>Could it be possible to add a flag to disable the allocation for the IP?</div>
<div style="font-family:Calibri,sans-serif;font-size:14.399999618530273px">>If the "no allocation" flag is enabled, all ports will have an empty value for IPs.</div><div><br></div><div>So what you are looking to do is to provide the IP address from the plugin and not the db_base class it seems? In this case all you need to do is implement: <br>
</div><div><br></div><div>_allocate_ips_for_port() in your plugin and then that method will be called instead of the base class one. <br></div><div><br></div><div>Aaron</div><div><br></div></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Fri, Jun 28, 2013 at 12:48 PM, Edgar Magana <span dir="ltr"><<a href="mailto:emagana@plumgrid.com" target="_blank">emagana@plumgrid.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="font-size:14px;font-family:Calibri,sans-serif;word-wrap:break-word"><div>Aaron,</div><div><br></div><div>You are totally right, the point is that I don't want to loose the IPAM info in Neutron because that is the moment when the backend plugin deploys a new DHCP server into the Virtual Networking Infrastruture. So, every time that a user creates a subnet and enables DHCP our plugin deploys a new DHCP service.</div>
<div><br></div><div>I am sure that is me the one missing something!!! :-) </div><div><br></div><div>Thanks,</div><div><br></div><div>Edgar</div><div><br></div><span><div style="border-right:medium none;padding-right:0in;padding-left:0in;padding-top:3pt;text-align:left;font-size:11pt;border-bottom:medium none;font-family:Calibri;border-top:#b5c4df 1pt solid;padding-bottom:0in;border-left:medium none">
<div class="im"><span style="font-weight:bold">From: </span> Aaron Rosen <<a href="mailto:arosen@nicira.com" target="_blank">arosen@nicira.com</a>><br><span style="font-weight:bold">Reply-To: </span> OpenStack List <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
</div><span style="font-weight:bold">Date: </span> Friday, June 28, 2013 12:07 PM<div><div class="h5"><br><span style="font-weight:bold">To: </span> OpenStack List <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span> Re: [openstack-dev] [Networking] Allocation of IPs<br></div></div></div><div><div class="h5"><div><br></div><div dir="ltr"><div>Hi Edgar, <br><br>I'm still not following. In your original question you asked how to you create a port and not allocate an ip address to it at all so that you can leverage a real dhcp server to do that. In order to do that you can create a network without a subnet but then you loose the ipam info in quantum. Or write a script that notifies your dhcp server the mac-ip bindings each instance should have. Am i missing something here? <br>
<br></div><div>Thanks,<br></div><div><br></div>Aaron<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jun 27, 2013 at 11:00 PM, Edgar Magana <span dir="ltr"><<a href="mailto:emagana@plumgrid.com" target="_blank">emagana@plumgrid.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div style="font-size:14px;font-family:Calibri,sans-serif">Aaron,</div><div style="font-size:14px;font-family:Calibri,sans-serif">
<br></div><div style="font-size:14px;font-family:Calibri,sans-serif">Because the create create_subnet API is the one that enables/disables the DHCP:</div><div><p style="margin:0px"></p><p style="color:rgb(36,48,45);font-family:Helvetica;font-size:12px;margin:0px">
quantum subnet-create <network> <CIDR> <span style="font-family:Monaco">--enable_dhcp False</span></p><p style="color:rgb(36,48,45);font-family:Helvetica;font-size:12px;margin:0px"><span style="font-family:Monaco"><br>
</span></p><p style="margin:0px"><font face="Monaco" color="#24302d"><span style="font-size:12px">Besides, the CIDR is actually the information that is sent to the DHCP to locate IP Addresses.</span></font></p><p style="margin:0px">
<font face="Monaco" color="#24302d"><span style="font-size:12px"><br></span></font></p><p style="margin:0px"><font face="Monaco" color="#24302d"><span style="font-size:12px">Thanks,</span></font></p><p style="margin:0px">
<font face="Monaco" color="#24302d"><span style="font-size:12px"><br></span></font></p><p style="margin:0px"><font face="Monaco" color="#24302d"><span style="font-size:12px">Edgar</span></font></p><p></p></div><div style="font-size:14px;font-family:Calibri,sans-serif">
<br></div><span style="font-size:14px;font-family:Calibri,sans-serif"><div style="border-right:medium none;padding-right:0in;padding-left:0in;padding-top:3pt;text-align:left;font-size:11pt;border-bottom:medium none;font-family:Calibri;border-top:#b5c4df 1pt solid;padding-bottom:0in;border-left:medium none">
<span style="font-weight:bold">From: </span> Aaron Rosen <<a href="mailto:arosen@nicira.com" target="_blank">arosen@nicira.com</a>><br><span style="font-weight:bold">Reply-To: </span> OpenStack List <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span> Thursday, June 27, 2013 8:59 AM<div><div><br><span style="font-weight:bold">To: </span> OpenStack List <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span> Re: [openstack-dev] [Networking] Allocation of IPs<br></div></div></div><div><div><div><br></div><div dir="ltr">Hi Edgar, <br><br>In this case if you don't associate a subnet with a network you should achieve that. Why doesn't that work? <br>
<div><br></div><div>Thanks, <br><br>Aaron<br></div><div><br><br></div></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div>On Thu, Jun 20, 2013 at 1:51 PM, Edgar Magana <span dir="ltr"><<a href="mailto:emagana@plumgrid.com" target="_blank">emagana@plumgrid.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="font-size:14px;font-family:Calibri,sans-serif;word-wrap:break-word"><div><div><div>Could it be possible to add a flag to disable the allocation for the IP?</div>
<div>If the "no allocation" flag is enabled, all ports will have an empty value for IPs.</div><div> It will increase the config parameters in quantum, should we try it?</div><div><br></div><div>Edgar</div><div><br>
</div></div></div><span><div><div><div style="border-right:medium none;padding-right:0in;padding-left:0in;padding-top:3pt;text-align:left;font-size:11pt;border-bottom:medium none;font-family:Calibri;border-top:#b5c4df 1pt solid;padding-bottom:0in;border-left:medium none">
<span style="font-weight:bold">From: </span> Mark McClain <<a href="mailto:mark.mcclain@dreamhost.com" target="_blank">mark.mcclain@dreamhost.com</a>><br><span style="font-weight:bold">Reply-To: </span> OpenStack List <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span> Thursday, June 20, 2013 1:13 PM<br><span style="font-weight:bold">To: </span> OpenStack List <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span> Re: [openstack-dev] [Networking] Allocation of IPs<br></div></div></div><div><div><div><div><div><br></div><div><div style="word-wrap:break-word">There's work under way to make IP allocation pluggable. One of the options will include not having an allocator for a subnet.<div>
<br><div>mark</div><div><br><div><div>On Jun 20, 2013, at 2:36 PM, Edgar Magana <<a href="mailto:emagana@plumgrid.com" target="_blank">emagana@plumgrid.com</a>> wrote:</div><br><blockquote type="cite"><div style="word-wrap:break-word;font-size:14px;font-family:Calibri,sans-serif">
<div>Developers,</div><div><br></div><div>So far in Networking (formerly Quantum) IPs are pre-allocated when a new port is created by the following def:</div><div>_allocate_ips_for_port(self, context, network, port):</div>
<div><br></div><div>If we are using a real DHCP (not the dnsmasq process) that does not accept static IP allocation because it only allocates IPs based on its own algorithm, how can we tell Networking to not allocate an IP at all?</div>
<div>I don’t think that is possible based on the code but I would like to know if somebody has gone through the same problem and have a workaround solution.</div><div><br></div><div>Cheers,</div><div><br></div><div>Edgar</div>
<div><br></div></div>
_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div><br></div></div></div></div></div></div>_______________________________________________
OpenStack-dev mailing list
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></div>
</div></span></div><div><br>_______________________________________________<br>
OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></div></blockquote></div><br></div><div>
_______________________________________________
OpenStack-dev mailing list
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></div>
</span></div><br>_______________________________________________<br>
OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>
_______________________________________________
OpenStack-dev mailing list
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</div></div></span></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>