1 .. This work is licensed under a
2 .. Creative Commons Attribution 4.0 International License.
3 .. http://creativecommons.org/licenses/by/4.0
10 ##########################
12 Policy XACML PDP S3P Tests
13 ~~~~~~~~~~~~~~~~~~~~~~~~~~
15 Both the Performance and the Stability tests were executed by performing requests
16 against Policy components installed in Kubernetes environment. These tests were all
17 performed on a Ubuntu VM with 32GB of memory, 16 CPU and 100GB of disk space.
19 Policy XACML PDP Deployment
20 +++++++++++++++++++++++++++
22 In an effort to allow the execution of the s3p tests to be as close to automatic as possible,
23 a script will be executed that will perform the following:
25 - Install of a microk8s kubernetes environment
26 - Bring up the policy components
27 - Checks that the components are successfully up and running before proceeding
29 - Install Jmeter locally and configure it
30 - Specify whether you want to run stability or performance tests
33 The remainder of this document outlines how to run the tests and the test results
37 The common setup for performance and stability tests is now automated - being carried out by a script in- **testsuites/run-s3p-test.sh**.
39 Clone the policy-xacml-pdp repo to access the test scripts
43 git clone https://gerrit.onap.org/r/policy/xacml-pdp xacml-pdp
45 Stability Test of Policy XACML PDP
46 ++++++++++++++++++++++++++++++++++
50 The 24 hours stability test ran the following steps.
52 - Healthcheck, 2 simultaneous threads
53 - Decisions, 2 simultaneous threads, each running the following tasks in sequence:
55 - Monitoring Decision, abbreviated
57 - Optimization Decision
58 - Default Guard Decision (always "Permit")
59 - Frequency Limiter Guard Decision
60 - Min/Max Guard Decision
62 This runs for 24 hours. Test results are present in the **testsuites/automated-performance/s3pTestResults.jtl**
63 file and in **/tmp/** directory. Logs are present for jmeter in **testsuites/automated-performance/jmeter.log** and
64 **testsuites/automated-performance/nohup.out**
69 The code in the setup section also serves to run the tests. Just one execution needed to do it all.
73 bash run-s3p-test.sh run stability
75 Once the test execution is completed, the results are present in the **automate-performance/s3pTestResults.jtl** file.
77 This file can be imported into the Jmeter GUI for visualization. The below results are tabulated from the GUI.
84 Stability test plan was triggered for 24 hours.
88 ======================= ================= ======================== =========================
89 **Total # of requests** **Error %** **Average Latency (ms)** **Measured requests/sec**
90 ======================= ================= ======================== =========================
91 54472562 0.00 % 5 ms 630.1 ms
92 ======================= ================= ======================== =========================
96 .. image:: xacml-s3p-results/s3p-stability-xacml.png
98 **Policy component Setup**
100 ============================================== ==================================================================== =============================================
101 **NAME** **IMAGE** **PORT**
102 ============================================== ==================================================================== =============================================
103 zookeeper-deployment-7ff87c7fcc-fbsfb confluentinc/cp-zookeeper:latest 2181/TCP
104 kafka-deployment-5c87d497b-m8s2g confluentinc/cp-kafka:latest 9092/TCP
105 policy-drools-pdp-0 nexus3.onap.org:10001/onap/policy-pdpd-cl:2.1.3-SNAPSHOT 6969/TCP 9696/TCP
106 policy-apex-pdp-0 nexus3.onap.org:10001/onap/policy-apex-pdp:3.1.3-SNAPSHOT 6969/TCP
107 policy-distribution-f48bff778-48pm2 nexus3.onap.org:10001/onap/policy-distribution:3.1.3-SNAPSHOT 6969/TCP
108 policy-models-simulator-6947667bdc-wcd9r nexus3.onap.org:10001/onap/policy-models-simulator:3.1.3-SNAPSHOT 6666/TCP 6680/TCP 6668/TCP 6669/TCP 6670/TCP
109 policy-clamp-ac-http-ppnt-7d747b5d98-wmr5n nexus3.onap.org:10001/onap/policy-clamp-ac-http-ppnt:7.1.3-SNAPSHOT 8084/TCP
110 policy-clamp-ac-k8s-ppnt-6bbd86bbc6-vnvx6 nexus3.onap.org:10001/onap/policy-clamp-ac-k8s-ppnt:7.1.3-SNAPSHOT 8083/TCP
111 policy-clamp-ac-pf-ppnt-5fcbbcdb6c-k2cbk nexus3.onap.org:10001/onap/policy-clamp-ac-pf-ppnt:7.1.3-SNAPSHOT 6969/TCP
112 policy-clamp-ac-sim-ppnt-97f487577-m2zjr nexus3.onap.org:10001/onap/policy-clamp-ac-sim-ppnt:7.1.3-SNAPSHOT 6969/TCP
113 policy-clamp-runtime-acm-66b5d6b64-l6dpq nexus3.onap.org:10001/onap/policy-clamp-runtime-acm:7.1.3-SNAPSHOT 6969/TCP
114 mariadb-galera-0 docker.io/bitnami/mariadb-galera:10.5.8 3306/TCP
115 prometheus-f66f97b6-kkmpq nexus3.onap.org:10001/prom/prometheus:latest 9090/TCP
116 policy-api-7f7d995b4-2zhnw nexus3.onap.org:10001/onap/policy-api:3.1.3-SNAPSHOT 6969/TCP
117 policy-pap-f7899d4cd-mfrtp nexus3.onap.org:10001/onap/policy-pap:3.1.3-SNAPSHOT 6969/TCP
118 policy-xacml-pdp-6c86f85ff6-6qzgf nexus3.onap.org:10001/onap/policy-xacml-pdp:3.1.2 6969/TCP
119 ============================================== ==================================================================== =============================================
123 .. container:: paragraph
125 There were no failures during the 24 hours test.
127 The XACML PDP offered very good performance with JMeter for the traffic mix described above.
128 The average transaction time is insignificant.
131 Performance Test of Policy XACML PDP
132 ++++++++++++++++++++++++++++++++++++
137 Performance test of acm components 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.
142 We can setup the environment and execute the tests like this from the **xacml-pdp/testsuites** directory
147 Performance test plan is the same as the stability test plan above except for the few differences listed below.
149 - Increase the number of threads up to 10 (simulating 10 users' behaviours at the same time).
150 - Reduce the test time to 20 minutes.
152 The performance tests runs the following, all in parallel:
154 - Healthcheck, 10 simultaneous threads
155 - Decisions, 10 simultaneous threads, each running the following in sequence:
157 - Monitoring Decision
158 - Monitoring Decision, abbreviated
160 - Optimization Decision
161 - Default Guard Decision (always "Permit")
162 - Frequency Limiter Guard Decision
163 - Min/Max Guard Decision
165 When the script starts up, it uses policy-api to create, and policy-pap to deploy
166 the policies that are needed by the test. It assumes that the "naming" policy has
167 already been created and deployed. Once the test completes, it undeploys and deletes
168 the policies that it previously created.
173 The code in the setup section also serves to run the tests. Just one execution needed to do it all.
177 bash run-s3p-test.sh run performance
179 Once the test execution is completed, the results are present in the **automate-performance/s3pTestResults.jtl** file and in **/tmp/** directory.
181 This file can be imported into the Jmeter GUI for visualization. The below results are tabulated from the GUI.
188 The test was run for 20 minutes with 10 users (i.e., threads), with the following results:
192 ======================= ================= ======================== =========================
193 **Total # of requests** **Error %** **Average Latency (ms)** **Measured requests/sec**
194 ======================= ================= ======================== =========================
195 888047 0.00 % 25 ms 723.2 ms
196 ======================= ================= ======================== =========================
198 .. image:: xacml-s3p-results/s3p-perf-xacml.png