61c19f3e9c
Previously, an internal metadata network is created for a router whenever a subnet is attached to this router. The purpose of this internal network is to help processing metadata requests from instances on DHCP-disabled networks. This commit adds a config option to create internal metadata networks only when a DHCP-disabled subnet is attached to a router. This will help saving system resources because each metadata network consumes one DHCP name space. Change-Id: Ia56050b3f431dbd65bb39da29ba6dbf8e62e36ea |
||
---|---|---|
devstack | ||
doc/source | ||
etc | ||
releasenotes | ||
tools | ||
vmware_nsx | ||
vmware_nsx_tempest | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.pylintrc | ||
.testr.conf | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
MANIFEST.in | ||
README.rst | ||
TESTING.rst | ||
babel.cfg | ||
requirements.txt | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
VMware-NSX package
You have come across the VMware-NSX family of Neutron plugins
External Resources:
The homepage for the VMware-NSX project is on Launchpad.
Use this site for asking for help, and filing bugs. Code is available both git.openstack.org and github.
For help on usage and hacking of VMware-NSX, please send a message to the openstack-dev mailing list.
For information on how to contribute to VMware-NSX, please see the contents of the CONTRIBUTING.rst file.