diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/configurationguide/featureconfig.rst | 5 | ||||
| -rw-r--r-- | docs/configurationguide/index.rst | 4 | ||||
| -rw-r--r-- | docs/installationprocedure/index.rst | 27 | ||||
| -rw-r--r-- | docs/installationprocedure/scenario.installation.instruction.rst | 27 |
4 files changed, 53 insertions, 10 deletions
diff --git a/docs/configurationguide/featureconfig.rst b/docs/configurationguide/featureconfig.rst index 87616ce..6d06325 100644 --- a/docs/configurationguide/featureconfig.rst +++ b/docs/configurationguide/featureconfig.rst @@ -436,6 +436,10 @@ Setup Manual in OpenStack with Open Daylight L2-Only Environment If you intend to set up a service VM as an IPv6 vRouter in an environment of OpenStack and Open Daylight L2-only of OPNFV Colorado Release, please **NOTE** that: +* We **SHOULD** use the ``odl-ovsdb-openstack`` version of Open Daylight Boron + in OPNFV Colorado Release. Please refer to our + `Gap Analysis <http://artifacts.opnfv.org/ipv6/docs/gapanalysis/gap-analysis-odl-boron.html>`_ + for more information. * The hostnames, IP addresses, and username are for exemplary purpose in instructions. Please change as needed to fit your environment. * The instructions apply to both deployment model of single controller node and @@ -1015,3 +1019,4 @@ Run some commands to verify that IPv6 addresses are configured on ``eth0`` inter If the above ping6 command succeeds, it implies that ``vRouter`` was able to successfully forward the IPv6 traffic to reach external ``ipv6-router``. + diff --git a/docs/configurationguide/index.rst b/docs/configurationguide/index.rst index 47ea3fe..67f616f 100644 --- a/docs/configurationguide/index.rst +++ b/docs/configurationguide/index.rst @@ -436,6 +436,10 @@ Setup Manual in OpenStack with Open Daylight L2-Only Environment If you intend to set up a service VM as an IPv6 vRouter in an environment of OpenStack and Open Daylight L2-only of OPNFV Colorado Release, please **NOTE** that: +* We **SHOULD** use the ``odl-ovsdb-openstack`` version of Open Daylight Boron + in OPNFV Colorado Release. Please refer to our + `Gap Analysis <http://artifacts.opnfv.org/ipv6/docs/gapanalysis/gap-analysis-odl-boron.html>`_ + for more information. * The hostnames, IP addresses, and username are for exemplary purpose in instructions. Please change as needed to fit your environment. * The instructions apply to both deployment model of single controller node and diff --git a/docs/installationprocedure/index.rst b/docs/installationprocedure/index.rst index 31f296d..166880a 100644 --- a/docs/installationprocedure/index.rst +++ b/docs/installationprocedure/index.rst @@ -22,8 +22,8 @@ Except the limitations above, the use case scenario of the IPv6-only infrastruct 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. -5. Inter VM communication (East-West traffic) when one of the VM is on Controller node - and the other on the Compute node. +5. Inter VM communication (East-West routing) when VMs are spread + across two compute nodes. 6. VNC access into a VM using IPv6 addresses. ------------------------------------------- @@ -151,7 +151,9 @@ Overlay Testing +++++++++++++++ **Overlay** Testing is to validate that IPv6 is supported in tenant networks, subnets and routers. -Tempest Scenario testing covers the following overlay IPv6 scenarios: +Both Tempest API testing and Tempest Scenario testing are used in our Overlay Testing. + +Tempest API testing validates that the Neutron API supports the creation of IPv6 networks, subnets, routers, etc: .. code-block:: bash @@ -183,6 +185,21 @@ Tempest Scenario testing covers the following overlay IPv6 scenarios: tempest.api.network.test_security_groups.SecGroupIPv6Test.test_create_show_delete_security_group_rule tempest.api.network.test_security_groups.SecGroupIPv6Test.test_list_security_groups -The above scenarios are quite comprehensive to validate IPv6 tenant networks. We are using above -Tempest Scenario testing as Smoke Test in FuncTest, which is integrated into OPNFV's CI/CD environment. +Tempest Scenario testing validates some specific overlay IPv6 scenarios +(i.e. use cases) as follows: + +.. code-block:: bash + + tempest.scenario.test_network_v6.TestGettingAddress.test_dhcp6_stateless_from_os + tempest.scenario.test_network_v6.TestGettingAddress.test_dualnet_dhcp6_stateless_from_os + tempest.scenario.test_network_v6.TestGettingAddress.test_dualnet_multi_prefix_dhcpv6_stateless + tempest.scenario.test_network_v6.TestGettingAddress.test_dualnet_multi_prefix_slaac + tempest.scenario.test_network_v6.TestGettingAddress.test_dualnet_slaac_from_os + tempest.scenario.test_network_v6.TestGettingAddress.test_multi_prefix_dhcpv6_stateless + tempest.scenario.test_network_v6.TestGettingAddress.test_multi_prefix_slaac + tempest.scenario.test_network_v6.TestGettingAddress.test_slaac_from_os + +The above Tempest API testing and Scenario testing are quite comprehensive to validate +overlay IPv6 tenant networks. They are used in Smoke Test in FuncTest, which is integrated +into OPNFV's CI/CD environment. diff --git a/docs/installationprocedure/scenario.installation.instruction.rst b/docs/installationprocedure/scenario.installation.instruction.rst index 31f296d..166880a 100644 --- a/docs/installationprocedure/scenario.installation.instruction.rst +++ b/docs/installationprocedure/scenario.installation.instruction.rst @@ -22,8 +22,8 @@ Except the limitations above, the use case scenario of the IPv6-only infrastruct 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. -5. Inter VM communication (East-West traffic) when one of the VM is on Controller node - and the other on the Compute node. +5. Inter VM communication (East-West routing) when VMs are spread + across two compute nodes. 6. VNC access into a VM using IPv6 addresses. ------------------------------------------- @@ -151,7 +151,9 @@ Overlay Testing +++++++++++++++ **Overlay** Testing is to validate that IPv6 is supported in tenant networks, subnets and routers. -Tempest Scenario testing covers the following overlay IPv6 scenarios: +Both Tempest API testing and Tempest Scenario testing are used in our Overlay Testing. + +Tempest API testing validates that the Neutron API supports the creation of IPv6 networks, subnets, routers, etc: .. code-block:: bash @@ -183,6 +185,21 @@ Tempest Scenario testing covers the following overlay IPv6 scenarios: tempest.api.network.test_security_groups.SecGroupIPv6Test.test_create_show_delete_security_group_rule tempest.api.network.test_security_groups.SecGroupIPv6Test.test_list_security_groups -The above scenarios are quite comprehensive to validate IPv6 tenant networks. We are using above -Tempest Scenario testing as Smoke Test in FuncTest, which is integrated into OPNFV's CI/CD environment. +Tempest Scenario testing validates some specific overlay IPv6 scenarios +(i.e. use cases) as follows: + +.. code-block:: bash + + tempest.scenario.test_network_v6.TestGettingAddress.test_dhcp6_stateless_from_os + tempest.scenario.test_network_v6.TestGettingAddress.test_dualnet_dhcp6_stateless_from_os + tempest.scenario.test_network_v6.TestGettingAddress.test_dualnet_multi_prefix_dhcpv6_stateless + tempest.scenario.test_network_v6.TestGettingAddress.test_dualnet_multi_prefix_slaac + tempest.scenario.test_network_v6.TestGettingAddress.test_dualnet_slaac_from_os + tempest.scenario.test_network_v6.TestGettingAddress.test_multi_prefix_dhcpv6_stateless + tempest.scenario.test_network_v6.TestGettingAddress.test_multi_prefix_slaac + tempest.scenario.test_network_v6.TestGettingAddress.test_slaac_from_os + +The above Tempest API testing and Scenario testing are quite comprehensive to validate +overlay IPv6 tenant networks. They are used in Smoke Test in FuncTest, which is integrated +into OPNFV's CI/CD environment. |