Here's the blueprint… https://blueprints.launchpad.net/quantum/+spec/configurable-ip-allocation
On Jun 21, 2013, at 5:34 PM, Edgar Magana <emag...@plumgrid.com> wrote: > Mark, > > Can you point me to the BP for this feature? > I want to keep an eye on it. > > Thanks, > > Edgar > > From: Mark McClain <mark.mccl...@dreamhost.com> > Reply-To: OpenStack List <openstack-dev@lists.openstack.org> > Date: Friday, June 21, 2013 12:41 PM > To: OpenStack List <openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [Networking] Allocation of IPs > > There will be a deployment option where you can configure the default IP > allocator. Additionally, the allocator will be configurable at subnet > creation time. > > mark > > > On Jun 20, 2013, at 4:51 PM, Edgar Magana <emag...@plumgrid.com> wrote: > >> Could it be possible to add a flag to disable the allocation for the IP? >> If the "no allocation" flag is enabled, all ports will have an empty value >> for IPs. >> It will increase the config parameters in quantum, should we try it? >> >> Edgar >> >> From: Mark McClain <mark.mccl...@dreamhost.com> >> Reply-To: OpenStack List <openstack-dev@lists.openstack.org> >> Date: Thursday, June 20, 2013 1:13 PM >> To: OpenStack List <openstack-dev@lists.openstack.org> >> Subject: Re: [openstack-dev] [Networking] Allocation of IPs >> >> There's work under way to make IP allocation pluggable. One of the options >> will include not having an allocator for a subnet. >> >> mark >> >> On Jun 20, 2013, at 2:36 PM, Edgar Magana <emag...@plumgrid.com> wrote: >> >>> Developers, >>> >>> So far in Networking (formerly Quantum) IPs are pre-allocated when a new >>> port is created by the following def: >>> _allocate_ips_for_port(self, context, network, port): >>> >>> 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? >>> 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. >>> >>> Cheers, >>> >>> Edgar >>> >>> _______________________________________________ >>> OpenStack-dev mailing list >>> OpenStack-dev@lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> _______________________________________________ OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.orghttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > _______________________________________________ OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
