vmware-nsx/neutron/plugins/nicira/README
armando-migliaccio 288eac9f47 Removes unused nvp plugin config param
nvp_cluster_uuid is no longer used; it was missed
during the configuration file tweaks that was done
during Havana.

Change-Id: Id6dd684833c99453cd97d88584be04d99fd21550
Closes-bug: #1251086
2013-11-13 18:22:53 -08:00

44 lines
1.8 KiB
Plaintext

nvp-plugin
-----------------------------------------------------------------------------
Overview and pre-requisites
This is a Neutron plugin that can talk to a set of NVP controllers and
implements the core Neutron v2 api. In order to use it you must have
Nicira NVP running and configured. You must also have Neutron installed
and configured.
NVP Plugin configuration
1) Database configuration
The NVP plugin leverages the Neutron database. The following connection
parameters should be specified:
- connection: Database connection string
- max_retries: Maximum number of connection attempts (default 10)
- retry_interval: Gap between connection attempts (default 2 seconds)
2) NVP (general)
- max_lp_per_bridged_ls: Maximum number of ports of a logical switch on a
bridged transport zone (default 64)
- concurrent_connections: Number of connects to each controller node
(default 3)
- nvp_gen_timout: Number of seconds a generation id should be valid for
(default -1 meaning do not time out)
3) NVP cluster
By default the Neutron NVP plugin can talk to multiple controllers in a
single cluster. In the future (Havana+) support for multiple clusters
will be added.
The following parameters can be configured:
- default_tz_uuid: This is uuid of the default NVP Transport zone that
will be used for creating tunneled isolated "Neutron" networks. It
needs to be created in NVP before starting Neutron with the nvp plugin.
- nvp_controllers: describes the list of controllers
More details can be found in etc/neutron/plugins/nicira/nvp.ini
Neutron Configuration
Modify your Neutron configuration for using the NVP Plugin:
core_plugin =
neutron.plugins.nicira.neutronPlugin.NvpPluginV2