blob: 228e0af9829148f188b3e8942457c451ce45bacd (
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
|
===========================
OPNFV functional test guide
===========================
The goal of this document consists in describing how to run functional tests on OPNFV solution and how to automate these tests.
For release 1, several test cases have been selected:
* Rally Bench test suite
* Tempest tes suite
* OpenDaylight test suite
* vPing
* vIMS
.. _prereqs:
-------------
Prerequisites
-------------
We assume that an OPNFV solution has been installed (System Under Test).
For release 1, the tools needed for functional testing are not part of the installer and are not automatically installed.
.. _pharos: https://wiki.opnfv.org/pharos
It is recommended to install the tools on the jump host server as defined in the Pharos project.
.. _installation:
------------
Installation
------------
Rally bench test suite
======================
Create or enter a folder where you want to check out the tool repos. Follow `Rally installation procedure`_.
.. _`Rally installation procedure`: https://rally.readthedocs.org/en/latest/tutorial/step_0_installation.html
Tempest
=======
It is possible to use Rally to perform Tempest tests. See `tempest installation guide using Rally`_.
.. _`tempest installation guide using Rally`: https://www.mirantis.com/blog/rally-openstack-tempest-testing-made-simpler/
OpenDaylight
============
vPing
=====
vIMS
====
.. _manualtest:
--------------
Manual testing
--------------
Rally
=====
Check your deployment::
# rally deployment check
keystone endpoints are valid and following service are available:
+-------------+-----------+------------+
| Services | Type | Status |
+-----------+-------------+------------+
| cinder | volume | Available |
| cinderv2 | volumev2 | Available |
| glance | image | Available |
| keystone | identity | Available |
| neutron | network | Available |
| nova | compute | Available |
| nova_ec2 | compute_ec2 | Available |
| novav3 | computev3 | Available |
+-----------+-------------+------------+
Create a new opnfv scenario directory and run test suite::
# cd ~/rally/samples/tasks/scenario/
# mkdir opnfv
# wget http://git.opnfv.org/.. <TODO>
# rally task start --abort-on-sla-failure ./opnfv.json
Tempest
=======
If we consider running Tempest suite with Rally::
# rally verify start
# rally verify list
OpenDaylight
============
vPing
=====
vIMS
====
.. _automatictest:
------------------
Testing Automation
------------------
Connection of your platform
===========================
If you want to add your platform to the community automation, you need to declare your machine as a Jenkins slave.
* Send a mail to OPNFV LF Helpdesk (opnfv-helpdesk@rt.linuxfoundation.org)
* Create a local user jenkins on your machine
* wget http://mirrors.jenkins-ci.org/war/1.599/jenkins.war
* Extract contents, find the file named slave.jar and copy it to somewhere which jenkins user created in first step can access.
* Create a directory /home/jenkins/opnfv_slave_root
* check the java version (>1.7.0_75)
* Contact Linux Foundation to manage authentication of your server
* A key/token will be produced. Establish connection towards OPNFV Jenkins by using below command: java -jar slave.jar -jnlpUrl https://build.opnfv.org/ci/computer/<slave_name>/slave-agent.jnlp -secret <token>
Continuous integration scripts
==============================
.. _references:
----------
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
|
