blob: ef064b75685c00019aeb7ee7159d974b889e940c (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
|
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
.. (c) Bin Hu (AT&T) and Sridhar Gaddam (RedHat)
====================
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
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
is ``192.168.0.10``
* The hostname of OpenStack Compute Node is ``opnfv-os-compute``, and the host IP address is ``192.168.0.20``
* The hostname of Open Daylight Controller Node is ``opnfv-odl-controller``, and the host IP address is
``192.168.0.30``
* We use ``opnfv`` as username to login.
* We use ``devstack`` to install OpenStack Kilo. Please note that OpenStack Liberty can be used as well.
The underlay network topology of those 3 hosts are shown as follows in :numref:`s2-figure1`:
.. figure:: images/ipv6-topology-scenario-2.png
:name: s2-figure1
:width: 100%
Underlay Network Topology - Scenario 2
**Please note that the IP address shown in** :numref:`s2-figure1`
**are for exemplary purpose. You need to configure your public IP
address connecting to Internet according to your actual network
infrastructure. And you need to make sure the private IP address are
not conflicting with other subnets**.
|
