summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBin Hu <bh526r@att.com>2017-03-01 14:35:15 -0800
committerBin Hu <bh526r@att.com>2017-03-01 14:35:15 -0800
commit0fd2a85cb0a036f960c63e059a8540972be806a5 (patch)
tree77db55cc98d8cfaf3fa0deedb79adefcf3ff6dc6
parente98330d85aa681054cc9a509d0f7a907475b781c (diff)
Update testing section in Installation Guide
Change-Id: I271e08dcfd07f6e6b210d39d04c8307d39d8f59d Signed-off-by: Bin Hu <bh526r@att.com>
-rw-r--r--docs/release/installation/installation.instruction.rst21
1 files changed, 16 insertions, 5 deletions
diff --git a/docs/release/installation/installation.instruction.rst b/docs/release/installation/installation.instruction.rst
index f78b1c7..3736826 100644
--- a/docs/release/installation/installation.instruction.rst
+++ b/docs/release/installation/installation.instruction.rst
@@ -120,11 +120,22 @@ Underlay Testing
**Underlay** Testing is to validate that API endpoints are listening on IPv6 addresses.
This can be as simple as validating Keystone service, and as complete as validating each
-API endpoint. It is important to reuse Tempest API testing.
-
-Please **Note** that, to the best of our knowledge, Tempest API testing does not validate
-API endpoints listening on IPv6 addresses. Thus Underlay Testing is postponed to future
-release until Tempest API testing is ready to validate API endpoints listening on IPv6 addresses.
+API endpoint. It is important to reuse Tempest API testing. Currently:
+
+* Apex Installer will change ``OS_AUTH_URL`` in ``overcloudrc`` during installation
+ process. For example: ``export OS_AUTH_URL=http://[2001:db8::15]:5000/v2.0``.
+ ``OS_AUTH_URL`` points to Keystone and Keystone catalog.
+* When FuncTest runs Tempest for the first time, the ``OS_AUTH_URL`` is taken
+ from the environment and placed automatically in ``Tempest.conf``.
+* Under this circumstance, ``openstack catalog list`` will return IPv6 URL
+ endpoints for all the services in catalog, including Nova, Neutron, etc,
+ and covering public URLs, private URLs and admin URLs.
+* Thus, as long as the IPv6 URL is given in the ``overclourc``, all the tests
+ will use that (including Tempest).
+
+Therefore Tempest API testing is reused to validate API endpoints are listening
+on IPv6 addresses as stated above. They are part of OpenStack default Smoke
+Tests, run in FuncTest and integrated into OPNFV's CI/CD environment.
+++++++++++++++
Overlay Testing