An openstack deployment with an external DHCP server is definetely a possible scenario; I don't think it can be implemented out-of-the-box with the components provided by the core openstack services, but it should be doable and a possibly even a requirement for deployments which integrate openstack with systems such as Infoblox. Therefore I would not disregard the possibility of an external DHCP server. Regarding the new attributes, I pretty much agree on them. As there's overlap between enable_dhcp and address_mode, it might be worth defining a strategy for deprecating enable_dhcp by adding inclduing also a 'dhcpv4' valid value for this attribute.
Salvatore On 23 January 2014 04:21, Shixiong Shang <[email protected]>wrote: > Any possibility we can nail the keywords in the next 12 - 24 hrs? So we > can decide the scope in Icehouse release and then, discuss who can do what? > > Shixiong > > > > On Jan 22, 2014, at 11:20 AM, Collins, Sean < > [email protected]> wrote: > > > I don't know if it's reasonable to expect a deployment of OpenStack that > > has an *external* DHCP server. It's certainly hard to imagine how you'd > > get the Neutron API and an external DHCP server to agree on an IP > > assignment, since OpenStack expects to be the source of truth. > > > > -- > > Sean M. Collins > > _______________________________________________ > > OpenStack-dev mailing list > > [email protected] > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
