Add a blueprint for ipv6-provider-nets-slaac

Change-Id: Id06bee32b4105767cc35b5f86db0cb803874849d
This commit is contained in:
Sean M. Collins 2014-04-16 14:07:09 -04:00
parent 4f354e9fd2
commit 3217363c5f
1 changed files with 52 additions and 0 deletions

View File

@ -0,0 +1,52 @@
============================================
Provider Networking - upstream SLAAC Support
============================================
It should be possible to create a Provider Network in Neutron, that uses an
upstream switch or router that advertises RA's - so that instances can use
SLAAC to configure their IPv6 networking, while still utilizing the Neutron
APIs for security group rules.
https://blueprints.launchpad.net/neutron/+spec/ipv6-provider-nets-slaac
It should be possible to create a Provider Network in Neutron, that uses an
upstream switch or router that advertises RA's - so that instances can use
SLAAC to configure their IPv6 networking, while still utilizing the Neutron
APIs for security group rules.
Problem description
===================
A deployer of OpenStack that wishes to use IPv6 and already has
configured IPv6 on northbound networking devices, may wish to
advertise IPv6 routes by having a non-OpenStack hardware transmit
ICMPv6 Router Advertisement packets.
OpenStack Neutron should support this configuration, and display the
correct IP address for instances, since Neutron has enough information
to generate the EUI-64 address.
Implementation
==============
* Subnets will be created with the `ipv6_address_mode` set to `slaac`
and `ipv6_ra_mode` *not* set.
* Neutron will calculate the IP address of a port, using the MAC address
and the CIDR.
Assignee
--------
Primary assignee:
scollins
Testing
-------
* Add unit tests to support Subnets created with only the
`ipv6_address_mode` set.
* Verify that ports with allocations from a subnet with
`ipv6_address_mode` set are not touched by the DHCP agent.