A set of Neutron drivers for the VMware NSX.
Go to file
Carl Baldwin cb30a284f2 Set onlink routes for all subnets on an external network
The addition of the on-link routes gives us some freedom to allocate a
router's IP address from any one of multiple subnets on one external
network.  Different routers can get their IPs from different subnets and
they still have direct on-link connectivity to each other.  For example,
one router with its primary IP from 10.0.0.0/24 and another from
192.168.0.0/24 can communicate directly.  It is important that each
router has on-link routes to *all* of the subnets.

Any router can host floating ips from any of the subnets regardless of
which subnet the primary IP address comes from.

This is an alternative to the "Multiple floating IP pools" section in
the administration guide.  It is a simpler alternative that avoids
having to create multiple external networks.  It is also more flexible
because routers will no longer be restricted to getting floating IPs
from the pool to which they happen to be connected.

DocImpact
Document the procedure for adding subnets to the external network.
Potentially remove the existing procedure for "Multiple floating IP
pools" from the docs.

Change-Id: I2c283f5be0cbb6b5d350cafc1b636c300b796a7b
Closes-Bug: #1312467
2014-05-22 21:47:39 +00:00
bin Use oslo.rootwrap library instead of local copy 2014-02-07 10:58:27 +01:00
doc Merge "Start using oslosphinx theme for docs" 2014-04-15 11:16:29 +00:00
etc Merge "LBaaS VIP doesn't work after delete and re-add" 2014-05-19 10:10:33 +00:00
neutron Set onlink routes for all subnets on an external network 2014-05-22 21:47:39 +00:00
tools Merge "Corrects broken format strings in check_i18n.py" 2014-01-07 14:11:59 +00:00
.coveragerc fix some missing change from quantum to neutron 2013-07-08 12:11:04 +08:00
.gitignore Updates .gitignore 2013-11-28 23:18:03 +08:00
.gitreview Rename quantum to neutron in .gitreview. 2013-07-06 12:25:09 -04:00
.mailmap Add mailmap entry 2014-05-16 13:40:04 -04:00
.pylintrc Remove duplicate module-rgx line in .pylintrc 2014-05-06 22:57:33 +00:00
.testr.conf Add an explicit tox job for functional tests 2014-02-05 17:11:52 +00:00
babel.cfg Use babel to generate translation file 2013-01-24 00:20:32 +08:00
HACKING.rst Cleanup HACKING.rst 2013-11-11 10:32:34 -08:00
LICENSE Adding Apache Version 2.0 license file. This is the official license agreement under which Quantum code is available to 2011-08-08 12:31:04 -07:00
MANIFEST.in Rename Quantum to Neutron 2013-07-06 15:02:43 -04:00
openstack-common.conf Sync service and systemd modules from oslo-incubator 2014-04-04 12:16:50 +02:00
README.rst Rename Quantum to Neutron 2013-07-06 15:02:43 -04:00
requirements.txt Updated from global requirements 2014-05-09 02:24:03 +00:00
run_tests.sh Merge "Don't document non-existing flag '--hide-elapsed'" 2014-02-22 04:05:04 +00:00
setup.cfg Merge "Remove last parts of Quantum compatibility shim" 2014-04-03 01:04:53 +00:00
setup.py Updated from global requirements 2014-04-30 02:41:29 +00:00
test-requirements.txt Start using oslosphinx theme for docs 2014-03-26 15:51:48 +04:00
TESTING.rst Developer documentation 2014-02-26 11:03:46 -05:00
tox.ini Fix H302 violations 2014-05-04 12:40:08 +02:00

# -- 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 github at <http://github.com/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/trunk/openstack-network/admin/content/

Neutron API Reference: http://docs.openstack.org/api/openstack-network/2.0/content/

The start of some developer documentation is available at: http://wiki.openstack.org/NeutronDevelopment

For help using or hacking on Neutron, you can send mail to <mailto:openstack-dev@lists.openstack.org>.