vmware-nsx

History

Salvatore Orlando 933088ac79 Ensure metadata access network does not prevent router deletion Bug 1152136 This patch checks if a metadata access network is still present when removing a router in the NVP plugin. If yes, the network is detached from the router and then destroyed, thus ensuring a safe completion of the operation as well as removal of metadata access network resources. Change-Id: Id8be6ec50ab4536f4ae9916dadaed56644597c7c		2013-03-09 00:23:29 +01:00
..
api_client	Fixes i18n messages in nvp plugin	2013-01-10 18:15:41 -08:00
common	Ensure metadata access network does not prevent router deletion	2013-03-09 00:23:29 +01:00
extensions	Remove compat cfg wrapper	2013-02-27 22:15:54 +09:00
__init__.py	Remove relative imports from NVP plugin	2013-01-09 18:33:07 +00:00
check_nvp_config.py	Add check-nvp-config utility	2013-02-20 14:03:55 -08:00
nicira_db.py	Enable multiple L3 GW services on NVP plugin	2013-02-27 03:06:21 +01:00
nicira_models.py	Enable multiple L3 GW services on NVP plugin	2013-02-27 03:06:21 +01:00
nicira_networkgw_db.py	Fixes import reorder nits	2013-02-26 10:37:59 +08:00
nicira_qos_db.py	Avoid sending names longer than 40 character to NVP	2013-03-04 18:25:43 +01:00
nvp_cluster.py	Add check-nvp-config utility	2013-02-20 14:03:55 -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 explicit egress rules to nvp security profile	2013-03-08 09:48:19 -08:00
QuantumPlugin.py	Ensure metadata access network does not prevent router deletion	2013-03-09 00:23:29 +01: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