diff options
Diffstat (limited to 'docs/setupservicevm/0-ipv6-configguide-prep-infra.rst')
| -rw-r--r-- | docs/setupservicevm/0-ipv6-configguide-prep-infra.rst | 10 |
1 files changed, 8 insertions, 2 deletions
diff --git a/docs/setupservicevm/0-ipv6-configguide-prep-infra.rst b/docs/setupservicevm/0-ipv6-configguide-prep-infra.rst index 9703991..997e12e 100644 --- a/docs/setupservicevm/0-ipv6-configguide-prep-infra.rst +++ b/docs/setupservicevm/0-ipv6-configguide-prep-infra.rst @@ -2,11 +2,17 @@ Infrastructure Setup ==================== -In order to set up the service VM as an IPv6 vRouter, we need to -prepare 3 hosts, each of which has minimum 8GB RAM and 40GB storage. One host is used as OpenStack Controller +In order to set up the service VM as an IPv6 vRouter, we need to prepare 3 hosts, +each of which has minimum 8GB RAM and 40GB storage. One host is used as OpenStack Controller Node. The second host is used as Open Daylight Controller Node. And the third one is used as OpenStack Compute Node. +Please **NOTE** that in case of HA (High Availability) deployment model where multiple controller +nodes are used, the setup procedure is the same. 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**. + For exemplary purpose, we assume: * The hostname of OpenStack Controller+Network+Compute Node is ``opnfv-os-controller``, and the host IP address |