1 *************************
2 OPNFV FUNCTEST user guide
3 *************************
14 The goal of this document is describing the Functest test cases for Brahmaputra.
15 A presentation has been created for the first OPNFV Summit: `[4]`
17 This guide will detail how to launch the different tests assuming that Functest container has been properly installed `[1]`_.
20 =============================
21 Description of the test cases
22 =============================
24 Functest is an OPNFV project dedicated to functional testing.
25 In the continuous integration, it is launched after a fresh installation of an OPNFV solution to verify the basic functions.
27 Functest includes several test suites that usually include several test cases.
28 Some are developped within the Functest project, some in dedicated feature projects.
30 The current list of test suites can be distributed in 3 main domains:
32 +----------------+----------------+---------------------------------------------------------+
33 | Component | Test suite | Comments |
34 +----------------+----------------+---------------------------------------------------------+
35 | | vPing | NFV "Hello World" |
36 | VIM +----------------+---------------------------------------------------------+
37 |(Virtualised | Tempest | OpenStack reference test suite `[2]`_ |
38 | Infrastructure +----------------+---------------------------------------------------------+
39 | Manager) | Rally scenario | OpenStack testing tool testing OpenStack modules `[3]`_ |
40 +----------------+----------------+---------------------------------------------------------+
42 | +----------------+---------------------------------------------------------+
43 | Controllers | onos | |
44 | +----------------+---------------------------------------------------------+
46 +----------------+----------------+---------------------------------------------------------+
47 | Features | vIMS | Show the capability to deploy a real NFV testcase |
48 | +----------------+---------------------------------------------------------+
50 +----------------+----------------+---------------------------------------------------------+
53 Most of the test suites are developed upstream. For example, Tempest `[2]`_ is the OpenStack integration test suite.
54 Functest is in charge of the integration of different functional test suites in OPNFV.
56 In Functest we customized the list of tests within Tempest but do not created our own test cases.
57 Some OPNFV feature projects (.e.g. SDNVPN) may create tempest scenario upstream that are integrated in our Tempest through our configuration.
59 The test results are pushed into a test result database (when possible) in order to build a test dashboard.
61 There is no real notion of Test domain or Test coverage yet, we tried to cover basic components such as VIM and controllers and integrate the tests of the feature projects.
63 The vIMS test case was also integrated to demonstrate the capability to deploy a relatively complex NFV scenario on top of the OPNFV infrastructure.
65 Functest considers OPNFV as a black box. OPNFV, since Brahmaputra, offers lots of possible combination (3 controllers, 4 installers).
67 However most of the tests (except obviously those dedicated to a specific controller) shall be runnable on any configuration.
69 The different scenarios are described in the section hereafter.
77 The goal of this test can be described as follow::
80 +-------------+ +-------------+
84 | +------------------>| |
87 | +------------------>| |
89 | | Boot VM2 | Under |
90 | +------------------>| Test |
93 | | Check console log | |
96 | | else (timeout) | |
100 +-------------+ +-------------+
103 This example, using OpenStack Python clients can be considered as an "Hello World" example and may be modified for future use.
104 It is the first basic example, it must work on any configuration.
109 Tempest `[2]`_ is the reference OpenStack Integration test suite. It is a set of integration tests to be run against a live OpenStack cluster.
110 Tempest has batteries of tests for OpenStack API validation, Scenarios, and other specific tests useful in validating an OpenStack deployment.
112 We use Rally `[3]`_ to run Tempest suite.
113 Rally generates automatically tempest.conf configuration file.
114 Before running actual test cases Functest creates needed resources and updates needed parameters into the configuration file.
115 When the Tempest suite is run, each test duration is measured and full console output is stored into tempest.log file.
117 We considered the smoke test suite for Arno. For Brahmaputra, we decided to customize the list of test cases using the --tests-file option introduced in Rally in version 0.1.2.
119 The customized test list is available on the Functest repo `[4]`_ and contains more than 200 tempest test cases chosen for Functest deployment.
120 The list consists of two main parts:
122 1) Set of tempest smoke test cases
123 2) Set of test cases from DefCore list (https://wiki.openstack.org/wiki/Governance/DefCoreCommittee)
125 The goal of Tempest test suite is to check the basic functionality of different OpenStack components on an OPNFV fresh installation using corresponding REST API interfaces.
128 Rally bench test suites
129 -----------------------
131 Rally `[3]`_ is a benchmarking tool that answers the question: “How does OpenStack work at scale?”.
133 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.
135 The OPNFV scenarios are based on the collection of the existing Rally scenarios:
147 For Brahmaputra, we integrated the rally certification feature introduced in Rally 0.1.1.
155 Brahmaputra introduces new SDN controllers in addition of odl already integrated in Arno.
156 There are currently 3 possible controllers:
165 The ODL test suite consists of a set of basic tests inherited from ODL project.
166 The suite verifies creation and deletion of networks, subnets and ports with OpenDaylight and Neutron.
168 The list of tests can be described as follow:
170 * Restconf.basic: Get the controller modules via Restconf
173 * Check OpenStack Networks :: Checking OpenStack Neutron for known networks
174 * Check OpenDaylight Networks :: Checking OpenDaylight Neutron API
175 * Create Network :: Create new network in OpenStack
176 * Check Network :: Check Network created in OpenDaylight
177 * Neutron.Networks :: Checking Network created in OpenStack are pushed
181 * Check OpenStack Subnets :: Checking OpenStack Neutron for known Subnets
182 * Check OpenDaylight subnets :: Checking OpenDaylight Neutron API
183 * Create New subnet :: Create new subnet in OpenStack
184 * Check New subnet :: Check new subnet created in OpenDaylight
185 * Neutron.Subnets :: Checking Subnets created in OpenStack are pushed
189 * Check OpenStack ports :: Checking OpenStack Neutron for known ports
190 * Check OpenDaylight ports :: Checking OpenDaylight Neutron API
191 * Create New Port :: Create new port in OpenStack
192 * Check New Port :: Check new subnet created in OpenDaylight
193 * Neutron.Ports :: Checking Port created in OpenStack are pushed
197 * Delete previously created subnet in OpenStack
198 * Check subnet deleted in OpenDaylight
199 * Check subnet deleted in OpenStack
203 * Delete previously created network in OpenStack
204 * Check network deleted in OpenDaylight
205 * Check network deleted in OpenStack
211 For ONOS function test,TestON Framework is being used.
212 The test cases contains L2 and L3 function.We config the function by OpenStack,and then check it in ONOS.
213 Following describe the test cases:
215 * onosfunctest: The mainly executable file,contains init the docker environment for test and function call of FUNCvirNetNB and FUNCvirNetNBL3
218 * Create Network :: Post Network data and check it in ONOS
219 * Update Network :: Update the Network and compare it in ONOS
220 * Delete Network :: Delete the Network and check if it's NULL in ONOS or not
221 * Create Subnet :: Post Subnet data and check it in ONOS
222 * Update Subnet :: Update the Subnet and compare it in ONOS
223 * Delete Subnet :: Delete the Subnet and check if it's NULL in ONOS or not
224 * Create Port :: Post Port data and check it in ONOS
225 * Update Port :: Update the Port and compare it in ONOS
226 * Delete Port :: Delete the Port and check if it's NULL in ONOS or not
230 * Create Router :: Post dataes for create Router and check it in ONOS
231 * Update Router :: Update the Router and compare it in ONOS
232 * Delete Router :: Delete the Router dataes and check it in ONOS
233 * Create RouterInterface :: Post RouterInterface data to an exist Router and check it in ONOS
234 * Delete RouterInterface :: Delete the RouterInterface and check the Router
235 * Create FloatingIp :: Post dataes for create FloatingIp and check it in ONOS
236 * Update FloatingIp :: Update the FloatingIp and compare it in ONOS
237 * Delete FloatingIp :: Delete the FloatingIp and check if it's NULL in ONOS or not
238 * Create External Gateway :: Post dataes for create External Gateway to an exit Router and check it
239 * Update External Gateway :: Update the External Gateway and compare it
240 * Delete External Gateway :: Delete the External Gateway and check if it's NULL in ONOS or not
254 The goal of this test suite consists in:
255 * deploying a VNF orchestrator (cloudify)
256 * deploy a Clearwater vIMS (IP Multimedia Subsystem) VNF from this orchestrator based on a TOSCA blueprint defined in `[5]`_
257 * run suite of signaling tests on top of this VNF
259 The Clearwater architecture may be described as follow:
261 .. figure:: ../images/clearwater-architecture.png
263 :alt: vIMS architecture
265 The duration of each step (orchestion deployment, VNF deployment and test), as well as test results, are stored and, in CI, pushed into the test collection database.
277 Once you have installed Functest docker file `[1]`_, and configured the system (though /home/opnfv/repos/functest/docker/prepare_env.sh script), you are ready to run the tests.
279 The script run_tests.sh has several options::
282 Script to trigger the tests automatically.
285 bash run_tests.sh [--offline] [-h|--help] [-t <test_name>]
288 -h|--help show this help text
289 -r|--report push results to database (false by default)
290 -t|--test run specific set of tests
291 <test_name> one or more of the following: vping,odl,rally,tempest,vims. Separated by comma.
295 run_tests.sh --test vping,odl
296 run_tests.sh -t tempest,rally
298 The -o option can be used to run the container offline (in case you are in a summit where there is no Internet connection...). It is an experimental option.
300 The -r option is used by the Continuous Integration in order to push the test results into a test collection database, see in next section for details. In manual mode, you must not use it, your try will be anyway probably rejected as your POD must be declared in the database to collect the data.
302 The -t option can be used to specify the list of test you want to launch, by default Functest will try to launch all its test suites in the following order vPing, odl, Tempest, vIMS, Rally. You may launch only one single test by using -t <the test you want to launch>
304 Within Tempest test suite you can define which test cases you want to execute in your environment by editing test_list.txt file before executing run_tests.sh script.
306 Please note that Functest includes cleaning mechanism in order to remove everything except what was present after a fresh install. If you create your own VMs, tenants, networks etc. and then launch Functest, they all will be deleted after executing the tests. Be carefull or comment the cleaning phase in run_test.sh (comment call to clean_openstack.py). However, be aware that Tempest and Rally create of lot of resources (users, tenants, networks, volumes etc.) that are not always properly cleaned, so this cleaning function has been set to keep the system as clean as possible after a full Functest run.
308 You may also add you own test by adding a section into the function run_test()
315 As mentioned in `[1]`, the prepare-env.sh and run_test.sh can be executed within the container from jenkins. 2 jobs have been created, one to run all the test and one that allows testing test suite by test suite. You thus just have to launch the acurate jenkins job on the target lab, all the tests shall be automatically run.
328 vPing result is displayed in the console::
330 2016-01-06 16:06:20,550 - vPing- INFO - Creating neutron network vping-net...
331 2016-01-06 16:06:23,867 - vPing- INFO - Flavor found 'm1.small'
332 2016-01-06 16:06:24,457 - vPing- INFO - vPing Start Time:'2016-01-06 16:06:24'
333 2016-01-06 16:06:24,626 - vPing- INFO - Creating instance 'opnfv-vping-1' with IP 192.168.130.30...
334 2016-01-06 16:06:39,351 - vPing- INFO - Instance 'opnfv-vping-1' is ACTIVE.
335 2016-01-06 16:06:39,650 - vPing- INFO - Creating instance 'opnfv-vping-2' with IP 192.168.130.40...
336 2016-01-06 16:06:53,330 - vPing- INFO - Instance 'opnfv-vping-2' is ACTIVE.
337 2016-01-06 16:06:53,330 - vPing- INFO - Waiting for ping...
338 2016-01-06 16:06:58,669 - vPing- INFO - vPing detected!
339 2016-01-06 16:06:58,669 - vPing- INFO - vPing duration:'34.2'
340 2016-01-06 16:06:58,670 - vPing- INFO - Cleaning up...
341 2016-01-06 16:07:12,661 - vPing- INFO - Deleting network 'vping-net'...
342 2016-01-06 16:07:14,748 - vPing- INFO - vPing OK
344 A json file is produced and pushed into the test result database.
350 The Tempest results are displayed in the console::
352 FUNCTEST.info: Running Tempest tests...
353 2016-01-06 16:07:32,271 - run_tempest - INFO - Creating tenant and user for Tempest suite
354 2016-01-06 16:07:38,864 - run_tempest - INFO - Starting Tempest test suite: '--tests-file /home/opnfv/repos/functest/testcases/VIM/OpenStack/CI/custom_tests/test_list.txt'.
356 {23} tempest.api.compute.flavors.test_flavors.FlavorsV2TestJSON.test_get_flavor [0.131741s] ... ok
357 {13} tempest.api.compute.images.test_list_images.ListImagesTestJSON.test_get_image [0.367465s] ... ok
358 {23} tempest.api.compute.flavors.test_flavors.FlavorsV2TestJSON.test_list_flavors [0.089323s] ... ok
359 {13} tempest.api.compute.images.test_list_images.ListImagesTestJSON.test_list_images [0.245090s] ... ok
360 {13} tempest.api.compute.images.test_list_images.ListImagesTestJSON.test_list_images_with_detail [0.434553s] ... ok
361 {7} setUpClass (tempest.api.identity.admin.v3.test_services.ServicesTestJSON) [0.000000s] ... FAILED
362 {5} setUpClass (tempest.api.identity.admin.v3.test_groups.GroupsV3TestJSON) [0.000000s] ... FAILED
363 {4} setUpClass (tempest.api.network.test_floating_ips.FloatingIPTestJSON) [0.000000s] ... FAILED
364 {10} setUpClass (tempest.api.identity.admin.v3.test_policies.PoliciesTestJSON) [0.000000s] ... FAILED
365 {3} tempest.api.compute.servers.test_servers.ServersTestJSON.test_create_server_with_admin_password [3.107954s] ... ok
366 {9} tempest.api.compute.security_groups.test_security_groups.SecurityGroupsTestJSON.test_security_groups_create_list_delete [2.933169s] ... ok
368 {1} tempest.api.network.test_networks.BulkNetworkOpsIpV6TestJSON.test_bulk_create_delete_network [1.002445s] ... ok
369 {1} tempest.api.network.test_networks.BulkNetworkOpsIpV6TestJSON.test_bulk_create_delete_port [1.553398s] ... ok
370 {1} tempest.api.network.test_networks.BulkNetworkOpsIpV6TestJSON.test_bulk_create_delete_subnet [3.082247s] ... ok
371 {3} tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_network_basic_ops [48.295630s] ... ok
372 {6} tempest.api.compute.servers.test_server_actions.ServerActionsTestJSON.test_rebuild_server [78.782038s] ... ok
373 {6} tempest.api.compute.servers.test_server_actions.ServerActionsTestJSON.test_resize_server_confirm [15.597440s] ... ok
374 {6} tempest.api.compute.servers.test_server_actions.ServerActionsTestJSON.test_resize_server_revert [19.248253s] ... ok
375 {6} tempest.api.compute.servers.test_server_actions.ServerActionsTestJSON.test_stop_start_server [7.078850s] ... ok
376 {6} tempest.api.compute.volumes.test_attach_volume.AttachVolumeTestJSON.test_attach_detach_volume [40.311720s] ... ok
377 {6} tempest.api.volume.test_volumes_actions.VolumesV1ActionsTest.test_attach_detach_volume_to_instance [1.159194s] ... ok
382 Ran: 199 tests in 241.0000 sec.
386 - Unexpected Success: 0
388 Sum of execute time for each test: 481.0934 sec.
390 In order to check all the available test case related debug information, please inspect tempest.log file stored into related Rally deployment folder.
402 The results of ODL tests can be seen in the console::
404 ==============================================================================
406 ==============================================================================
407 Basic.010 Restconf OK :: Test suite to verify Restconf is OK
408 ==============================================================================
409 Get Controller Modules :: Get the controller modules via Restconf | PASS |
410 ------------------------------------------------------------------------------
411 Basic.010 Restconf OK :: Test suite to verify Restconf is OK | PASS |
412 1 critical test, 1 passed, 0 failed
413 1 test total, 1 passed, 0 failed
414 ==============================================================================
416 1 critical test, 1 passed, 0 failed
417 1 test total, 1 passed, 0 failed
418 ==============================================================================
419 Output: /home/jenkins-ci/workspace/functest-opnfv-jump-2/output.xml
420 Log: /home/jenkins-ci/workspace/functest-opnfv-jump-2/log.html
421 Report: /home/jenkins-ci/workspace/functest-opnfv-jump-2/report.html
423 ..............................................................................
425 Neutron.Delete Networks :: Checking Network deleted in OpenStack a... | FAIL |
426 2 critical tests, 1 passed, 1 failed
427 2 tests total, 1 passed, 1 failed
428 ==============================================================================
429 Neutron :: Test suite for Neutron Plugin | FAIL |
430 18 critical tests, 15 passed, 3 failed
431 18 tests total, 15 passed, 3 failed
432 ==============================================================================
433 Output: /home/jenkins-ci/workspace/functest-opnfv-jump-2/output.xml
434 Log: /home/jenkins-ci/workspace/functest-opnfv-jump-2/log.html
435 Report: /home/jenkins-ci/workspace/functest-opnfv-jump-2/report.html
437 3 result files are generated:
444 .. figure:: ./images/functestODL.png
447 :alt: ODL suite result page
453 Tests are expected to fail now:
454 * Check port deleted in OpenDaylight
455 * Check subnet deleted in OpenDaylight
456 * Check Network deleted in OpenDaylight
458 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.
463 The ONOS test logs output to OnosSystemTest/TestON/logs with ONOSCI_PATH added,and also can be seen in the console::
465 ******************************
466 Result summary for Testcase4
467 ******************************
469 2016-01-14 05:25:40,529 - FUNCvirNetNBL3 - INFO - ONOS Router Delete test Start
471 [2016-01-14 05:25:40.529644] [FUNCvirNetNBL3] [CASE] Virtual Network NBI Test - Router
472 2016-01-14 05:25:40,530 - FUNCvirNetNBL3 - INFO - Generate Post Data
474 [2016-01-14 05:25:40.530825] [FUNCvirNetNBL3] [STEP] 4.1: Post Network Data via HTTP(Post Router need post network)
475 2016-01-14 05:25:40,531 - FUNCvirNetNBL3 - INFO - Sending request http://192.168.122.56:8181/onos/vtn/networks/ using POST method.
476 2016-01-14 05:25:40,539 - FUNCvirNetNBL3 - INFO - Verifying the Expected is equal to the actual or not using assert_equal
477 2016-01-14 05:25:40,539 - FUNCvirNetNBL3 - INFO - Post Network Success
478 2016-01-14 05:25:40,539 - FUNCvirNetNBL3 - INFO - Assertion Passed
480 [2016-01-14 05:25:40.539687] [FUNCvirNetNBL3] [STEP] 4.2: Post Router Data via HTTP
481 2016-01-14 05:25:40,540 - FUNCvirNetNBL3 - INFO - Sending request http://192.168.122.56:8181/onos/vtn/routers/ using POST method.
482 2016-01-14 05:25:40,543 - FUNCvirNetNBL3 - INFO - Verifying the Expected is equal to the actual or not using assert_equal
483 2016-01-14 05:25:40,543 - FUNCvirNetNBL3 - INFO - Post Router Success
484 2016-01-14 05:25:40,543 - FUNCvirNetNBL3 - INFO - Assertion Passed
486 [2016-01-14 05:25:40.543489] [FUNCvirNetNBL3] [STEP] 4.3: Delete Router Data via HTTP
487 2016-01-14 05:25:40,543 - FUNCvirNetNBL3 - INFO - Sending request http://192.168.122.56:8181/onos/vtn/routers/e44bd655-e22c-4aeb-b1e9-ea1606875178 using DELETE method.
488 2016-01-14 05:25:40,546 - FUNCvirNetNBL3 - INFO - Verifying the Expected is equal to the actual or not using assert_equal
489 2016-01-14 05:25:40,546 - FUNCvirNetNBL3 - INFO - Delete Router Success
490 2016-01-14 05:25:40,546 - FUNCvirNetNBL3 - INFO - Assertion Passed
492 [2016-01-14 05:25:40.546774] [FUNCvirNetNBL3] [STEP] 4.4: Get Router Data is NULL
493 2016-01-14 05:25:40,547 - FUNCvirNetNBL3 - INFO - Sending request http://192.168.122.56:8181/onos/vtn/routers/e44bd655-e22c-4aeb-b1e9-ea1606875178 using GET method.
494 2016-01-14 05:25:40,550 - FUNCvirNetNBL3 - INFO - Verifying the Expected is equal to the actual or not using assert_equal
495 2016-01-14 05:25:40,550 - FUNCvirNetNBL3 - INFO - Get Router Success
496 2016-01-14 05:25:40,550 - FUNCvirNetNBL3 - INFO - Assertion Passed
499 *****************************
501 *****************************
503 .......................................................................................
505 ******************************
506 Result summary for Testcase9
507 ******************************
508 .......................................................................................
511 [2016-01-14 05:26:42.543489] [FUNCvirNetNBL3] [STEP] 9.6: FloatingIp Clean Data via HTTP
512 2016-01-14 05:26:42,543 - FUNCvirNetNBL3 - INFO - Sending request http://192.168.122.56:8181/onos/vtn/floatingips/e44bd655-e22c-4aeb-b1e9-ea1606875178 using DELETE method.
513 2016-01-14 05:26:42,546 - FUNCvirNetNBL3 - INFO - Verifying the Expected is equal to the actual or not using assert_equal
514 2016-01-14 05:26:42,546 - FUNCvirNetNBL3 - ERROR - Delete Floatingip failed
516 .......................................................................................
518 *****************************
520 *****************************
522 There's a Result summary for each testcase,and a total summary for the whole test file,if any problem occured,ERROR can be seen in the testcase summary and total summary::
524 *************************************
525 Test Execution Summary
527 *************************************
529 Test Start : 14 Jan 2016 05:25:37
530 Test End : 14 Jan 2016 05:25:41
531 Execution Time : 0:00:03.349087
532 Total tests planned : 11
537 Success Percentage : 72%
538 Execution Result : 100%
552 The results in the console are very verbose::
554 FUNCTEST.info: Running vIMS test...
555 2016-01-07 12:30:24,107 - vIMS - INFO - Prepare OpenStack plateform (create tenant and user)
556 2016-01-07 12:30:24,484 - vIMS - INFO - Update OpenStack creds informations
557 2016-01-07 12:30:24,484 - vIMS - INFO - Upload some OS images if it doesn't exist
558 2016-01-07 12:30:24,917 - vIMS - INFO - centos_7 image doesn't exist on glance repository.
559 Try downloading this image and upload on glance !
560 2016-01-07 12:31:01,268 - vIMS - INFO - ubuntu_14.04 image doesn't exist on glance repository.
561 Try downloading this image and upload on glance !
562 2016-01-07 12:31:28,670 - vIMS - INFO - Update security group quota for this tenant
563 2016-01-07 12:31:28,903 - vIMS - INFO - Update cinder quota for this tenant
564 2016-01-07 12:31:29,355 - vIMS - INFO - Collect flavor id for cloudify manager server
565 2016-01-07 12:31:30,453 - vIMS - INFO - Prepare virtualenv for cloudify-cli
566 2016-01-07 12:31:30,453 - vIMS - DEBUG - Executing command : chmod +x /home/opnfv/repos/functest/testcases/vIMS/CI/create_venv.sh
567 2016-01-07 12:31:30,460 - vIMS - DEBUG - Executing command : /home/opnfv/repos/functest/testcases/vIMS/CI/create_venv.sh /home/opnfv/functest/data/vIMS/
568 2016-01-07 12:31:30,469 - vIMS - INFO - Downloading the cloudify manager server blueprint
569 2016-01-07 12:31:46,028 - vIMS - INFO - Cloudify deployment Start Time:'2016-01-07 12:31:46'
570 2016-01-07 12:31:46,029 - vIMS - INFO - Writing the inputs file
571 2016-01-07 12:31:46,032 - vIMS - INFO - Launching the cloudify-manager deployment
572 .........................................
573 2016-01-07 12:36:51 LOG <manager> [rabbitmq_3c04e.create] INFO: preparing fabric environment...
574 2016-01-07 12:36:51 LOG <manager> [rabbitmq_3c04e.create] INFO: environment prepared successfully
575 .........................................
576 2016-01-07 12:42:51,982 - vIMS - INFO - Cloudify-manager server is UP !
577 2016-01-07 12:42:51,983 - vIMS - INFO - Cloudify deployment duration:'666.0'
578 2016-01-07 12:42:51,983 - vIMS - INFO - Collect flavor id for all clearwater vm
579 2016-01-07 12:42:53,330 - vIMS - INFO - vIMS VNF deployment Start Time:'2016-01-07 12:42:53'
580 2016-01-07 12:42:53,330 - vIMS - INFO - Downloading the openstack-blueprint.yaml blueprint
581 2016-01-07 12:43:05,798 - vIMS - INFO - Writing the inputs file
582 2016-01-07 12:43:05,801 - vIMS - INFO - Launching the clearwater deployment
583 2016-01-07 12:43:05,801 - vIMS - DEBUG - Executing command : /bin/bash -c 'source /home/opnfv/functest/data/vIMS/venv_cloudify/bin/activate; cd /home/opnfv/functest/data/vIMS/opnfv-cloudify-clearwater; cfy blueprints upload -b clearwater -p openstack-blueprint.yaml; cfy deployments create -b clearwater -d clearwater-opnfv --inputs inputs.yaml; cfy executions start -w install -d clearwater-opnfv --timeout 1800; '
584 2016-01-07 13:01:50,577 - vIMS - DEBUG - Validating openstack-blueprint.yaml
585 Blueprint validated successfully
586 Uploading blueprint openstack-blueprint.yaml to management server 172.30.10.165
587 Uploaded blueprint, blueprint's id is: clearwater
588 Creating new deployment from blueprint clearwater at management server 172.30.10.165
589 Deployment created, deployment's id is: clearwater-opnfv
590 .........................................
591 2016-01-07 13:01:50,578 - vIMS - INFO - The deployment of clearwater-opnfv is ended
592 2016-01-07 13:01:50,578 - vIMS - INFO - vIMS VNF deployment duration:'1137.2'
593 2016-01-07 13:04:50,591 - vIMS - DEBUG - Trying to get clearwater nameserver IP ...
594 2016-01-07 13:04:55,176 - vIMS - INFO - vIMS functional test Start Time:'2016-01-07 13:04:55'
595 2016-01-07 13:14:20,694 - vIMS - INFO - vIMS functional test duration:'565.5'
596 .........................................
597 Basic Call - Rejected by remote endpoint (TCP) - (6505550603, 6505550969) Passed
598 Basic Call - Rejected by remote endpoint (UDP) - (6505550095, 6505550084) Passed
599 Basic Call - Messages - Pager model (TCP) - (6505550000, 6505550520) Passed
600 Basic Call - Messages - Pager model (UDP) - (6505550742, 6505550077) Passed
601 Basic Call - Pracks (TCP) - (6505550670, 6505550304) Passed
602 Basic Call - Pracks (UDP) - (6505550990, 6505550391) Passed
603 Basic Registration (TCP) - (6505550744) Passed
604 Basic Registration (UDP) - (6505550616) Passed
605 Multiple Identities (TCP) - (6505550957, 6505550949) Passed
606 Multiple Identities (UDP) - (6505550771, 6505550675) Passed
607 .........................................
608 2016-01-07 13:14:20,695 - vIMS - DEBUG - Trying to load test results
609 2016-01-07 13:14:20,702 - vIMS - DEBUG - Push result into DB
610 2016-01-07 13:14:20,702 - vIMS - DEBUG - Pushing results to DB....
611 2016-01-07 13:14:21,396 - vIMS - DEBUG - <Response [200]>
612 2016-01-07 13:14:21,396 - vIMS - INFO - Launching the clearwater-opnfv undeployment
615 ==========================
616 Functest in test Dashboard
617 ==========================
619 The OPNFV testing group created a test collection database to collect the test results from CI.
620 Any lab integrated in CI can push the results to this database.
622 The idea is to centralize the resultes and create a dashboard to give a high level overview of the test activities.
623 You can find more information about the dashboard from Testing Dashboard wiki page `[6]`_.
640 In the upstream OpenStack CI all the Tempest test cases are supposed to pass. If some test cases fail in an OPNFV deployment, the reason is very probably one of the following:
642 * Some resources required for execution test cases are missing. Such resources could be e.g. an external network and access to the management subnet (adminURL) from the Functest docker container.
643 * Some OpenStack components or services are missing or not configured properly. You can check running services in the controller and compute nodes e.g. with "systemctl" or "service" commands. Configuration parameters can be verified from related .conf files located under /etc/<component> directories.
644 * Used tempest.conf file doesn't contain all the needed parameters or some parameters are not set properly. When using Functest, tempest.conf file is generated by Rally and updated with needed parameters automatically before executing Tempest cases. You can find the used configuration file e.g. with "find / -name tempest.conf" command. Use "rally deployment list" command in order to check UUID of current deployment.
646 When some Tempest test case fails, captured traceback and possibly also related REST API requests/responses are output to the console.
647 More detailed debug information can be found from tempest.log file stored into related Rally deployment folder.
680 .. _`[1]`: Functest configuration guide URL
681 .. _`[2]`: http://docs.openstack.org/developer/tempest/overview.html
682 .. _`[3]`: https://rally.readthedocs.org/en/latest/index.html
683 .. _`[4]`: http://events.linuxfoundation.org/sites/events/files/slides/Functest%20in%20Depth_0.pdf
684 .. _`[5]`: https://github.com/Orange-OpenSource/opnfv-cloudify-clearwater/blob/master/openstack-blueprint.yaml
685 .. _`[6]`: https://wiki.opnfv.org/opnfv_test_dashboard
688 OPNFV main site: opnfvmain_.
690 OPNFV functional test page: opnfvfunctest_.
692 IRC support chan: #opnfv-testperf
694 .. _opnfvmain: http://www.opnfv.org
695 .. _opnfvfunctest: https://wiki.opnfv.org/opnfv_functional_testing
696 .. _`OpenRC`: http://docs.openstack.org/user-guide/common/cli_set_environment_variables_using_openstack_rc.html
697 .. _`Rally installation procedure`: https://rally.readthedocs.org/en/latest/tutorial/step_0_installation.html
698 .. _`config_test.py` : https://git.opnfv.org/cgit/functest/tree/testcases/config_functest.py
699 .. _`config_functest.yaml` : https://git.opnfv.org/cgit/functest/tree/testcases/config_functest.yaml