blob: 0eabac21753ffada42d47fdef3382b9caff081c1 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
|
===========================
OPNFV FUNCTEST user guide
===========================
.. contents::
.. _introduction:
DOCUMENT IS IN PROGRESS FOR BRAHMAPUTRA
------------
Introduction
------------
.. _description:
-----------------------------
Description of the test cases
-----------------------------
vPing
=====
The goal of this test can be described as follow::
vPing testcase
+-------------+ +-------------+
| | | |
| | | |
| | Boot VM1 | |
| +------------------>| |
| | | |
| | Get IP VM1 | |
| +------------------>| |
| Tester | | System |
| | Boot VM2 | Under |
| +------------------>| Test |
| | VM2 pings VM1 | |
| | | |
| | Check console log | |
| | If ping: | |
| | exit OK | |
| | else (timeout) | |
| | exit KO | |
| | | |
| | | |
+-------------+ +-------------+
This example, using OpenStack Python clients can be considered as an "Hello World" example and may be modified for future use.
In SR1, some code has been added in order to push the results (status and duration) into a centralized test result database.
SDN Controllers
===============
OpenDaylight
------------
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.
The list of tests can be described as follow:
* Restconf.basic: Get the controller modules via Restconf
* Neutron.Networks
* Check OpenStack Networks :: Checking OpenStack Neutron for known networks
* Check OpenDaylight Networks :: Checking OpenDaylight Neutron API
* Create Network :: Create new network in OpenStack
* Check Network :: Check Network created in OpenDaylight
* Neutron.Networks :: Checking Network created in OpenStack are pushed
* Neutron.Subnets
* Check OpenStack Subnets :: Checking OpenStack Neutron for known Subnets
* Check OpenDaylight subnets :: Checking OpenDaylight Neutron API
* Create New subnet :: Create new subnet in OpenStack
* Check New subnet :: Check new subnet created in OpenDaylight
* Neutron.Subnets :: Checking Subnets created in OpenStack are pushed
* Neutron.Ports
* Check OpenStack ports :: Checking OpenStack Neutron for known ports
* Check OpenDaylight ports :: Checking OpenDaylight Neutron API
* Create New Port :: Create new port in OpenStack
* Check New Port :: Check new subnet created in OpenDaylight
* Neutron.Ports :: Checking Port created in OpenStack are pushed
* Delete Ports
* Delete previously created subnet in OpenStack
* Check subnet deleted in OpenDaylight
* Check subnet deleted in OpenStack
* Delete network
* Delete previously created network in OpenStack
* Check network deleted in OpenDaylight
* Check network deleted in OpenStack
ONOS
----
TODO
OpenContrail
------------
TODO
Tempest
=======
.. _Tempest: http://docs.openstack.org/developer/tempest/overview.html
Tempest_ is the OpenStack Integration Test Suite. We use Rally to run Tempest suite.
The Tempest.conf configuration file is automatically generated by Rally then the Tempest suite is run, each test duration is measured.
We considered the smoke test suite for Arno.
The goal of this test is to to check the basic OpenStack functionality on a fresh installation.
vIMS
====
TODO
Rally bench test suite
======================
.. _Rally: https://wiki.openstack.org/wiki/Rally
Rally bench test suite consist in a suite of light performance tests on some of the OpenStack components.
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.
The OPNFV scenarios are based on the collection of the existing Rally_ scenarios:
* authenticate
* cinder
* nova
* requests
* glance
* keystone
* neutron
* quotas
This test suite provides performance information on VIM (OpenStack) part.
No SLA were defined for release 1, we just consider whether the tests are passed or failed.
In the future SLA shall be defined (e.g. accepting booting time for a given image with a given flavour).
Through its integration in Continuous Integration, the evolution of the performance of these tests shall also be considered.
Feature projects
================
--------------
Manual testing
--------------
------------------
Automated testing
------------------
---------------
Troubleshooting
---------------
----------
References
----------
OPNFV main site: opnfvmain_.
OPNFV functional test page: opnfvfunctest_.
IRC support chan: #opnfv-testperf
.. _opnfvmain: http://www.opnfv.org
.. _opnfvfunctest: https://wiki.opnfv.org/opnfv_functional_testing
.. _`OpenRC`: http://docs.openstack.org/user-guide/common/cli_set_environment_variables_using_openstack_rc.html
.. _`Rally installation procedure`: https://rally.readthedocs.org/en/latest/tutorial/step_0_installation.html
.. _`config_test.py` : https://git.opnfv.org/cgit/functest/tree/testcases/config_functest.py
.. _`config_functest.yaml` : https://git.opnfv.org/cgit/functest/tree/testcases/config_functest.yaml
|
