summaryrefslogtreecommitdiffstats
path: root/docs/development/overview
diff options
context:
space:
mode:
authorTomi Juvonen <tomi.juvonen@nokia.com>2019-03-27 10:10:53 +0200
committerTomi Juvonen <tomi.juvonen@nokia.com>2019-03-29 08:00:31 +0200
commit2eb1c7f3fbd2a4bf6468f63e64ea3c1496236fe5 (patch)
tree0aa9c365b00e0a08c5c6cd72f98791dbcd6b82fd /docs/development/overview
parent73605c5c34b97ab56306bfa9af0f5888f3c7e46d (diff)
Hunter release documentation
Release note and minor document fixes for Fenix support Change-Id: If3e81992dc7ed203223291ecd9c96eb76257b053 Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
Diffstat (limited to 'docs/development/overview')
-rw-r--r--docs/development/overview/functest_scenario/doctor-scenario-in-functest.rst10
-rw-r--r--docs/development/overview/testing.rst3
2 files changed, 8 insertions, 5 deletions
diff --git a/docs/development/overview/functest_scenario/doctor-scenario-in-functest.rst b/docs/development/overview/functest_scenario/doctor-scenario-in-functest.rst
index 9f92b5bf..4505dd8f 100644
--- a/docs/development/overview/functest_scenario/doctor-scenario-in-functest.rst
+++ b/docs/development/overview/functest_scenario/doctor-scenario-in-functest.rst
@@ -59,7 +59,7 @@ Doctor testing can also be triggered by tox on OPNFV installer jumphost. Tox
is normally used for functional, module and coding style testing in Python
project.
-Currently, 'Apex', 'Daisy', 'Fuel' and 'local' installer are supported.
+Currently, 'Apex', 'MCP' and 'local' installer are supported.
Fault management use case
@@ -172,9 +172,11 @@ Maintenance test case
Maintenance test case is currently running in our Apex CI and executed by tox.
This is because the special limitation mentioned below and also the fact we
-currently have only sample implementation as a proof of concept. Environmental
-variable TEST_CASE='maintenance' needs to be used when executing
-"doctor_tests/main.py". Test case workflow can be seen in :numref:`figure-p3`.
+currently have only sample implementation as a proof of concept and we also
+support unofficial OpenStack project Fenix. Environment variable
+TEST_CASE='maintenance' needs to be used when executing "doctor_tests/main.py"
+and ADMIN_TOOL_TYPE='fenix' if want to test with Fenix instead of sample
+implementation. Test case workflow can be seen in :numref:`figure-p3`.
.. figure:: ./images/Maintenance-workflow.png
:name: figure-p3
diff --git a/docs/development/overview/testing.rst b/docs/development/overview/testing.rst
index a4b9ffa6..663d4c3f 100644
--- a/docs/development/overview/testing.rst
+++ b/docs/development/overview/testing.rst
@@ -38,6 +38,8 @@ export TEST_CASE with different values:
export TEST_CASE='fault_management'
#Maintenance (requires 3 compute nodes)
export TEST_CASE='maintenance'
+ #Use Fenix in maintenance testing instead of sample admin_tool
+ export ADMIN_TOOL_TYPE='fenix'
#Run both tests cases
export TEST_CASE='all'
@@ -61,7 +63,6 @@ In OPNFV Apex jumphost you can run Doctor testing as follows using tox:
.. code-block:: bash
- #Before Gambia: overcloudrc.v3
source overcloudrc
export INSTALLER_IP=${INSTALLER_IP}
export INSTALLER_TYPE=${INSTALLER_TYPE}