Files
vmware-nsx/neutron/plugins/nicira
linb 6a84485b0c Support advanced NVP LBaaS Service
The patch adds NVP advanced LBaaS service support for NVP with
VCNS:
        * NVP LBaaS is an advanced Service of NVP depending on NVP
          advanced service router
            - Once an advanced router id created, one corresponding
              vshield edge will be deployed, and then we can configure
              LB service On the vshield edge
        * NVP LBaaS service plugin still uses LBaaS DB service logic,
          while finally calling vShield Edge to support FWaaS service
            - When creating VIP object, service attaches the object to
              the advanced router with routedserviceinsertion service.
              Then before pushing VIP VCNS call, the server would first
              pushing associated POOL VCNS call and associated Monitor
              VCNS call to vShield Edge. Deleting VIP is opposite
              operation
            - Refering to CUD operation of other objects, service would
              first find the associated VIP object and then find the edge bound to
              the router which vip inserted. Then service would push corresponding
              VCNS call to Vshield Edge
        * on driver part, the driver will first convert the object
          to VSM known object input, and then send a synchronous JSON
          calling to VSM, and receive the result

Implements: blueprint nvp-lbaas-plugin
Change-Id: Iec41f2dc103daddf3bed4d09c147df3865b3dccd
2013-09-17 11:07:28 -07:00
..
2013-09-17 11:07:28 -07:00
2013-09-17 11:07:28 -07:00
2013-07-06 15:02:43 -04:00
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