diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/conf.py | 2 | ||||
| -rw-r--r-- | docs/release/release-notes/functest-release.rst | 2 | ||||
| -rw-r--r-- | docs/spelling_wordlist.txt | 147 | ||||
| -rw-r--r-- | docs/testing/user/configguide/configguide.rst | 6 | ||||
| -rw-r--r-- | docs/testing/user/configguide/prerequisites.rst | 2 | ||||
| -rw-r--r-- | docs/testing/user/userguide/reporting.rst | 4 | ||||
| -rw-r--r-- | docs/testing/user/userguide/test_overview.rst | 6 | ||||
| -rw-r--r-- | docs/testing/user/userguide/troubleshooting.rst | 6 |
8 files changed, 162 insertions, 13 deletions
diff --git a/docs/conf.py b/docs/conf.py index 2be6a5ab7..7a8d1858d 100644 --- a/docs/conf.py +++ b/docs/conf.py @@ -175,3 +175,5 @@ texinfo_documents = [ 'One line description of project.', 'Miscellaneous'), ] + +spelling_word_list_filename = 'spelling_wordlist.txt' diff --git a/docs/release/release-notes/functest-release.rst b/docs/release/release-notes/functest-release.rst index 9d4f896a6..14b271ab4 100644 --- a/docs/release/release-notes/functest-release.rst +++ b/docs/release/release-notes/functest-release.rst @@ -99,7 +99,7 @@ Docker tag for jerma: jerma Documents --------- - * Functests Guides: https://functest.readthedocs.io/en/stable-jerma/ + * Functest Guides: https://functest.readthedocs.io/en/stable-jerma/ * API Docs: https://functest-api.readthedocs.io/en/stable-jerma/ Version change diff --git a/docs/spelling_wordlist.txt b/docs/spelling_wordlist.txt new file mode 100644 index 000000000..d9e3c1811 --- /dev/null +++ b/docs/spelling_wordlist.txt @@ -0,0 +1,147 @@ +ABot +admin +adminURL +api +auth +backend +barbican +benchmarking +Benchmarking +bgpvpn +cacerts +chan +ci +Clearwater +cloudify +Cloudify +conf +config +dashboarding +defcore +Defcore +Deliverables +dhcp +dockerhub +enduser +env +EnvironmentVariable +epc +fds +frontend +functest +Functest +guestbook +Guestbook +healthcheck +Healthcheck +http +https +ims +ini +init +interop +Interop +interoperability +intra +iptables +jenkins +jerma +Jerma +Joid +juju +Juju +jumphost +Jumphost +kube +kubernetes +Kubernetes +kvm +linux +metadata +Metadata +middleware +nfv +nofeature +noha +nosdn +octavia +odl +onboarding +ons +Opendaylight +openstack +Openstack +opnfv +orchestrator +Orchestrator +organised +os +ovs +patrole +Patrole +plugin +pre +proxified +Reachability +reconnection +redis +refactored +refstack +Refstack +repo +resolv +restapi +Restconf +runnable +screenshot +sdn +sfc +signalling +singlevm +src +su +subfolder +subnet +Subnet +subnets +sudo +systemctl +Telco +tenantnetwork +testcase +testcases +TLS +txt +un +url +userdata +userid +username +usr +util +utils +UUID +vdb +vEPC +verifier +versioned +vIMS +Virtualised +Virtualized +vm +VM +vmready +vmtp +vnf +Vnf +vping +vPing +vrouter +vRouter +vyos +wconsole +wiki +Workflow +xrally +xtesting +yaml diff --git a/docs/testing/user/configguide/configguide.rst b/docs/testing/user/configguide/configguide.rst index 98ae8fe33..074c2b9d3 100644 --- a/docs/testing/user/configguide/configguide.rst +++ b/docs/testing/user/configguide/configguide.rst @@ -177,8 +177,8 @@ Functest Dockers for Kubernetes deployment Docker images are available on the dockerhub: * opnfv/functest-kubernetes-core - * opnfv/functest-kubernetest-healthcheck - * opnfv/functest-kubernetest-smoke + * opnfv/functest-kubernetes-healthcheck + * opnfv/functest-kubernetes-smoke Preparing your environment ^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -228,7 +228,7 @@ Results shall be displayed as follows:: Environment variables ===================== -Several environement variables may be specified: +Several environment variables may be specified: * INSTALLER_IP=<Specific IP Address> * DEPLOY_SCENARIO=<vim>-<controller>-<nfv_feature>-<ha_mode> diff --git a/docs/testing/user/configguide/prerequisites.rst b/docs/testing/user/configguide/prerequisites.rst index c7b52dc54..dab4a9e6b 100644 --- a/docs/testing/user/configguide/prerequisites.rst +++ b/docs/testing/user/configguide/prerequisites.rst @@ -92,4 +92,4 @@ should thus be known. Ensure you can reach each node in the SUT, from the Jumphost using the 'ping' command using the respective IP address on the public/external network for each node in the SUT. The details of how to determine the needed IP addresses for each node in the SUT may vary according -to the used installer and are therefore ommitted here. +to the used installer and are therefore omitted here. diff --git a/docs/testing/user/userguide/reporting.rst b/docs/testing/user/userguide/reporting.rst index 7c8c48ece..8fad55d33 100644 --- a/docs/testing/user/userguide/reporting.rst +++ b/docs/testing/user/userguide/reporting.rst @@ -48,7 +48,7 @@ and features) corresponding to this scenario. All the testcases (X) listed in the table are runnable on os-odl_l2-nofeature scenarios. Please note that other test cases (e.g. sfc_odl, bgpvpn) need ODL configuration -addons and, as a consequence, specific scenario. +add-ons and, as a consequence, specific scenario. There are not considered as runnable on the generic odl_l2 scenario. @@ -82,7 +82,7 @@ Therefore the scoring provides 3 types of indicators: * the maturity: if the percentage (scoring/target scoring * 100) is high, it means that all the tests are PASS * the stability: as the number of iteration is included in the calculation, - the pecentage can be high only if the scenario is run regularly (at least + the percentage can be high only if the scenario is run regularly (at least more than 4 iterations over the last 10 days in CI) In any case, the scoring is used to give feedback to the other projects and diff --git a/docs/testing/user/userguide/test_overview.rst b/docs/testing/user/userguide/test_overview.rst index 5aef27c1c..bc3e79dcb 100644 --- a/docs/testing/user/userguide/test_overview.rst +++ b/docs/testing/user/userguide/test_overview.rst @@ -17,7 +17,7 @@ The current list of test suites can be distributed over 5 main domains: Functest test suites are also distributed in the OPNFV testing categories: healthcheck, smoke, benchmarking, VNF, Stress tests. -All the Healthcheck and smoke tests of a given scenario must be succesful to +All the Healthcheck and smoke tests of a given scenario must be successful to validate the scenario for the release. +-------------+---------------+------------+----------------------------------+ @@ -90,7 +90,7 @@ validate the scenario for the release. | VNF | vnf | cloudify | Example of a real VNF deployment | | | | \_ims | to show the NFV capabilities of | | | | | the platform. The IP Multimedia | -| | | | Subsytem is a typical Telco test | +| | | | Subsystem is a typical Telco test| | | | | case, referenced by ETSI. | | | | | It provides a fully functional | | | | | VoIP System | @@ -177,7 +177,7 @@ deployed services. The system uses the environment variables to automatically determine the valid test cases, for each given environment. A convenience Functest CLI utility is also available to simplify setting up the -Functest evironment, management of the OpenStack environment (e.g. resource +Functest environment, management of the OpenStack environment (e.g. resource clean-up) and for executing tests. The Functest CLI organised the testcase into logical Tiers, which contain in turn one or more testcases. The CLI allows execution of a single specified diff --git a/docs/testing/user/userguide/troubleshooting.rst b/docs/testing/user/userguide/troubleshooting.rst index fb534376d..66e2433f6 100644 --- a/docs/testing/user/userguide/troubleshooting.rst +++ b/docs/testing/user/userguide/troubleshooting.rst @@ -133,8 +133,8 @@ here:: vPing_ssh- ERROR - Cannot establish connection to IP xxx.xxx.xxx.xxx. Aborting If this is displayed, stop the test or wait for it to finish, if you have used -the special method of test invocation with specific supression of OpenStack -resource clean-up, as explained earler. It means that the Container can not +the special method of test invocation with specific suppression of OpenStack +resource clean-up, as explained earlier. It means that the Container can not reach the Public/External IP assigned to the instance **opnfv-vping-2**. There are many possible reasons, and they really depend on the chosen scenario. For most of the ODL-L3 and ONOS scenarios this has been noticed and it is a known @@ -158,7 +158,7 @@ container:: ping <public IP> If the ping does not return anything, try to ping from the Host where the -Docker container is running. If that solves the problem, check the iptable +Docker container is running. If that solves the problem, check the iptables rules because there might be some rules rejecting ICMP or TCP traffic coming/going from/to the container. |