[openstack-dev] [Neutron] [Spec freeze exception] Support Stateful and Stateless DHCPv6 by dnsmasq

Xuhan Peng pengxuhan at gmail.com
Mon Jul 28 02:02:07 UTC 2014


Thanks Kyle and everyone for supporting this! Will try the best to make the code ready for Juno-3.


Xu Han 
—
Sent from Mailbox for iPhone

On Fri, Jul 25, 2014 at 11:06 PM, Kyle Mestery <mestery at mestery.com>
wrote:

> On Thu, Jul 24, 2014 at 8:46 PM, CARVER, PAUL <pc2929 at att.com> wrote:
>> Collins, Sean wrote:
>>
>>> On Wed, Jul 23, 2014 at 12:06:06AM EDT, Xu Han Peng wrote:
>>>> I would like to request one Juno Spec freeze exception for "Support Stateful
>>>> and Stateless DHCPv6 by dnsmasq" BP.
>>>>
>>>> The spec is under review:
>>>> https://review.openstack.org/#/c/102411/
>>>>
>>>> Code change for this BP is submitted as well for a while:
>>>> https://review.openstack.org/#/c/106299/
>>
>>>I'd like to +1 this request, if this work landed in Juno, this would
>>>mean Neutron would have 100% support for all IPv6 subnet attribute
>>>settings, since slaac support landed in J-2.
>>
>> +1 on this from me too. It's getting more and more difficult to keep
>> claiming OpenStack will have IPv6 "any day now" and not having it
>> in Juno will hurt credibility a lot.
>>
>> IPv4 address space is basically gone. AT&T has a fair amount of it
>> but even we're feeling the pinch. A lot of companies have it worse.
>> NAT is a mediocre stop-gap at best.
>> We've been running IPv6 in production for well over a year.
>>
>> Our pre-OpenStack environments support IPv6 where needed
>> even though we have a lot of IPv4 running where we aren't feeling
>> immediate pressure. We're having to turn internal applications away
>> from our OpenStack based cloud because they require IPv6 and we
>> can't provide it.
>>
>> We're actively searching for workarounds but none of them are
>> attractive.
>>
> I've given a spec exception to this, and targeted this work at Juno-3
> as medium priority. Given that at the start of Juno we agreed to get
> to IPV6 parity in Juno, this one falls into the community work area
> for exceptions.
> Thanks,
> Kyle
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140727/348c5206/attachment.html>


More information about the OpenStack-dev mailing list