Alpine containers have been introduced in Euphrates.
Alpine allows Functest testing in several very light containers and thanks to
the refactoring on dependency management should allow the creation of light and
-fully customized docker files.
+fully customized docker images.
-It is still possible to use the monolithic functest opnfv/functest especially
-for tests on Aarch64 architecture.
Functest Dockers
----------------
-Docker files are available on the dockerhub:
+Docker images are available on the dockerhub:
* opnfv/functest-core
* opnfv/functest-healthcheck
* opnfv/functest-parser
* opnfv/functest-restapi
-By default, we use the docker tag latest, but you may pull a tagged docker
-image.
+The tag "opnfv-5.0.0" is the official release image in Euphrates, but you can also pull "euphrates"
+tag as it is being maintained by Functest team and might include bugfixes.
The Functest docker container environment can -in principle- be also
used with non-OPNFV official installers (e.g. 'devstack'), with the
See section on OpenStack credentials for details.
-Create a directory for the different images (included as volume)::
+Create a directory for the different images (attached as a Docker volume)::
- mkdir -p images && wget -q -O- https://git.opnfv.org/functest/plain/functest/ci/download_images.sh | bash -s -- images && ls -1 images/*
+ mkdir -p images && wget -q -O- https://git.opnfv.org/functest/plain/functest/ci/download_images.sh?h=stable/euphrates | bash -s -- images && ls -1 images/*
images/CentOS-7-aarch64-GenericCloud.qcow2
images/CentOS-7-aarch64-GenericCloud.qcow2.xz
| api_check | functest | healthcheck | 04:57 | PASS |
| snaps_health_check | functest | healthcheck | 00:51 | PASS |
+----------------------------+------------------+---------------------+------------------+----------------+
+ NOTE: the duration is a reference and it might vary depending on your SUT.
Testing smoke suite
-------------------
+-------------------------------+------------------+--------------------+------------------+----------------+
| tempest_full_parallel | functest | components | 102:48 | PASS |
| rally_full | functest | components | 160:58 | PASS |
- | tempest_custom | functest | components | 00:00 | SKIP |
+-------------------------------+------------------+--------------------+------------------+----------------+
Testing vnf suite
| cloudify_ims | functest | vnf | 21:25 | PASS |
| orchestra_openims | functest | vnf | 11:02 | FAIL |
| orchestra_clearwaterims | functest | vnf | 09:13 | FAIL |
- | vyos_vrouter | functest | vnf | 00:00 | SKIP |
+---------------------------------+------------------+--------------+------------------+----------------+
=====================
Several environement variables may be specified:
- * INSTALLER_TYPE=(apex|compass|daisy|fuel|joid|osa)
+ * INSTALLER_TYPE=(apex|compass|daisy|fuel|joid)
* INSTALLER_IP=<Specific IP Address>
* DEPLOY_SCENARIO=<vim>-<controller>-<nfv_feature>-<ha_mode>
* ha_mode (high availability) is one of ( ha | noha )
If several features are pertinent then use the underscore character '_' to
-separate each feature (e.g. ovs_kvm) 'nofeature' indicates no OPNFV feature is
-deployed
+separate each feature (e.g. ovs_kvm). 'nofeature' indicates that no OPNFV
+feature is deployed.
The list of supported scenarios per release/installer is indicated in the
release note.
**NOTE:** The scenario name is mainly used to automatically detect
-if a test suite is runnable or not (e.g. it will prevent ONOS test suite to be
-run on ODL scenarios). If not set, Functest will try to run the default test
-cases that might not include SDN controller or a specific
-feature
+if a test suite is runnable or not (e.g. it will prevent ODL test suite to be
+run on 'nosdn' scenarios). If not set, Functest will try to run the default test
+cases that might not include SDN controller or a specific feature
-**NOTE:** A HA scenario means that 3 OpenStack controller nodes are
+**NOTE:** An HA scenario means that 3 OpenStack controller nodes are
deployed. It does not necessarily mean that the whole system is HA. See
installer release notes for details.
to the database. This option is only set when
tests are activated under Jenkins CI control.
It enables the correlation of test results,
- which
- are independently pushed to the results database
+ which are independently pushed to the results database
from different Jenkins jobs.
DO NOT USE THIS OPTION IN MANUAL TEST SCENARIOS.
* <DebugTraceValue> = "true" or "false"
your installer guide for further details. This is however not
instructed in this document.
-There is a default environment variable in the Functest container **$creds**
-that points to the credentials absolute path to help the user with this task.
-
In proxified environment you may need to change the credentials file.
There are some tips in chapter: `Proxy support`_
-v <path_to_your_cert_file>:/etc/ssl/certs/ca.cert
You might need to export OS_CACERT environment variable inside the
-container::
+credentials file::
export OS_CACERT=/etc/ssl/certs/ca.crt
src and repos directories are used to host third party code used for the tests.
-The functest code is under /usr/lib/python2.7/site-packages/functest
-The structure can be described as follows::
+The structure of functest repo can be described as follows::
|-- INFO
|-- LICENSE
| `-- apidoc
|-- build.sh
|-- commons
- | |-- docker
- | |-- Dockerfile
- | |-- Dockerfile.aarch64.patch
+ |-- docker
| |-- components
- | |-- config_install_env.sh
| |-- core
- | |-- docker_remote_api
| |-- features
| |-- healthcheck
| |-- smoke
| |-- vnf
- | `-- thirdparty-requirements.txt
+ | |-- parser
+ | |-- restapi
+ | |-- thirdparty-requirements.txt
|-- docs
| |-- com
| |-- images
| |-- urls.py
| |-- common
| | |-- api_utils.py
- | | `-- error.py
+ | | |-- thread.py
| `-- resources
| `-- v1
| |-- creds.py
| |-- envs.py
| |-- testcases.py
- | `-- tiers.py
+ | |-- tiers.py
+ | |-- tasks.py
+ | `-- database
+ | |-- db.py
+ | `-- v1
+ | |-- handlers.py
+ | |-- models.py
+ | `-- swagger
|-- ci
│ |-- check_deployment.py
│ |-- config_aarch64_patch.yaml
│ |-- config_functest.yaml
│ |-- config_patch.yaml
│ |-- download_images.sh
- │ |-- installer_params.yaml
│ |-- logging.ini
│ |-- prepare_env.py
│ |-- rally_aarch64_patch.conf
│ |-- run_tests.py
│ |-- testcases.yaml
│ |-- tier_builder.py
- │ `-- tier_handler.py
+ │ |-- tier_handler.py
|-- cli
│ |-- cli_base.py
│ |-- commands
│ │ |-- cli_env.py
│ │ |-- cli_os.py
│ │ |-- cli_testcase.py
- │ │ `-- cli_tier.py
+ │ │ |-- cli_tier.py
│ |-- functest-complete.sh
|-- core
│ |-- feature.py
│ |-- testcase.py
│ |-- unit.py
- │ `-- vnf.py
+ │ |-- vnf.py
|-- energy
│ |-- energy.py
- │ `-- energy.pyc
|-- opnfv_tests
- │ |-- mano
- │ │ |-- orchestra.py
- │ |-- openstack
- │ │ |-- rally
- │ │ |-- refstack_client
- │ │ |-- snaps
- │ │ |-- tempest
- │ │ `-- vping
- │ |-- sdn
+ │ `-- openstack
+ │ |-- rally
+ │ |-- refstack_client
+ │ |-- snaps
+ │ |-- tempest
+ │ |-- vping
+ │ `-- sdn
│ │ `-- odl
│ `-- vnf
- │ |-- aaa
│ |-- ims
│ `-- router
|-- tests
We may distinguish several directories, the first level has 5 directories:
* **api**: This directory is dedicated to the API (framework) documentations.
-* **commons**: This directory is dedicated for storage of traffic
- profile or any other test inputs that could be reused by any test
- project.
+* **commons**: This directory is dedicated for storage of traffic profile or
+ any other test inputs that could be reused by any test project.
* **docker**: This directory includes the needed files and tools to
- build the Functest Docker image.
+ build the Functest Docker images.
* **docs**: This directory includes documentation: Release Notes,
User Guide, Configuration Guide and Developer Guide.
* **functest**: This directory contains all the code needed to run
functest internal cases and OPNFV onboarded feature or VNF test cases.
-Functest directory has 7 sub-directories:
- * **api**: This directory is dedicated for the internal Functest API and the
- API (framework) documentations.
+Functest directory has 7 sub-directories, which is located under
+/usr/lib/python2.7/site-packages/functest:
+ * **api**: This directory is dedicated for the internal Functest API.
* **ci**: This directory contains test structure definition files
(e.g <filename>.yaml) and bash shell/python scripts used to
configure and execute Functional tests. The test execution script
the integration of internal, feature or vnf cases.
* **opnfv_tests**: This directory includes the scripts required by
Functest internal test cases and other feature projects test cases.
- * **tests**: This directory includes the functest unit tests
+ * **tests**: This directory includes the functest unit tests.
* **utils**: this directory holds Python source code for some general
purpose helper utilities, which testers can also re-use in their
own test code. See for an example the Openstack helper utility:
.. _`[4]`: http://docs.opnfv.org/en/latest/submodules/functest/docs/testing/user/configguide/index.html
.. _`dockerdocs`: https://docs.docker.com/
-.. _`dockerhub`: https://hub.docker.com/r/opnfv/functest/
.. _`Proxy`: https://docs.docker.com/engine/admin/systemd/#http-proxy
-.. _`FunctestDockerTags`: https://hub.docker.com/r/opnfv/functest/tags/
.. _`Install Docker on CentOS`: https://docs.docker.com/engine/installation/linux/centos/
.. _`Functest User Guide`: http://docs.opnfv.org/en/stable-danube/submodules/functest/docs/testing/user/userguide/index.html
.. _`images/CentOS-7-x86_64-GenericCloud.qcow2` http://download.cirros-cloud.net/0.3.5/cirros-0.3.5-x86_64-disk.img
Code Review / functest-xtesting.git / blobdiff