1 .. This work is licensed under a
2 .. Creative Commons Attribution 4.0 International License.
3 .. http://creativecommons.org/licenses/by/4.0
10 Policy Drools PDP component
11 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
13 Both the Performance and the Stability tests were executed against a default ONAP installation in the policy-k8s tenant in the windriver lab, from an independent VM running the jmeter tool to inject the load.
18 The kubernetes installation allocated all policy components in the same worker node VM and some additional ones.
19 The worker VM hosting the policy components has the following spec:
23 - 160GB Ephemeral Disk
25 The standalone VM designated to run jmeter has the same configuration. The jmeter JVM
26 was instantiated with a max heap configuration of 12G.
28 Other ONAP components used during the stability tests are:
30 - Policy XACML PDP to process guard queries for each transaction.
31 - DMaaP to carry PDP-D and jmeter initiated traffic to complete transactions.
32 - Policy API to create (and delete at the end of the tests) policies for each
34 - Policy PAP to deploy (and undeploy at the end of the tests) policies for each scenario under test.
36 The following components are simulated during the tests.
38 - SO actor for the vDNS use case.
39 - APPC responses for the vCPE and vFW use cases.
40 - AAI to answer queries for the use cases under test.
42 In order to avoid interferences with the APPC component while running the tests,
43 the APPC component was disabled.
45 SO, and AAI actors were simulated within the PDP-D JVM by enabling the
46 feature-controlloop-utils before running the tests.
51 The kubernetes charts were modified previous to the installation with
54 The feature-controlloop-utils was started by adding the following script:
58 oom/kubernetes/policy/charts/drools/resources/configmaps/features.pre.sh:
61 bash -c "features enable controlloop-utils"
63 Stability Test of Policy PDP-D
64 ******************************
66 The 72 hour stability test happened in parallel with the stability run of the API component.
68 Worker Node performance
69 =======================
71 The VM named onap-k8s-09 was monitored for the duration of the 72 hours
72 stability run. The table below show the usage ranges:
77 onap-k8s-09 <=1214m <=20%
82 The test set focused on the following use cases:
88 For 72 hours the following 5 scenarios ran in parallel:
90 - vCPE success scenario
91 - vCPE failure scenario (failure returned by simulated APPC recipient through DMaaP).
92 - vDNS success scenario.
93 - vDNS failure scenario.
94 - vFirewall success scenario.
96 Five threads ran in parallel, one for each scenario. The transactions were initiated
97 by each jmeter thread group. Each thread initiated a transaction, monitored the transaction, and
98 as soon as the transaction ending was detected, it initiated the next one, so back to back with no
101 All transactions completed successfully as it was expected in each scenario, with no failures.
103 The command executed was
107 ./jmeter -n -t /home/ubuntu/drools-applications/testsuites/stability/src/main/resources/frankfurt/s3p.jmx -l /home/ubuntu/jmeter_result/jmeter.jtl -e -o /home/ubuntu/jmeter_result > /dev/null 2>&1
109 The results were computed by taking the ellapsed time from the audit.log
110 (this log reports all end to end transactions, marking the start, end, and
113 The count reflects the number of successful transactions as expected in the
114 use case, as well as the average, standard deviation, and max/min. An histogram
115 of the response times have been added as a visual indication on the most common
118 vCPE Success scenario
119 =====================
121 ControlLoop-vCPE-48f0c2c3-a172-4192-9ae3-052274181b6e:
125 Max: 4323 ms, Min: 143 ms, Average: 380 ms [samples taken for average: 260628]
127 .. image:: images/ControlLoop-vCPE-48f0c2c3-a172-4192-9ae3-052274181b6e.png
130 vCPE Failure scenario
131 =====================
133 ControlLoop-vCPE-Fail:
137 Max: 3723 ms, Min: 148 ms, Average: 671 ms [samples taken for average: 87888]
139 .. image:: images/ControlLoop-vCPE-Fail.png
141 vDNS Success scenario
142 =====================
144 ControlLoop-vDNS-6f37f56d-a87d-4b85-b6a9-cc953cf779b3:
148 Max: 6437 ms, Min: 19 ms, Average: 165 ms [samples taken for average: 59259]
150 .. image:: images/ControlLoop-vDNS-6f37f56d-a87d-4b85-b6a9-cc953cf779b3.png
152 vDNS Failure scenario
153 =====================
155 ControlLoop-vDNS-Fail:
159 Max: 1176 ms, Min: 4 ms, Average: 5 ms [samples taken for average: 340810]
161 .. image:: images/ControlLoop-vDNS-Fail.png
163 vFirewall Success scenario
164 ==========================
166 ControlLoop-vFirewall-d0a1dfc6-94f5-4fd4-a5b5-4630b438850a:
170 Max: 4016 ms, Min: 177 ms, Average: 644 ms [samples taken for average: 36460]
172 .. image:: images/ControlLoop-vFirewall-d0a1dfc6-94f5-4fd4-a5b5-4630b438850a.png