blob: f5c0e7cfc674fcaba5e7980ec5654e3ca8cfed96 (
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
|
.. This work is licensed under a
.. Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
.. _apex-s3p-label:
.. toctree::
:maxdepth: 2
Policy APEX PDP component
~~~~~~~~~~~~~~~~~~~~~~~~~
Setting up Stability Tests in APEX
++++++++++++++++++++++++++++++++++
Introduction
------------
The 72 hour Stability Test for apex-pdp has the goal of introducing a steady flow of transactions initiated from a test client server running JMeter. The pdp is configured to start a rest server inside it and take input from rest clients (JMeter) and send back output to the rest clients (JMeter).
The input events will be submitted through rest interface of apex-pdp and the results are verified using the rest responses coming out from apex-pdp.
The test will be performed in a multi-threaded environment where 5 threads running in JMeter will keep sending events to apex-pdp for the duration of 72 hours.
Setup details
-------------
Stability test is performed on VM's running in OpenStack cloud environment. APEX-PDP along with other components in Policy Framework is deployed in an OOM ONAP installation. JMeter runs on a separate VM to simulate a steady flow of transactions.
Test Plan
---------
The 72 hours stability test will run the following steps in a 5 threaded loop.
Setup stage (these calls run only once - at the beginning)
- **Create Policy** - creates a policy using the policy/api component
- **Deploy Policy** - deploys the policy in the existing PdpGroup
Test stage (these calls run over and over again)
- **Check Health** - checks the health status of apex
- **Send Input Event** - triggers 'unauthenticated.DCAE_CL_OUTPUT' event of DMaaP.
- **Get Output Event Response** - checks for the triggered output event.
Teardown stage (this calls run only once - at the end)
- **Undeploy Policy** - undeploys the policy from PdpGroup
- **Delete Policy** - deletes the policy using the policy/api component
The following steps can be used to configure the parameters of the test plan.
- **HTTP Header Manager** - used to store headers which will be used for making HTTP requests.
- **HTTP Request Defaults** - used to store HTTP request details like Server Name or IP, Port, Protocol etc.
- **User Defined Variables** - used to store the following user defined parameters:
================== ============================================================================ ============================
**Name** **Description** **Default Value**
================== ============================================================================ ============================
wait Wait time after each request (in milliseconds) 10000
threads Number of threads to run test cases in parallel. 5
threadsTimeOutInMs Synchronization timer for threads running in parallel (in milliseconds). 5000
PAP_PORT Port number of PAP for making REST API calls
API_PORT Port number of API for making REST API calls
APEX_PORT Port number of APEX for making REST API calls
DMAAP_PORT Port number of DMAAP for making REST API calls
HOSTNAME Server IP address for making REST API calls
================== ============================================================================ ============================
Download and update the jmx file presented in the apex-pdp git repository - `jmx file path <https://gerrit.onap.org/r/gitweb?p=policy/apex-pdp.git;a=tree;f=testsuites/apex-pdp-stability/src/main/resources;h=99d373033a190a690d4e05012bc3a656cae7bc3f;hb=refs/heads/master>`_.
- ThreadGroup.duration - Set the duration to 259200 seconds (72 hours)
Use the CLI mode to start the test
.. code-block:: bash
nohup ./jmeter.sh -n -t ~/apexPdpStabilityTestPlan.jmx -Jusers=1 -l ~/stability.log
Stability Test Results
----------------------
The stability test plan was triggered for 72 hours, injecting input events to apex-pdp pod from 5 client threads running in JMeter.
The stability tests were executed as part of a full ONAP OOM deployment in Nordix lab.
Once the tests complete, we can generate an HTML test report via the command:
.. code-block:: bash
~/jMeter/apache-jmeter-5.2.1/bin/jmeter -g stability.log -o ./result/
============================================== ================================ ============= ============ ============================
**Number of Client Threads running in JMeter** **Total number of input events** **Success %** **Error %** **Average Time per Request**
============================================== ================================ ============= ============ ============================
5 129326 100% 0% 6716.12
============================================== ================================ ============= ============ ============================
**JMeter Screenshot**
.. image:: images/apex_s3p_jm-1.png
.. image:: images/apex_s3p_jm-2.png
:download:`result.zip <apex-s3p-results/apex_s3p_results.zip>`
Setting up Performance Tests in APEX
++++++++++++++++++++++++++++++++++++
The Performance test is performed on a similar setup to the Stability test. JMeter will send a large number of REST requests and will then retrieve those requests.
Performance test plan will be the same as the stability test plan except for some differences listed below:
- Increase the number of threads from 5 to 20.
- Reduce test time to ninety minutes. (ThreadGroup.duration - Set the duration to 5400 seconds)
Download and update the jmx file presented in the apex-pdp git repository - `jmx file path <https://gerrit.onap.org/r/gitweb?p=policy/apex-pdp.git;a=tree;f=testsuites/performance/performance-benchmark-test/src/main/resources;h=b0ed1058b11f82b42fb5be1a07009114e1e8b593;hb=refs/heads/master>`_.
Run Test
--------
Running the performance test will be the same as the stability test. That is, launch JMeter pointing to corresponding *.jmx* test plan. The *API_HOST* , *API_PORT* , *PAP_HOST* , *PAP_PORT* are already set up in *.jmx*.
.. code-block:: bash
nohup ./jmeter.sh -n -t ~/performance.jmx -Jusers=1 -l ~/perf.log
Once the tests have completed, run the following the gather results.
.. code-block:: bash
~/jMeter/apache-jmeter-5.2.1/bin/jmeter -g perf.log -o ./performance_result/
Performance Test Result
-----------------------
**Summary**
Performance test was triggered for 90 minutes. The results are shown below.
**Test Statistics**
============================ =========== ========= ==================================
**Total Number of Requests** **Success** **Error** **Average Time Taken per Request**
============================ =========== ========= ==================================
32304 99,99 % 0.01 % 8746.50 ms
============================ =========== ========= ==================================
**JMeter Screenshot**
.. image:: images/apex_perf_jm_1.PNG
.. image:: images/apex_perf_jm_2.PNG
|
