1 ===========================
2 OPNFV functional test guide
3 ===========================
11 Testing is a key challenge of OPNFV.
12 It shall be possible to run functional tests on any OPNFV solution.
14 The goal of this document consists in
15 * a description of functional tests for OPNFV
16 * a description of the tools needed to perform these tests
17 * the procedure to configure the tools and the scenarios associated with these tests
19 Functional tests shall be automated (as much as possible) and collected results shall be used to improve the robustness and the reliability of the overall system.
21 Function tests may cover any domain that could lead to improve the OPNFV solution and define "Telco Cloud" KPI.
23 The last section also describes how to automate these tests within the OPNFV continuous integration project.
25 .. _ETSI: http://docbox.etsi.org/ISG/NFV/Open/Published/gs_NFV001v010101p%20-%20Use%20Cases.pdf
27 ETSI NFV defined 9 use cases (ref ETSI_):
30 * VNF Forwarding graphs
31 * Virtual Network Platform as a Service
32 * Virtualisation of Mobile Core and IMS
33 * Virtualisation of Mobile station
35 * Virtualization of CDNs (vCDN)
36 * Virtualization of the Home environment
38 .. _`Openstack Telco Working Group`: https://wiki.openstack.org/wiki/TelcoWorkingGroup
39 .. _`functest guide`: https://wiki.opnfv.org/_media/opnfv-_functest.pdf
42 Most of the use cases are also discussed in upstream projects (e.g. `Openstack Telco Working Group`_ )
44 For release 1 (Arno), 4 test suites have been selected:
45 * Rally Bench test suite for Openstack
46 * Openstack Tempest test suite
47 * OpenDaylight test suite
50 The 3 first suites are directly inherited from upstream projects.
51 vPing, that is already present in Tempest suite, has been developped to provided a basic "hello world" functional test example.
53 .. _`Continuous Integration`: https://build.opnfv.org/ci/view/functest/
55 vIMS, vEPC, vPE, vHGW, vCDN, vWhatever use cases are not considered for first release.
56 It does not mean that such use cases cannot be tested on OPNFV Arno.
57 It means that these testcases have not been integrated in the `Continuous Integration`_ and no specific work (integration or developpment) have been done for the first release.
58 We may expect that new VNFs and new scenarios will be created and integrated in the future releases. See `functest guide`_ for details.
65 We assume that an OPNFV Arno solution has been installed.
67 .. _here: https://wiki.opnfv.org/documentation/Arno
69 The installation of the OPNFV solution is out of scope of this document but can be found [here_].
70 In the rest of the document the OPNFV solution would be considered as the System Under Test (SUT).
72 The installation and configuration of the tools needed to perform the tests will be described in the following sections.
74 For Arno SR1, the tools are automatically installed. Manual sourcing of OpenStack credentials is no more required if you are fully integrated in the continuous integration.
75 A script has been added to automatically retrieve the credentials.
76 However, if you still install manually functest, you will need to source the rc file on the machine you are running the tests.
77 More details will be provided in the configuration section.
79 .. _pharos: https://wiki.opnfv.org/pharos
81 It is recommended to install the different tools on the jump host server as defined in the pharos_ project.
83 For functest, the following libraries are needed. You can install them either with yum install or apt-get install, depending on your operating system:
90 You will also need some Python modules:
91 * sudo pip install GitPython
92 * sudo pip install python-novaclient
93 * sudo pip install python-neutronclient
94 * sudo pip install python-glanceclient
95 * sudo pip install python-keystoneclient
98 The high level architecture can be described as follow::
100 CIMC/Lights+out management Admin Private Public Storage
106 | +-----------------+ | | + |
108 +-----+ Jumpserver | | | | |
109 | | +---------------------+ | | |
111 | | +----------+ | | | | |
112 | | | Rally | +---- --------------------------+ | |
114 | | | Robot | | | | | |
116 | | | vPing | | | | | |
118 | | | Tempest | | | | | |
119 | | +----------+ | | | | |
120 | | FuncTest +-----------------------------------------+ |
122 | | +--------------------------------------------------+
124 | +-----------------+ | | | |
126 | +----------------+ | | | |
128 +----+ +--------------+-+ | | | |
130 | | | +--------------+-+ | | | |
132 | | | | +--------------+-+ | | | |
133 | | | | | 4 | | | | |
134 | +-+ | | +--------------+-+ | | | |
135 | | | | | 5 +---------------+ | | |
136 | +-+ | | nodes for | | | | |
137 | | | | deploying +-------------------------+ | |
138 | +-+ | opnfv | | | | |
139 | | | SUT +-----------------------------------+ |
141 | | +--------------------------------------------+
142 | +----------------+ | | | |
148 -----------------------------
149 Description of the test cases
150 -----------------------------
155 The goal of this test can be described as follow::
158 +-------------+ +-------------+
162 | +------------------>| |
165 | +------------------>| |
166 | Tester | | System |
167 | | Boot VM2 | Under |
168 | +------------------>| Test |
169 | | VM2 pings VM1 | |
171 | | Check console log | |
174 | | else (timeout) | |
178 +-------------+ +-------------+
181 This example, using OpenStack Python clients can be considered as an "Hello World" example and may be modified for future use.
183 In SR1, some code has been added in order to push the results (status and duration) into a centralized test result database.
188 The ODL suite consists in a set of basic tests inherited from ODL project. The suite tests the creation and deletion of network, subnet, port though OpenDaylight and Neutron.
190 The list of tests can be described as follow:
191 * Restconf.basic: Get the controller modules via Restconf
194 * Check OpenStack Networks :: Checking OpenStack Neutron for known networks
195 * Check OpenDaylight Networks :: Checking OpenDaylight Neutron API
196 * Create Network :: Create new network in OpenStack
197 * Check Network :: Check Network created in OpenDaylight
198 * Neutron.Networks :: Checking Network created in OpenStack are pushed
202 * Check OpenStack Subnets :: Checking OpenStack Neutron for known Subnets
203 * Check OpenDaylight subnets :: Checking OpenDaylight Neutron API
204 * Create New subnet :: Create new subnet in OpenStack
205 * Check New subnet :: Check new subnet created in OpenDaylight
206 * Neutron.Subnets :: Checking Subnets created in OpenStack are pushed
210 * Check OpenStack ports :: Checking OpenStack Neutron for known ports
211 * Check OpenDaylight ports :: Checking OpenDaylight Neutron API
212 * Create New Port :: Create new port in OpenStack
213 * Check New Port :: Check new subnet created in OpenDaylight
214 * Neutron.Ports :: Checking Port created in OpenStack are pushed
218 * Delete previously created subnet in OpenStack
219 * Check subnet deleted in OpenDaylight
220 * Check subnet deleted in OpenStack
224 * Delete previously created network in OpenStack
225 * Check network deleted in OpenDaylight
226 * Check network deleted in OpenStack
231 Rally bench test suite
232 ======================
234 .. _Rally: https://wiki.openstack.org/wiki/Rally
236 Rally bench test suite consist in a suite of light performance tests on some of the OpenStack components.
238 The goal of this test suite is to test the different modules of OpenStack and get significant figures that could help us to define telco Cloud KPI.
240 The OPNFV scenarios are based on the collection of the existing Rally_ scenarios:
251 This test suite provides performance information on VIM (OpenStack) part.
253 No SLA were defined for release 1, we just consider whether the tests are passed or failed.
255 In the future SLA shall be defined (e.g. accepting booting time for a given image with a given flavour).
257 Through its integration in Continuous Integration, the evolution of the performance of these tests shall also be considered.
262 .. _Tempest: http://docs.openstack.org/developer/tempest/overview.html
264 Tempest_ is the OpenStack Integration Test Suite. We use Rally to run Tempest suite.
266 The Tempest.conf configuration file is automatically generated by Rally then the Tempest suite is run, each test duration is measured.
268 We considered the smoke test suite for Arno.
270 The goal of this test is to to check the basic OpenStack functionality on a fresh installation.
274 .. _tooling_installation:
276 ----------------------
278 ----------------------
280 .. _fetch_os_creds.sh: https://git.opnfv.org/cgit/releng/tree/utils/fetch_os_creds.sh
282 2 external tools are needed for the functional tests on Arno:
286 Rally is used for benchmarking and running Tempest. Robot is used for running OpenDaylight test suites.
288 A script (config_test.py) has been created to simplify as much as possible the installation of the different suites of tests.
290 This script config_test.py_ is hosted in OPNFV repository and uses the configuration file config_functest.yaml_::
292 usage: config_functest.py [-h] [-d] [-f] path action
294 positional arguments:
295 repo_path path to the repository
296 action Possible actions are: 'start|check|clean'
299 -h, --help show this help message and exit
300 -d, --debug Debug mode
301 -f, --force used to avoid prompting the user for confirmation when cleaning functest environment.
304 * start: will prepare the functional testing environment
305 * check: will check the configuration (scenarios available, environment variables properly set, networks,..)
306 * clean: will clean the functional test environement if existing
309 * Install Rally environment
310 * Install Robot environment
312 * Retrieve test scenarios
313 * Create temporary neutron private network (if needed)
314 * Create Glance images
317 When integrated in CI, there are no additional prerequisites.
318 When running functest manually, the only prerequisite consists in retrieving the OpenStack credentials (rc file).
319 This file shall be saved on the jumphost. It must be sourced by the user (who shall have sudo rights) executing the tests.
321 For the Continuous Integration we store this file under $HOME/functest/opnfv-openrc.sh on the jumphost server so CI can automatically execute the suite of tests
323 The procedure to set up functional testing environment can be described as follow:
325 Log on the Jumphost server. Be sure you are no root then execute::
327 [user@jumphost]$ mkdir <Your_functest_directory>
328 [user@jumphost]$ cd <Your_functest_directory>
329 [user@jumphost]$ git clone https://git.opnfv.org/functest
330 [user@jumphost]$ cd testcases/
332 Modify and adapt needed parameters in the config_functest.yaml. Follow the instructions below.
334 Retrieve OpenStack source file (configure your `OpenRC`_ file to let Rally access to your OpenStack, you can either export it from Horizon or build it manually (OpenStack credentials are required)::
336 [user@jumphost]$ source Your_OpenRC_file
337 [user@jumphost]$ python <functest_repo_directory>/config_functest.py -d <Your_functest_directory> start
339 In SR1, a script has been created: fetch_os_creds.sh_. This script retrieves automatically the credentials of your OpenStack solution. You may run it manually::
341 [user@jumphost]$ /home/jenkins-ci/functest/fetch_os_creds.sh -d <destination> -i <installer_type> -a <installer_ip>
344 * installer_type = fuel or foreman
345 * installer_ip the IP of your installer
346 * the destination shall be the full path including the file name.
350 [user@jumphost]$./fetch_os_creds.sh -d ./credentials -i foreman -a 172.30.10.73
351 [user@jumphost]$./fetch_os_creds.sh -d ./credentials -i fuel -a 10.20.0.2
354 At the end of the git clone, the tree of <functest_repo_directory> will have the following structure::
359 | |-- Ims_overview.png
363 |-- config_functest.py
364 |-- config_functest.yaml
365 |-- functest_utils.py
369 | | |-- create_venv.sh
370 | | |-- custom_tests/
373 | | | |-- distributions
375 | | | |-- feature-selector
381 | | |-- requirements.pip
382 | | |-- start_tests.sh
383 | | |-- test_list.txt
385 |-- functest_utils.py
390 | | | |-- run_rally.py
392 | | |-- opnfv-authenticate.json
393 | | |-- opnfv-cinder.json
394 | | |-- opnfv-glance.json
395 | | |-- opnfv-heat.json
396 | | |-- opnfv-keystone.json
397 | | |-- opnfv-neutron.json
398 | | |-- opnfv-nova.json
399 | | |-- opnfv-quotas.json
400 | | |-- opnfv-requests.json
401 | | |-- opnfv-smoke-green.json
402 | | |-- opnfv-smoke.json
403 | | |-- opnfv-tempest.json
404 | | |-- opnfv-vm.json
412 NOTE: the Rally environment will be installed under ~/.rally/ the default Tempest configuration (automatically generated by Rally based on OpenStack credentials) can be found under .rally/tempest/for-deployment-<deployment_id>/tempest.conf
415 Configuration of config_functest.yaml
416 =====================================
418 Do not change the directories structure:
420 * image_name: name of the image that will be created in Glance
421 * image_url: URL of the image to be downloaded
422 * image_disk_format: glance image disk format (raw, qcow2, ...)
424 * neutron_private_net_name: name of an OpenStack private network. If not existing, it will be created
425 * neutron_private_subnet_name: private subnet network to be created if not existing
426 * neutron_private_subnet_cidr: range of the private subnet.
427 * neutron_private_subnet_start: start IP
428 * neutron_private_subnet_end: end IP
429 * neutron_router_name: name of the router between the private and the public networks
431 * ping_timeout: time out of the vPing test case
432 * vm_flavor: name of the flavor used to create the VMs
433 * vm_name_1: name of the first VM
434 * vm_name_2: name of the second VM
435 * ip_1: IP of the first VM (matching the private subnet cidr)
436 * ip_2: IP of the second VM
439 Please note that you need to install this environment only once.
440 As long as the credentials of the System Under Test do not change, there is no reason to modify the testing environment.
442 If you need more details on Rally installation, see `Rally installation procedure`_.
444 You can check if the configuration of rally is fine by typing 'rally deployment check', you shall see the list of available services as follow::
446 # rally deployment check
447 keystone endpoints are valid and following service are available:
448 +-------------+-----------+------------+
449 | Services | Type | Status |
450 +-----------+-------------+------------+
451 | cinder | volume | Available |
452 | cinderv2 | volumev2 | Available |
453 | glance | image | Available |
454 | keystone | identity | Available |
455 | neutron | network | Available |
456 | nova | compute | Available |
457 | nova_ec2 | compute_ec2 | Available |
458 | novav3 | computev3 | Available |
459 +-----------+-------------+------------+
462 +--------------------------------------+----------------------------------------------+------------+
463 | UUID | Name | Size (B) |
464 +--------------------------------------+----------------------------------------------+------------+
465 | 0a15951f-6388-4d5d-8531-79e7205eb140 | cirros_2015_04_10_13_13_18 | 13167616 |
466 | b1504066-045a-4f8f-8919-8c665ef3f400 | Ubuntu 14.04 64b | 253297152 |
467 +--------------------------------------+----------------------------------------------+------------+
470 +--------------------------------------+---------------------+-------+----------+-----------+-----------+
471 | ID | Name | vCPUs | RAM (MB) | Swap (MB) | Disk (GB) |
472 +--------------------------------------+---------------------+-------+----------+-----------+-----------+
473 | 110e6375-a058-4af6-b21e-b765187904d2 | m1.medium | 2 | 1024 | | 20 |
474 | 7084d7e7-415a-455d-a55a-2ad286ddf7c9 | m1.large | 4 | 4096 | | 80 |
475 | a0345ba7-c667-4fd2-964f-7e98f8cda279 | m1.xlarge | 4 | 8192 | | 200 |
476 | accdc28c-5e20-4859-a5cc-61cf9009e56d | m1.small | 1 | 512 | | 10 |
477 +--------------------------------------+---------------------+-------+----------+-----------+-----------+
479 # rally show networks
480 Networks for user `admin` in tenant `admin`:
481 +--------------------------------------+------------------------------+------+
482 | ID | Label | CIDR |
483 +--------------------------------------+------------------------------+------+
484 | 4f43c349-956f-4073-9ef6-75bf4e62a0e7 | functest-net | None |
485 | faefaab1-e503-41fc-875b-5e3112be49ed | provider_network | None |
486 +--------------------------------------+------------------------------+------+
496 You can run the vPing testcase by typing::
498 [user@jumphost]$ python <functest_repo_directory>/vPing/vPing.py -d <Your_functest_directory>
504 You can run ODL suite as follow::
506 [user@jumphost]$ python <functest_repo_directory>testcases/Controllers/ODL/CI/start_tests.sh
508 ODL wiki page describes system preparation and running tests. See `Integration Group CSIT`_.
510 .. _`Integration Group CSIT`: https://wiki.opendaylight.org/view/CrossProject:Integration_Group:CSIT
516 You can run the script as follow::
518 [user@jumphost]$ python <functest_repo_directory>/testcases/VIM/OpenStack/CI/libraries/run_rally.py <functest_repo_directory> <module_to_be_tested>
520 with <module_to_be_tested> set to:
532 * run rally with the selected scenario
533 * generate the html result page into <result_folder>/<timestamp>/opnfv-[module name].html
534 * generate the json result page into <result_folder>/<timestamp>/opnfv-[module name].json
535 * generate OK or NOK per test based on json result file
540 It is possible to use Rally to perform Tempest tests (ref: `tempest installation guide using Rally`_)
541 You just need to run::
543 # rally verify start smoke
545 The different modes available are smoke, baremetal, compute, data_processing, identity, image, network, object_storage, orchestration, telemetry, and volume. For Arno, it was decided to focus on smoke tests.
547 .. _`tempest installation guide using Rally`: https://www.mirantis.com/blog/rally-openstack-tempest-testing-made-simpler/
558 vPing result is displayed in the console::
561 2015-09-13 22:11:49,502 - vPing- INFO - Glance image found 'functest-img'
562 2015-09-13 22:11:49,502 - vPing- INFO - Creating neutron network functest-net...
563 2015-09-13 22:11:50,275 - vPing- INFO - Flavor found 'm1.small'
564 2015-09-13 22:11:50,318 - vPing- INFO - vPing Start Time:'2015-09-13 22:11:50'
565 2015-09-13 22:11:50,470 - vPing- INFO - Creating instance 'opnfv-vping-1' with IP 192.168.120.30...
566 2015-09-13 22:11:58,803 - vPing- INFO - Instance 'opnfv-vping-1' is ACTIVE.
567 2015-09-13 22:11:58,981 - vPing- INFO - Creating instance 'opnfv-vping-2' with IP 192.168.120.40...
568 2015-09-13 22:12:09,169 - vPing- INFO - Instance 'opnfv-vping-2' is ACTIVE.
569 2015-09-13 22:12:09,169 - vPing- INFO - Waiting for ping...
570 2015-09-13 22:13:11,329 - vPing- INFO - vPing detected!
571 2015-09-13 22:13:11,329 - vPing- INFO - vPing duration:'81.0'
572 2015-09-13 22:13:11,329 - vPing- INFO - Cleaning up...
573 2015-09-13 22:13:18,727 - vPing- INFO - Deleting network 'functest-net'...
574 015-09-13 22:13:19,470 - vPing- INFO - vPing OK
576 A json file is produced and pushed into the test result database.
580 .. _`functest wiki (ODL section)`: https://wiki.opnfv.org/r1_odl_suite
583 The results of ODL tests can be seen in the console::
585 ==============================================================================
587 ==============================================================================
588 Basic.010 Restconf OK :: Test suite to verify Restconf is OK
589 ==============================================================================
590 Get Controller Modules :: Get the controller modules via Restconf | PASS |
591 ------------------------------------------------------------------------------
592 Basic.010 Restconf OK :: Test suite to verify Restconf is OK | PASS |
593 1 critical test, 1 passed, 0 failed
594 1 test total, 1 passed, 0 failed
595 ==============================================================================
597 1 critical test, 1 passed, 0 failed
598 1 test total, 1 passed, 0 failed
599 ==============================================================================
600 Output: /home/jenkins-ci/workspace/functest-opnfv-jump-2/output.xml
601 Log: /home/jenkins-ci/workspace/functest-opnfv-jump-2/log.html
602 Report: /home/jenkins-ci/workspace/functest-opnfv-jump-2/report.html
604 ..............................................................................
606 Neutron.Delete Networks :: Checking Network deleted in OpenStack a... | FAIL |
607 2 critical tests, 1 passed, 1 failed
608 2 tests total, 1 passed, 1 failed
609 ==============================================================================
610 Neutron :: Test suite for Neutron Plugin | FAIL |
611 18 critical tests, 15 passed, 3 failed
612 18 tests total, 15 passed, 3 failed
613 ==============================================================================
614 Output: /home/jenkins-ci/workspace/functest-opnfv-jump-2/output.xml
615 Log: /home/jenkins-ci/workspace/functest-opnfv-jump-2/log.html
616 Report: /home/jenkins-ci/workspace/functest-opnfv-jump-2/report.html
618 3 result files are generated:
625 .. figure:: ./images/functestODL.png
628 :alt: ODL suite result page
634 Tests are expected to fail now:
635 * Check port deleted in OpenDaylight
636 * Check subnet deleted in OpenDaylight
637 * Check Network deleted in OpenDaylight
639 These failures to delete objects in OpenDaylight (when removed via OpenStack Neutron) are due to the following bug: https://bugs.opendaylight.org/show_bug.cgi?id=3052.
641 More details on `functest wiki (ODL section)`_
646 .. _`functest wiki (Rally section)`: https://wiki.opnfv.org/r1_rally_bench
648 Results are available in the result folder through a html page and a json file.
650 It generates a result page per module and can be described as follow.
652 .. figure:: ./images/functestRally2.png
654 :alt: Example of Rally keystone test results
657 .. figure:: ./images/functestRally1.png
660 :alt: Details on Glance test from Rally bench suite
665 - some tests of Cinder suite may be failed due to time-out (timer could probably be extended in the configuration file)
666 - some test of Nova & Neutron suite may fail due to network issues (previously created network not properly cleaned and/or quota exceeded because of created ressources that have not be properly cleaned) or ODL bugs (see `ODL bug lists`_).
668 More details on `functest wiki (Rally section)`_.
673 You can get the results of tempest by typing::
677 You shall see the results as follow::
679 Total results of verification:
681 +--------------------------------------+--------------------------------------+----------+-------+----------+----------------------------+----------------+----------+
682 | UUID | Deployment UUID | Set name | Tests | Failures | Created at | Duration | Status |
683 +--------------------------------------+--------------------------------------+----------+-------+----------+----------------------------+----------------+----------+
684 | 546c678a-19c4-4b2e-8f24-6f8c5ff20635 | 9c13dbbe-7a80-43db-8d6c-c4a61f257c7f | smoke | 111 | 15 | 2015-09-14 06:18:54.896224 | 0:00:51.804504 | finished |
685 +--------------------------------------+--------------------------------------+----------+-------+----------+----------------------------+----------------+----------+
687 If you run this test several times, you will see as many lines as test attempts.
689 You can get more details on the test by typing::
691 # rally verify show --uuid <UUID of the test>
692 # rally verify detailed --uuid <UUID of the test>
694 "show" will show you all the restults including the time needed to execute the test.
695 "detailed" will display additional elements (errors)
697 Example of test result display::
699 +------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------+--------+
700 | name | time | status |
701 +------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------+--------+
702 | tempest.api.network.test_routers.RoutersTest.test_create_show_list_update_delete_router[id-f64403e2-8483-4b34-8ccd-b09a87bcc68c,smoke] | 0.011466 | FAIL |
703 | tempest.api.network.test_security_groups.SecGroupIPv6Test.test_create_list_update_show_delete_security_group[id-bfd128e5-3c92-44b6-9d66-7fe29d22c802,smoke]| 1.234566 | OK |
704 | tempest.api.network.test_security_groups.SecGroupIPv6Test.test_create_show_delete_security_group_rule[id-cfb99e0e-7410-4a3d-8a0c-959a63ee77e9,smoke] | 1.060221 | OK |
705 | tempest.api.network.test_security_groups.SecGroupIPv6Test.test_list_security_groups[id-e30abd17-fef9-4739-8617-dc26da88e686,smoke] | 0.060797 | OK |
706 | tempest.api.network.test_security_groups.SecGroupTest.test_create_list_update_show_delete_security_group[id-bfd128e5-3c92-44b6-9d66-7fe29d22c802,smoke] | 0.685149 | OK |
707 | tempest.api.network.test_security_groups.SecGroupTest.test_create_show_delete_security_group_rule[id-cfb99e0e-7410-4a3d-8a0c-959a63ee77e9,smoke] | 0.730561 | OK |
708 | tempest.api.network.test_security_groups.SecGroupTest.test_list_security_groups[id-e30abd17-fef9-4739-8617-dc26da88e686,smoke] | 0.116862 | OK |
709 | tempest.api.object_storage.test_account_quotas.AccountQuotasTest | 0.0 | SKIP |
716 .. _`Rally patch`: https://review.openstack.org/#/c/187481/
717 .. _`automatically generated tempest.conf`: https://github.com/openstack/rally/blob/master/rally/verification/tempest/config.py
718 .. _`functest wiki (Tempest section)`: https://wiki.opnfv.org/r1_tempest
719 .. _`ODL bug lists`: https://bugs.opendaylight.org/buglist.cgi?component=General&product=neutron&resolution=---
721 Several tests are declared as failed. They can be divided in 2 main categories:
722 * Multiple possible networks found, use a Network ID to be more specific.
725 The Multiple possible netwok error occurs several times and may have different origins. It indicates that the test needs a network context to be run properly. A change in the `automatically generated tempest.conf`_ file could allow to precise the network ID.
727 The network errors are various and dealing with all the aspects of networking: create/update/delete network/subnet/port/router. Some may be due to (possible) bug in tempest when it tries to delete networks which should not be there for the following tests. Some may be caused by the ODL bugs, several bugs related to tempest are already reported in `ODL bug lists`_.
729 The follow-up of these tests can be found on the `functest wiki (Tempest section)`_.
737 For Arno, the CI job performs the following actions:
738 * clean and prepare functest environment
743 * clean functest environment
745 Connection of your platform
746 ===========================
748 .. _`Octopus procedure`: https://wiki.opnfv.org/octopus/jenkins_slave_connection/
750 If you want to add your platform to the community automation, please follow the `Octopus procedure`_.
752 Integrating into CI Pipeline
753 ============================
755 .. _`pipeline document`: https://wiki.opnfv.org/octopus/pipelines
757 Contact Octopus Team (#opnfv-octopus) and see `pipeline document`_ for more details.
765 OPNFV main site: opnfvmain_.
767 OPNFV functional test page: opnfvfunctest_.
769 IRC support chan: #opnfv-testperf
771 .. _opnfvmain: http://www.opnfv.org
772 .. _opnfvfunctest: https://wiki.opnfv.org/opnfv_functional_testing
773 .. _`OpenRC`: http://docs.openstack.org/user-guide/common/cli_set_environment_variables_using_openstack_rc.html
774 .. _`Rally installation procedure`: https://rally.readthedocs.org/en/latest/tutorial/step_0_installation.html
775 .. _`config_test.py` : https://git.opnfv.org/cgit/functest/tree/testcases/config_functest.py
776 .. _`config_functest.yaml` : https://git.opnfv.org/cgit/functest/tree/testcases/config_functest.yaml