vmware-nsx

History

Aaron Rosen b77246b844 Need to pass port['port'] to _get_tenant_id_for_create() This change set I9ac44a8e moved this logic out of the transaction which caused this bug. Unit tests did not catch this because this error is caused on NVP since the tenant_id is passed in as a tag and this change resulted in the tenant_id becoming None which is not an allowed tag value. Will improve error handling and edge cases like this to fake_nvpapiclient in different commit. Change-Id: Ib0eaab1f389de98b335f58e9215981adbbf9e2ef		2013-02-17 18:59:35 -08:00
..
api_client	Fixes i18n messages in nvp plugin	2013-01-10 18:15:41 -08:00
common	Use oslo-config-2013.1b3	2013-02-17 17:33:05 +00:00
extensions	Add nvp qos extension	2013-02-16 21:17:12 -08:00
__init__.py	Remove relative imports from NVP plugin	2013-01-09 18:33:07 +00:00
nicira_db.py	L3 API support for nicira plugin	2013-02-11 05:19:04 -08:00
nicira_models.py	L3 API support for nicira plugin	2013-02-11 05:19:04 -08:00
nicira_qos_db.py	Add nvp qos extension	2013-02-16 21:17:12 -08:00
nvp_cluster.py	L3 API support for nicira plugin	2013-02-11 05:19:04 -08:00
nvp_plugin_version.py	Remove relative imports from NVP plugin	2013-01-09 18:33:07 +00:00
NvpApiClient.py	Allow nicira plugin to handle multiple NVP API versions	2013-02-16 01:38:26 +01:00
nvplib.py	Add nvp qos extension	2013-02-16 21:17:12 -08:00
QuantumPlugin.py	Need to pass port['port'] to _get_tenant_id_for_create()	2013-02-17 18:59:35 -08:00
README	Allow nvp_api to load balance requests	2013-01-08 00:39:32 -05:00

README

nvp-plugin
-----------------------------------------------------------------------------

Overview and pre-requisites

    This is a Quantum plugin that can talk to a set of NVP controllers and
    implements the core Quantum v2 api.  In order to use it you must have
    Nicira NVP running and configured.  You must also have Quantum installed
    and configured.

NVP Plugin configuration

    1) Database configuration
    The NVP plugin leverages the Quantum database. The following connection
    parameters should be specified:
    - sql_connection: Database connection string
    - sql_max_retries: Maximum number of connection attempts (default 10)
    - reconnect_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
    The Quantum NVP plugin allow for configuring multiple clusters.
    Each cluster configuration section must be declared in the following way
    in the configuration file: [CLUSTER:cluster_name].
    The following parameters can be configured for each cluster:
    - default_tz_uuid: This is uuid of the default NVP Transport zone that
    will be used for creating tunneled isolated "Quantum" networks. It
    needs to be created in NVP before starting Quantum with the nvp plugin.
        - nova_zone_id: Optional parameter identifying the Nova "zone" that maps
        to this NVP cluster.
        - nvp_cluster_uuid: Optional paramter identifying the UUID of the cluster
        in NVP.  This can be retrieved from NVP management console "admin" section.
        - nvp_controller_connetion: describes a connection to a single NVP
        controller. A different connection for each controller in the cluster can
        be specified; there must be at least one connection per cluster.

Quantum Configuration

    Modify your Quantum configuration for using the NVP Plugin:

    core_plugin =
        quantum.plugins.nicira.nicira_nvp_plugin.QuantumPlugin.NvpPluginV2