1 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
2 .. http://creativecommons.org/licenses/by/4.0
4 Overview of the functest suites
5 ===============================
7 Functest is the OPNFV project primarily targeting function testing.
8 In the Continuous Integration pipeline, it is launched after an OPNFV fresh
9 installation to validate and verify the basic functions of the infrastructure.
11 The current list of test suites can be distributed in 3 main domains: VIM
12 (Virtualised Infrastructure Manager), Controllers and Features.
14 +----------------+----------------+-------------------------------------------+
15 | Domain | Test suite | Comments |
16 +================+================+===========================================+
17 | VIM | vPing | NFV "Hello World" using SSH connection |
18 | | | and floatting IP |
19 | +----------------+-------------------------------------------+
20 | | vPing_userdata | Ping using userdata and cloud-init |
22 | +----------------+-------------------------------------------+
23 | | Tempest | OpenStack reference test suite `[2]`_ |
24 | +----------------+-------------------------------------------+
25 | | Rally bench | OpenStack testing tool benchmarking |
26 | | | OpenStack modules `[3]`_ |
27 +----------------+----------------+-------------------------------------------+
28 | | OpenDaylight | Opendaylight Test suite |
29 | +----------------+-------------------------------------------+
30 | Controllers | ONOS | Test suite of ONOS L2 and L3 functions |
31 | | | See `ONOSFW User Guide`_ for details |
32 +----------------+----------------+-------------------------------------------+
33 | Features | vIMS | Example of a real VNF deployment to show |
34 | | | the NFV capabilities of the platform. |
35 | | | The IP Multimedia Subsytem is a typical |
36 | | | Telco test case, referenced by ETSI. |
37 | | | It provides a fully functional VoIP System|
38 | +----------------+-------------------------------------------+
39 | | Promise | Resource reservation and management |
40 | | | project to identify NFV related |
41 | | | requirements and realize resource |
42 | | | reservation for future usage by capacity |
43 | | | management of resource pools regarding |
44 | | | compute, network and storage. |
45 | | | See `Promise User Guide`_ for details |
46 | +----------------+-------------------------------------------+
47 | | Doctor | Doctor platform, as of Brahmaputra release|
48 | | | , provides the two features: |
49 | | | * Immediate Notification |
50 | | | * Consistent resource state awareness |
51 | | | (compute), see `Doctor User Guide`_ for |
53 +----------------+----------------+-------------------------------------------+
56 Functest includes different test suites with several test cases within. Some
57 of the tests are developed by Functest team members whereas others are
58 integrated from upstream communities or other OPNFV projects. For example,
59 `Tempest <http://docs.openstack.org/developer/tempest/overview.html>`_ is the
60 OpenStack integration test suite and Functest is in charge of the selection,
61 integration and automation of the tests that fit in OPNFV.
63 The Tempest suite has been customized but no new test cases have been created.
65 The results produced by the tests run from CI are pushed and collected in a NoSQL
66 database. The goal is to populate the database with results from different sources
67 and scenarios and to show them on a Dashboard.
69 There is no real notion of Test domain or Test coverage. Basic components
70 (VIM, controllers) are tested through their own suites. Feature projects also
71 provide their own test suites with different ways of running their tests.
73 vIMS test case was integrated to demonstrate the capability to deploy a
74 relatively complex NFV scenario on top of the OPNFV infrastructure.
76 Functest considers OPNFV as a black box.
77 OPNFV, since the Brahmaputra release, offers lots of potential combinations:
79 * 2 controllers (OpenDayligh, ONOS)
80 * 4 installers (Apex, Compass, Fuel, Joid)
82 Most of the tests are runnable on any combination, but some others might have
83 restrictions imposed by the installers or the available deployed features.
85 .. _`[2]`: http://docs.openstack.org/developer/tempest/overview.html
86 .. _`[3]`: https://rally.readthedocs.org/en/latest/index.html
87 .. _`Doctor User Guide`: http://artifacts.opnfv.org/opnfvdocs/brahmaputra/docs/userguide/featureusage-doctor.html
88 .. _`Promise User Guide`: http://artifacts.opnfv.org/promise/brahmaputra/docs/userguide/index.html
89 .. _`ONOSFW User Guide`: http://artifacts.opnfv.org/onosfw/brahmaputra/docs/userguide/index.html