diff options
| author |   Bin Hu <bh526r@att.com> | 2016-08-04 17:08:45 -0700 |
|---|---|---|
| committer | Bin Hu <bh526r@att.com> | 2016-08-04 17:08:45 -0700 |
| commit | 7594135b2d4e27cdee3501b17fa0f95d26dc88be (patch) | |
| tree | 96371a3af565565aef81d3a0452c3cfc03986ef8 | |
| parent | f7fd16d35c7ef53dba3468530c665d3a880004e8 (diff) | |
Fix number bullet issue
Change-Id: If98ad5fcabe86cf78f88edae266ac5ad254af67d
Signed-off-by: Bin Hu <bh526r@att.com>
| -rw-r--r-- | docs/configguide/index.rst | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/configguide/index.rst b/docs/configguide/index.rst index 75c925b..31f296d 100644 --- a/docs/configguide/index.rst +++ b/docs/configguide/index.rst @@ -10,9 +10,9 @@ This section provides instructions to install OPNFV on IPv6-only Infrastructure. and API endpoints will be IPv6-only except: 1. "admin" network in underlay/undercloud still has to be IPv4, due to lack of support of IPMI - over IPv6 or PXE over IPv6. + over IPv6 or PXE over IPv6. 2. OVS VxLAN (or GRE) tunnel endpoint is still IPv4 only, although IPv6 traffic can be - encapsulated within the tunnel. + encapsulated within the tunnel. 3. Metadata server is still IPv4 only. Except the limitations above, the use case scenario of the IPv6-only infrastructure includes: @@ -21,9 +21,9 @@ Except the limitations above, the use case scenario of the IPv6-only infrastruct 2. Horizon/ODL-DLUX access using IPv6 address from an external host. 3. OpenStack API access using IPv6 addresses from various python-clients. 4. Ability to create Neutron Routers, IPv6 subnets (e.g. SLAAC/DHCPv6-Stateful/ - DHCPv6-Stateless) to support North-South traffic. + DHCPv6-Stateless) to support North-South traffic. 5. Inter VM communication (East-West traffic) when one of the VM is on Controller node - and the other on the Compute node. + and the other on the Compute node. 6. VNC access into a VM using IPv6 addresses. ------------------------------------------- |