openstack/neutron-vpnaas
Code Issues Proposed changes
neutron-vpnaas/doc/source/devref/devstack.rst
Ryan Moats e544a4f669 Add multi-node devstack support to VPNaaS 
Modify devstack plugin to support multi-node confgurations
(i.e. where the network node is split from the controller node).

DocImpact: Migrate HowTo wiki page to additional devref text

Change-Id: Iac5756ffe75b2125faace54b74b296036905a9b0
Signed-off-by: Ryan Moats <rmoats@us.ibm.com>
2016-01-12 07:53:59 -06:00

1.6 KiB
Raw Blame History

Configuring VPNaaS for DevStack

Multinode vs All-In-One

Devstack typically runs in single or "All-In-One" (AIO) mode. However, it can also be deployed to run on multiple nodes. For VPNaaS, running on an AIO setup is simple, as everything happens on the same node. However, to deploy to a multinode setup requires the following things to happen:

  1. Each controller node requires database migrations in support of running VPNaaS.
  2. Each network node that would run the L3 agent needs to run the Neutron VPNaaS agent in its place.

Therefore, the devstack plugin script needs some extra logic.

How to Configure

To configure VPNaaS, it is only necessary to enable the neutron-vpnaas devstack plugin by adding the following line to the local section of devstack's local.conf file:

enable_plugin neutron-vpnaas <GITURL> [BRANCH]

<GITURL> is the URL of a neutron-vpnaas repository
[BRANCH] is an optional git ref (branch/ref/tag).  The default is master.

For example::

    enable_plugin neutron-vpnaas https://git.openstack.org/openstack/neutron-vpnaas stable/kilo

This VPNaaS devstack plugin code will then

  1. Install the common VPNaaS configuration and code,
  2. Apply database migrations on nodes that are running the controller (as determined by enabling the q-svc service),
  3. Run the VPNaaS agent on nodes that would normally be running the L3 agent (as determined by enabling the q-l3 service).