diff options
Diffstat (limited to 'docs/setupservicevm/0-ipv6-configguide-prep-infra.rst')
| -rw-r--r-- | docs/setupservicevm/0-ipv6-configguide-prep-infra.rst | 43 |
1 files changed, 43 insertions, 0 deletions
diff --git a/docs/setupservicevm/0-ipv6-configguide-prep-infra.rst b/docs/setupservicevm/0-ipv6-configguide-prep-infra.rst new file mode 100644 index 0000000..695dbca --- /dev/null +++ b/docs/setupservicevm/0-ipv6-configguide-prep-infra.rst @@ -0,0 +1,43 @@ +======================== +Preparing Infrastructure +======================== + +******************** +Architectural Design +******************** + +The architectural design of using a service VM as an IPv6 vRouter is +shown as follows :numref:`figure1`: + +.. figure:: images/ipv6-architecture.png + :name: figure1 + :width: 100% + + Architectural Design of Using a VM as an IPv6 vRouter + +******************** +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. + +For exemplary purpose, we give them hostnames ``opnfv-odl- +controller``, ``opnfv-os-controller``, and ``opnfv-os-compute`` +respectively. + +The underlay network topology of those 3 hosts are shown as follows :numref:`figure2`: + +.. figure:: images/ipv6-topology.png + :name: figure2 + :width: 100% + + Underlay Network Topology + +**Please note that the IP address shown in ``:numref:`figure2``` +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. |