From ba18f8a9f83bae6dd8d9324934b31536f9d6936a Mon Sep 17 00:00:00 2001 From: Cao Xuan Hoang Date: Fri, 8 Dec 2017 14:26:51 +0700 Subject: [PATCH] [doc] Update for devstack configuration Now that VPNaaS is running under L3 agent extension. There is no need extra steps. Change-Id: I0f6a6dfe83f81da9d98b7ba1bd1b594eed4152e8 Related-bug: 1692131 --- doc/source/devref/devstack.rst | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/doc/source/devref/devstack.rst b/doc/source/devref/devstack.rst index b583f605d..a5cfc55bf 100644 --- a/doc/source/devref/devstack.rst +++ b/doc/source/devref/devstack.rst @@ -13,8 +13,8 @@ deploy to a multinode setup requires the following things to happen: #. Each controller node requires database migrations in support of running VPNaaS. -#. Each network node that would run the L3 agent needs to run the Neutron - VPNaaS agent in its place. + +#. Each network node that would run VPNaaS L3 agent extension. Therefore, the devstack plugin script needs some extra logic. @@ -49,6 +49,3 @@ This VPNaaS devstack plugin code will then #. Apply database migrations on nodes that are running the controller (as determined by enabling the q-svc service), - -#. Run the VPNaaS agent on nodes that would normally be running the L3 agent - (as determined by enabling the q-l3 service).