[openstack-dev] Status of Neutron IPv6 dual stack
Xuhan Peng
pengxuhan at gmail.com
Sat Nov 22 13:50:18 UTC 2014
Harm,
We were not able to enable dual stack with l3 routers in Juno release. You may need to wait for Kilo to see if that can be pushed in.
Xu Han
—
Xu Han Peng (xuhanp)
On Sat, Nov 22, 2014 at 3:03 AM, Harm Weites <harm at weites.com> wrote:
> Hi,
> We're running Juno since a few weeks now, is it now possible to go dual
> stack with l3-routers or are there some pieces missing and should I wait
> for Kilo?
> -Harm
> On 08/19/2014 07:08 PM, Dane Leblanc (leblancd) wrote:
>>
>> Hi Harm:
>>
>>
>>
>> Unfortunately I haven’t had time to complete the changes yet. Even
>> if/when these changes are completed, it’s unlikely that this blueprint
>> will get approved for Juno, but I’ll see what I can do.
>>
>>
>>
>> Thanks,
>>
>> Dane
>>
>>
>>
>>
>>
>> *From:*Harm Weites [mailto:harm at weites.com]
>> *Sent:* Tuesday, August 19, 2014 12:53 PM
>> *To:* openstack-dev at lists.openstack.org
>> *Subject:* Re: [openstack-dev] Status of Neutron IPv6 dual stack
>>
>>
>>
>> Thiago,
>>
>> My old setup was dual-stacked, simply using a flat linuxbridge. It's
>> just that I now realy would like to separate multiple tenants using L3
>> routers, which should be easy (dual stacked) to achieve once Dane's
>> work is completed.
>>
>> Did you find the time to commit those required changes for that yet Dane?
>>
>> Regards,
>> Harm
>>
>> op 16-08-14 23:33, Martinx - ジェームズ schreef:
>>
>> Guys,
>>
>>
>>
>> Just for the record, I'm using IceHouse in a Dual-Stacked
>> environment (with security groups working) but, Instance's IPv6
>> address are static (no upstream SLAAC, arrived in Juno-2, I think)
>> and the topology is `VLAN Provider Networks`, no Neutron L3
>> Router. Where each VLAN have v4/v6 addrs, same upstream router
>> (also dual-stacked - still no radvd enabled).
>>
>>
>>
>> Looking forward to start testing L3 + IPv6 in K...
>>
>>
>>
>> Best,
>>
>> Thiago
>>
>>
>>
>> On 16 August 2014 16:21, Harm Weites <harm at weites.com
>> <mailto:harm at weites.com>> wrote:
>>
>> Hi Dane,
>>
>> Thanks, that looks promising. Once support for multiple v6
>> addresses on
>> gateway ports is added I'll be happy to give this a go. Should it work
>> just fine with an otherwise Icehouse based deployment?
>>
>> Regards,
>> Harm
>>
>> op 16-08-14 20:31, Dane Leblanc (leblancd) schreef:
>>
>> > Hi Harm:
>> >
>> > Can you take a look at the following, which should address this:
>> >
>> https://blueprints.launchpad.net/neutron/+spec/multiple-ipv6-prefixes
>> >
>> > There are some diffs out for review for this blueprint:
>> > https://review.openstack.org/#/c/113339/
>> > but the change to support 1 V4 + multiple V6 addresses on a
>> gateway port hasn't been added yet. I should be adding this soon.
>> >
>> > There was a request for a Juno feature freeze exception for this
>> blueprint, but there's been no response, so this may not get
>> approved until K release.
>> >
>> > -Dane
>> >
>> > -----Original Message-----
>> > From: Harm Weites [mailto:harm at weites.com <mailto:harm at weites.com>]
>> > Sent: Saturday, August 16, 2014 2:22 PM
>> > To: openstack-dev at lists.openstack.org
>> <mailto:openstack-dev at lists.openstack.org>
>> > Subject: [openstack-dev] Status of Neutron IPv6 dual stack
>> >
>> > Hi,
>> >
>> > Given the work on [1] has been abandoned, I'm wondering what the
>> current status of going dual stack is. Of course, given Neutron
>> got something like that on it's roadmap.
>> >
>> > The initial BP [2] aimed for Havana and Icehouse, and I'm
>> unaware of something similar to achieve a dual stack network. What
>> are the options, if any? To my knowledge it all comes down to
>> supporting multiple exterior interfaces (networks) on a l3-agent,
>> which is currently limited to just 1: either IP4 or IP6.
>> >
>> > [1] https://review.openstack.org/#/c/77471/
>> > [2]
>> >
>> https://blueprints.launchpad.net/neutron/+spec/allow-multiple-subnets-on-gateway-port
>> >
>> > Regards,
>> > Harm
>> >
>> > _______________________________________________
>> > OpenStack-dev mailing list
>> > OpenStack-dev at lists.openstack.org
>> <mailto: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
>> <mailto: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
>> <mailto: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 <mailto: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/20141122/5e119bde/attachment.html>
More information about the OpenStack-dev
mailing list