1 .. This work is licensed under a
2 .. Creative Commons Attribution 4.0 International License.
3 .. http://creativecommons.org/licenses/by/4.0
13 72 Hours Stability Test of PAP
14 ++++++++++++++++++++++++++++++
19 The 72 hour Stability Test for PAP has the goal of introducing a steady flow of transactions initiated from a test client server running JMeter for the duration of 72 hours.
24 The stability test is performed on VM's running in OpenStack cloud environment.
26 There are 2 seperate VM's, one for running PAP & other one for running JMeter to simulate steady flow of transactions.
28 All the dependencies like mariadb, dmaap simulator, pdp simulator & policy/api component are installed in the VM having JMeter.
30 For simplicity lets assume
32 VM1 will be running JMeter, MariaDB, DMaaP simulator, PDP simulator & API component.
34 VM2 will be running only PAP component.
36 **OpenStack environment details**
40 **PAP VM details (VM2)**
50 Docker version 19.03.8
52 Java: openjdk version "11.0.7" 2020-04-14
54 **JMeter VM details (VM1)**
64 Docker Version: 18.09.6
66 Java: openjdk version "11.0.7" 2020-04-14
70 Install Docker in VM1 & VM2
71 ---------------------------
73 Make sure to execute below commands in VM1 & VM2 both.
75 Make the etc/hosts entries
79 $ echo $(hostname -I | cut -d\ -f1) $(hostname) | sudo tee -a /etc/hosts
85 $ echo "nameserver <PrimaryDNSIPIP>" >> /etc/resolvconf/resolv.conf.d/head
86 $ echo "nameserver <SecondaryDNSIP>" >> /etc/resolvconf/resolv.conf.d/head
89 Update the ubuntu software installer
95 Check and Install Java
99 $ apt-get install -y openjdk-11-jdk
102 Ensure that the Java version that is executing is OpenJDK version 8
105 Check and install docker
109 $ curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
110 $ add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"
112 $ apt-cache policy docker-ce
113 $ apt-get install -y docker-ce
114 $ systemctl status docker
117 Change the permissions of the Docker socket file
121 $ chmod 777 /var/run/docker.sock
123 Check the status of the Docker service and ensure it is running correctly
127 $ service docker status
130 Install JMeter in VM1
131 ---------------------
133 Download & install JMeter
139 $ wget http://mirrors.whoishostingthis.com/apache//jmeter/binaries/apache-jmeter-5.2.1.zip
140 $ unzip apache-jmeter-5.2.1.zip
146 $ /home/ubuntu/jMeter/apache-jmeter-5.2.1/bin/jmeter
148 The above command will load the JMeter UI. Then navigate to File ā Open ā Browse and select the test plan jmx file to open.
149 The jmx file is present in the policy/pap git repository.
151 Install simulators in VM1
152 -------------------------
154 For installing simulator, there is a script placed at `install simulator script <https://gerrit.onap.org/r/gitweb?p=policy/pap.git;a=blob;f=testsuites/stability/src/main/resources/simulatorsetup/setup_components.sh;h=86de3c1efcb468431a2395eef610db209a613fc3;hb=refs/heads/master>`_
156 Copy the script & all related files in virtual machine and run it.
158 After installation make sure that following 4 docker containers are up and running.
162 root@policytest-policytest-3-p5djn6as2477:/home/ubuntu/simulator# docker ps
163 CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
164 887efa8dac12 nexus3.onap.org:10001/onap/policy-api "bash ./policy-api.sh" 6 days ago Up 6 days 0.0.0.0:6969->6969/tcp policy-api
165 0a931c0a63ac pdp/simulator:latest "bash pdp-sim.sh" 6 days ago Up 6 days pdp-simulator
166 a41adcb32afb dmaap/simulator:latest "bash dmaap-sim.sh" 6 days ago Up 6 days 0.0.0.0:3904->3904/tcp dmaap-simulator
167 d52d6b750ba0 mariadb:10.2.14 "docker-entrypoint.sā¦" 6 days ago Up 6 days 0.0.0.0:3306->3306/tcp mariadb
172 For installing PAP, there is a script placed at `install pap script <https://gerrit.onap.org/r/gitweb?p=policy/pap.git;a=blob;f=testsuites/stability/src/main/resources/papsetup/setup_pap.sh;h=dc5e69e76da9f48f6b23cc012e14148f1373d1e1;hb=refs/heads/master>`_
174 Copy the script & all related files in virtual machine and run it.
176 After installation make sure that following docker container is up and running.
180 root@policytest-policytest-0-uc3y2h5x6p4j:/home/ubuntu/pap# docker ps
181 CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
182 42ac0ed4b713 nexus3.onap.org:10001/onap/policy-pap:2.2.3-SNAPSHOT "bash ./policy-pap.sh" 3 days ago Up 3 days 0.0.0.0:6969->6969/tcp, 0.0.0.0:9090->9090/tcp policy-pap
184 Install & configure visualVM in VM2
185 -----------------------------------
187 visualVM needs to be installed in the virtual machine having PAP. It will be used to monitor CPU, Memory, GC for PAP while stability test is running.
193 $ sudo apt-get install visualvm
195 Run few commands to configure permissions
199 $ cd /usr/lib/jvm/java-11-openjdk-amd64/bin/
200 $ sudo touch visualvm.policy
201 $ sudo chmod 777 visualvm.policy
205 Add the following in visualvm.policy
208 grant codebase "file:/usr/lib/jvm/java-11-openjdk-amd64/lib/tools.jar" {
209 permission java.security.AllPermission;
212 Run following commands to start jstatd using port 1111
216 $ cd /usr/lib/jvm/java-11-openjdk-amd64/bin/
217 $ ./jstatd -p 1111 -J-Djava.security.policy=visualvm.policy &
219 Run visualVM locally to connect to remote VM2
223 # On your windows machine or your linux box locally, launch visualVM
226 Connect to jstatd & remote apex-pdp JVM
228 1. Right click on "Remote" in the left panel of the screen and select "Add Remote Host..."
229 2. Enter the IP address of VM2.
230 3. Right click on IP address, select "Add JMX Connection..."
231 4. Enter the VM2 IP Address (from step 2) <IP address>:9090 ( for example -10.12.6.201:9090) and click OK.
232 5. Double click on the newly added nodes under "Remote" to start monitoring CPU, Memory & GC.
234 Sample Screenshot of visualVM
236 .. image:: images/pap-s3p-vvm-sample.png
241 The 72 hours stability test will run the following steps sequentially in a single threaded loop.
243 - **Create Policy Type** - creates an operational policy type using policy/api component
244 - **Create Policy defaultDomain** - creates an operational policy using the policy type created in the above step using policy/api component
245 - **Create Policy sampleDomain** - creates an operational policy using the policy type created in the above step using policy/api component
246 - **Check Health** - checks the health status of pap
247 - **Check Statistics** - checks the statistics of pap
248 - **Change state to ACTIVE** - changes the state of defaultGroup PdpGroup to ACTIVE
249 - **Check PdpGroup Query** - makes a PdpGroup query request and verifies that PdpGroup is in the ACTIVE state.
250 - **Deploy defaultDomain Policy** - deploys the policy defaultDomain in the existing PdpGroup
251 - **Create/Update PDP Group** - creates a new PDPGroup named sampleGroup.
252 - **OS Process Sampler** - OS Process Sampler to start a new Pdp Instance
253 - **Check PdpGroup Query** - makes a PdpGroup query request and verifies that 2 PdpGroups are in the ACTIVE state and defaultGroup has a policy deployed on it.
254 - **Deployment Update sampleDomain** - deploys the policy sampleDomain in sampleGroup PdpGroup using pap api
255 - **Check PdpGroup Query** - makes a PdpGroup query request and verifies that the defaultGroup has a policy defaultDomain deployed on it and sampleGroup has policy sampleDomain deployed on it.
256 - **Check Deployed Policies** - checks for all the deployed policies using pap api.
257 - **OS Process Sampler** - OS Process Sampler to stop the newly created Pdp Instance
258 - **Undeploy Policy sampleDomain** - undeploys the policy sampleDomain from sampleGroup PdpGroup using pap api
259 - **Undeploy Default Policy** - undeploys the policy defaultDomain from PdpGroup
260 - **Change state to PASSIVE(sampleGroup)** - changes the state of sampleGroup PdpGroup to PASSIVE
261 - **Delete PdpGroup SampleGroup** - delete the sampleGroup PdpGroup using pap api
262 - **Change State to PASSIVE(defaultGroup)** - changes the state of defaultGroup PdpGroup to PASSIVE
263 - **Check PdpGroup Query** - makes a PdpGroup query request and verifies that PdpGroup is in the PASSIVE state.
264 - **Delete Policy defaultDomain** - deletes the operational policy defaultDomain using policy/api component
265 - **Delete Policy sampleDomain** - deletes the operational policy sampleDomain using policy/api component
266 - **Delete Policy Type** - deletes the operational policy type using policy/api component
268 The following steps can be used to configure the parameters of test plan.
270 - **HTTP Authorization Manager** - used to store user/password authentication details.
271 - **HTTP Header Manager** - used to store headers which will be used for making HTTP requests.
272 - **User Defined Variables** - used to store following user defined parameters.
274 =========== ===================================================================
275 **Name** **Description**
276 =========== ===================================================================
277 PAP_HOST IP Address or host name of PAP component
278 PAP_PORT Port number of PAP for making REST API calls
279 API_HOST IP Address or host name of API component
280 API_PORT Port number of API for making REST API calls
281 DIR Path where the pdp instance startup and stop script is placed
282 CONFIG_DIR Path where the pdp default Config file is placed
283 =========== ===================================================================
285 Screenshot of PAP stability test plan
287 .. image:: images/pap-s3p-testplan.png
294 Stability test plan was triggered for 72 hours.
298 ======================= ================= ================== ==================================
299 **Total # of requests** **Success %** **Error %** **Average time taken per request**
300 ======================= ================= ================== ==================================
301 178208 100 % 0 % 76 ms
302 ======================= ================= ================== ==================================
304 **VisualVM Screenshot**
306 .. image:: images/pap-s3p-vvm-1.png
307 .. image:: images/pap-s3p-vvm-2.png
309 **JMeter Screenshot**
311 .. image:: images/pap-s3p-jm-1.png
312 .. image:: images/pap-s3p-jm-1.png
314 Test Results Frankfurt release
315 -------------------------------
319 Stability test plan was triggered for 72 hours.
323 .. container:: paragraph
325 Test cases for starting and stopping the PDP Instance has been included in the
326 test plan. These test cases have resulted in a spike in the Average time taken per request.
330 ======================= ================= ================== ==================================
331 **Total # of requests** **Success %** **Error %** **Average time taken per request**
332 ======================= ================= ================== ==================================
333 29423 100 % 0 % 948 ms
334 ======================= ================= ================== ==================================
336 **VisualVM Screenshot**
338 .. image:: images/pap-s3p-vvm-1_F.png
339 .. image:: images/pap-s3p-vvm-2_F.png
341 **JMeter Screenshot**
343 .. image:: images/pap-s3p-jm-1_F.png
344 .. image:: images/pap-s3p-jm-1_F.png
346 Performance Test of PAP
347 ++++++++++++++++++++++++
352 Performance test of PAP has the goal of testing the min/avg/max processing time and rest call throughput for all the requests with multiple requests at the same time.
357 The performance test is performed on a similar setup as Stability test. The JMeter VM will be sending a large number of REST requests to the PAP component and collecting the statistics.
362 Performance test plan is the same as the stability test plan above except for the few differences listed below.
364 - Increase the number of threads up to 5 (simulating 5 users' behaviours at the same time).
365 - Reduce the test time to 2 hours.
366 - Usage of counters to create different groups by the 'Create/Update PDP Group' test case.
367 - Usage of If-Controller for 'Deploy defaultDomain Policy' and 'Undeploy defaultDomain Policy' test cases to install and uninstall the Default policy only in one thread.
368 - OS Process Sampler for starting and stopping the PDP Instance has been disabled in the performance test plan for a better performance check.
373 Running/Triggering 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*.
375 Once the test execution is completed, execute the below script to get the statistics:
379 $ cd /home/ubuntu/pap/testsuites/performance/src/main/resources/testplans
380 $ ./results.sh /home/ubuntu/pap_perf/resultTree.log
385 Test results are shown as below. Overall, the test was running smoothly and successfully. We do see some minor failed transactions, especially in the 'Deploy' and 'Undeploy' Pap API in a multi-threaded fashion .
389 ======================= ================= ================== ================================== =======================
390 **Total # of requests** **Success %** **Error %** **Average time taken per request** **Requests/sec**
391 ======================= ================= ================== ================================== =======================
392 25743 99.5 % 0.50 % 397 ms 5148
393 ======================= ================= ================== ================================== =======================
395 **JMeter Screenshot**
397 .. image:: images/pap-perf-jm-1_F.png
398 .. image:: images/pap-perf-jm-2_F.png