Shixiong,
I'm fine with the current two modes design.
—
Xu Han Peng (xuhanp)
On Sat, Jan 25, 2014 at 5:17 AM, Shixiong Shang
<sparkofwisdom.cl...@gmail.com> wrote:
> Any decisions yet?
> Shixiong
> On Jan 23, 2014, at 7:45 AM, Veiga, Anthony <anthony_ve...@cable.comcast.com>
> wrote:
>>
>>> 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.
>>
>>
>> We were initially intending to treat enable_dhcp as an on-off flag for IPv6.
>> If it's off, then we won't even bother with the other two attributes.
>> Because of the issues already being discussed elsewhere in Neutron, you
>> can't assign multiple scopes to a subnet so it's safe to assume that there
>> won't be an IPv4 scope in an IPv6 subnet.
>>
>>>
>>> Salvatore
>>>
>>>
>>> On 23 January 2014 04:21, Shixiong Shang <sparkofwisdom.cl...@gmail.com>
>>> 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
>>>> <sean_colli...@cable.comcast.com> 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
>>>> > 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
