vmware-nsx/neutron/plugins/nicira
armando-migliaccio f1b0dbe7a7 Refactoring for nicira plugin to support NVP DHCP/Metadata services
This initial patch is aimed at decoupling core plugin services from
DHCP and metadata services. The abstraction being introduced is
needed so that the code can support both models where dhcp and
metadata services are provided by external RPC agents or solely by
the server-side plugin.

Supports blueprint nvp-dhcp-metadata-services

Change-Id: I396ee7bbcbd866e4e9d4a79887e844b4f5ec3c9e
2013-09-03 15:04:32 -07:00
..
api_client Add support for the extra route extension in the NVP plugin. 2013-07-12 13:21:17 -07:00
common Refactoring for nicira plugin to support NVP DHCP/Metadata services 2013-09-03 15:04:32 -07:00
dbexts Allow subclasses to modify dict_extend hooks 2013-09-02 17:37:22 -07:00
dhcp_meta Refactoring for nicira plugin to support NVP DHCP/Metadata services 2013-09-03 15:04:32 -07:00
extensions Support for NVP distributed router 2013-08-29 09:56:08 -07:00
__init__.py Rename Quantum to Neutron 2013-07-06 15:02:43 -04:00
check_nvp_config.py Remove references to enable_metadata_access_network_option 2013-08-13 09:04:50 -07:00
dhcpmeta_modes.py Refactoring for nicira plugin to support NVP DHCP/Metadata services 2013-09-03 15:04:32 -07:00
NeutronPlugin.py Refactoring for nicira plugin to support NVP DHCP/Metadata services 2013-09-03 15:04:32 -07:00
nvp_cluster.py Nicira plugin: Reduce message severity to DEBUG from INFO 2013-08-13 09:24:05 -07:00
NvpApiClient.py Deal with 501 errors from NVP correctly 2013-08-22 13:12:15 -07:00
nvplib.py Return 400 if creating a distributed router on old NVP platforms 2013-08-30 08:41:56 -07:00
README Rename Quantum to Neutron 2013-07-06 15:02:43 -04:00

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_cluster_uuid: Optional paramter identifying the UUID of the cluster
      in NVP.  This can be retrieved from NVP management console "admin" section.
    - 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