armando-migliaccio 4ad3cae6ff Add migration support from agent to NSX dhcp/metadata services
This is feature patch (3 of 3) that introduces support for
transitioning existing NSX-based deployments from the agent
based model of providing dhcp and metadata proxy services
to the new agentless based mode. In 'combined' mode, existing
networks will still be served by the existing infrastructure,
whereas new networks will be served by the new infrastructure.

Networks may be migrated to the model using a new CLI tool
provided, called 'neutron-nsx-manage'. Currently the tool
provides two admin-only commands:

  neutron-nsx-manage net-report <net-id-or-name>

This will check that the network can be migrated and returns
the resources currently in use. And:

  neutron-nsx-manage net-migrate <net-id-or-name>

This will move the network over the new model and deallocate
resources from the agent. Once a network has been migrated
there is no turning back.

Completes-blueprint nsx-integrated-services

Change-Id: I37c9aa0e76124e1023899106406de7be6714c24d
2014-02-10 17:27:14 -08:00
..
2013-12-03 15:03:47 -08:00
2013-07-06 15:02:43 -04:00
2013-12-03 15:03:47 -08: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 5000)
    - concurrent_connections: Number of connects to each controller node
    (default 10)
    - 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.
    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