![]() When the service insertion is first enabled, and a security group is created, the plugin should do 2 things to allow the user to start working with service insertion immediately: 1. Add all the current compute ports (VMs) to service insertion security group. 2. Depending on the configuration, the driver will create any->any flow classifier entry, and any->any redirect rule at the backend so all the traffic will be redirected to the security partner. DocImpact: new nsxv configuration: service_insertion_redirect_all In True the plugin will create a rule to redirect all the traffic to the security partner. Change-Id: I2d45f4db821e205ccb09f02e2579d05c938c2658 |
||
---|---|---|
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.