54c05b500a
(Patch set #3 for the multiple-ipv6-prefixes blueprint) Provides support for adding multiple IPv6 subnets to an internal router port. The limitation of one IPv4 subnet per internal router port remains, though a port may contain one IPv4 subnet with any number of IPv6 subnets. This changes the behavior of both the router-interface-add and router-interface-delete APIs. When router-interface-add is called with an IPv6 subnet, the subnet will be added to an existing internal port on the router with the same network ID if the existing port already has one or more IPv6 subnets. Otherwise, a new port will be created on the router for that subnet. When calling the router-interface-add with a port (one that has already been created using the port-create command), that port will be added to the router if it meets the following conditions: 1. The port has no more than one IPv4 subnet. 2. If the port has any IPv6 subnets, it must not have the same network ID as an existing port on the router if the existing port has any IPv6 subnets. If the router-interface-delete command is called with a subnet, that subnet will be removed from the router port to which it belongs. If the subnet is the last subnet on a port, the port itself will be deleted from the router. If the router-interface-delete command is called with a port, that port will be deleted from the router. This change also allows the RADVD configuration to support advertising multiple prefixes on a single router interface. DocImpact Change-Id: I7d4e8194815e626f1cfa267f77a3f2475fdfa3d1 Closes-Bug: #1439824 Partially-implements: blueprint multiple-ipv6-prefixes |
||
---|---|---|
bin | ||
doc | ||
etc | ||
neutron | ||
rally-jobs | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.pylintrc | ||
.testr.conf | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
MANIFEST.in | ||
README.rst | ||
TESTING.rst | ||
babel.cfg | ||
openstack-common.conf | ||
requirements.txt | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
Welcome!
You have come across a cloud computing network fabric controller. It has identified itself as "Neutron." It aims to tame your (cloud) networking!
External Resources:
The homepage for Neutron is: http://launchpad.net/neutron. Use this site for asking for help, and filing bugs. Code is available on git.openstack.org at <http://git.openstack.org/cgit/openstack/neutron>.
The latest and most in-depth documentation on how to use Neutron is available at: <http://docs.openstack.org>. This includes:
- Neutron Administrator Guide
-
http://docs.openstack.org/admin-guide-cloud/content/ch_networking.html
- Neutron API Reference:
-
http://docs.openstack.org/api/openstack-network/2.0/content/
- Current Neutron developer documentation is available at:
For help on usage and hacking of Neutron, please send mail to <mailto:openstack-dev@lists.openstack.org>.
For information on how to contribute to Neutron, please see the contents of the CONTRIBUTING.rst file.