summaryrefslogtreecommitdiffstats
path: root/docs/setupservicevm/index.rst
diff options
context:
space:
mode:
authorBin Hu <bh526r@att.com>2016-01-08 22:27:13 -0800
committerBin Hu <bh526r@att.com>2016-01-08 22:27:13 -0800
commit987aa5e0d106068f6c4887ba21bcd4321cb7f203 (patch)
tree5801a00c40359a73d6c3d0d68c154aea4e28409f /docs/setupservicevm/index.rst
parent1d0d7b0d1a9eeaa3d6c9f17aec1d1907e8fe6bff (diff)
JIRA:IPVSIX-29
Change-Id: Iadb01d1dd79e1da05003bbc524040c03d20abe88 Signed-off-by: Bin Hu <bh526r@att.com>
Diffstat (limited to 'docs/setupservicevm/index.rst')
-rw-r--r--docs/setupservicevm/index.rst10
1 files changed, 10 insertions, 0 deletions
diff --git a/docs/setupservicevm/index.rst b/docs/setupservicevm/index.rst
index 292cffe..f498138 100644
--- a/docs/setupservicevm/index.rst
+++ b/docs/setupservicevm/index.rst
@@ -23,6 +23,16 @@ environment. There are three scenarios.
controller which is built from the latest stable/Lithium branch which includes the fix.
In this scenario, we can fully automate the setup similar to Scenario 1.
+Please **NOTE** that the instructions in this document assume the deployment model of single
+controller node. In case of HA (High Availability) deployment model where multiple controller
+nodes are used, the setup procedure is the same. In particular:
+
+* There is **No Impact** on Scenario 1 and Scenario 3.
+* For Scenario 2, when ``ipv6-router`` is created in step **SETUP-SVM-11**, it could be
+ created in any of the controller node. Thus you need to identify in which controller node
+ ``ipv6-router`` is created in order to manually spawn ``radvd`` daemon inside the
+ ``ipv6-router`` namespace in steps **SETUP-SVM-24** through **SETUP-SVM-30**.
+
.. toctree::
:numbered:
:maxdepth: 4