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 APEX PDP component
11 ~~~~~~~~~~~~~~~~~~~~~~~~~
13 Both the Stability and the Performance tests were executed in a full ONAP OOM deployment in Nordix lab.
19 - APEX-PDP along with all policy components deployed as part of a full ONAP OOM deployment.
20 - Policy-models-simulator is deployed to use CDS and DMaaP simulators during policy execution.
21 Simulator configurations used are available in apex-pdp repository:
22 testsuites/apex-pdp-stability/src/main/resources/simulatorConfig/
23 - Two APEX policies are executed in the APEX-PDP engine, and are triggered by multiple threads during the tests.
24 - Both tests were run via jMeter.
26 Stability test script is available in apex-pdp repository:
27 testsuites/apex-pdp-stability/src/main/resources/apexPdpStabilityTestPlan.jmx
29 Performance test script is available in apex-pdp repository:
30 testsuites/performance/performance-benchmark-test/src/main/resources/apexPdpPerformanceTestPlan.jmx
33 Policy executions are validated in a more strict fashion during the tests.
34 There are test cases where upto 80 events are expected on the DMaaP topic.
35 DMaaP simulator is used to keep it simple and avoid any message pickup timing related issues.
37 Stability Test of APEX-PDP
38 ++++++++++++++++++++++++++
43 The 72 hours stability test ran the following steps.
48 Policies are created and deployed to APEX-PDP during this phase. Only one thread is in action and this step is done only once.
50 - **Create Policy onap.policies.apex.Simplecontrolloop** - creates the first APEX policy using policy/api component.
51 This is a sample policy used for PNF testing.
52 - **Create Policy onap.policies.apex.Example** - creates the second APEX policy using policy/api component.
53 This is a sample policy used for VNF testing.
54 - **Deploy Policies** - Deploy both the policies created to APEX-PDP using policy/pap component
59 Once the policies are created and deployed to APEX-PDP by the setup thread, five threads execute the below tests for 72 hours.
61 - **Healthcheck** - checks the health status of APEX-PDP
62 - **Prometheus Metrics** - checks that APEX-PDP is exposing prometheus metrics
63 - **Test Simplecontrolloop policy success case** - Send a trigger event to *unauthenticated.DCAE_CL_OUTPUT* DMaaP topic.
64 If the policy execution is successful, 3 different notification events are sent to *APEX-CL-MGT* topic by each one of the 5 threads.
65 So, it is checked if 15 notification messages are received in total on *APEX-CL-MGT* topic with the relevant messages.
66 - **Test Simplecontrolloop policy failure case** - Send a trigger event with invalid pnfName to *unauthenticated.DCAE_CL_OUTPUT* DMaaP topic.
67 The policy execution is expected to fail due to AAI failure response. 2 notification events are expected on *APEX-CL-MGT* topic by a thread in this case.
68 It is checked if 10 notification messages are received in total on *APEX-CL-MGT* topic with the relevant messages.
69 - **Test Example policy success case** - Send a trigger event to *unauthenticated.DCAE_POLICY_EXAMPLE_OUTPUT* DMaaP topic.
70 If the policy execution is successful, 4 different notification events are sent to *APEX-CL-MGT* topic by each one of the 5 threads.
71 So, it is checked if 20 notification messages are received in total on *APEX-CL-MGT* topic with the relevant messages.
72 - **Test Example policy failure case** - Send a trigger event with invalid vnfName to *unauthenticated.DCAE_POLICY_EXAMPLE_OUTPUT* DMaaP topic.
73 The policy execution is expected to fail due to AAI failure response. 2 notification events are expected on *APEX-CL-MGT* topic by a thread in this case.
74 So, it is checked if 10 notification messages are received in total on *APEX-CL-MGT* topic with the relevant messages.
75 - **Clean up DMaaP notification topic** - DMaaP notification topic which is *APEX-CL-MGT* is cleaned up after each test to make sure that one failure doesn't lead to cascading errors.
81 Policies are undeployed from APEX-PDP and deleted during this phase.
82 Only one thread is in action and this step is done only once after the Main phase is complete.
84 - **Undeploy Policies** - Undeploy both the policies from APEX-PDP using policy/pap component
85 - **Delete Policy onap.policies.apex.Simplecontrolloop** - delete the first APEX policy using policy/api component.
86 - **Delete Policy onap.policies.apex.Example** - delete the second APEX policy also using policy/api component.
89 The following steps can be used to configure the parameters of test plan.
91 - **HTTP Authorization Manager** - used to store user/password authentication details.
92 - **HTTP Header Manager** - used to store headers which will be used for making HTTP requests.
93 - **User Defined Variables** - used to store following user defined parameters.
95 =================== ===============================================================================
96 **Name** **Description**
97 =================== ===============================================================================
98 HOSTNAME IP Address or host name to access the components
99 PAP_PORT Port number of PAP for making REST API calls such as deploy/undeploy of policy
100 API_PORT Port number of API for making REST API calls such as create/ delete of policy
101 APEX_PORT Port number of APEX for making REST API calls such as healthcheck/metrics
102 wait Wait time if required after a request (in milliseconds)
103 threads Number of threads to run test cases in parallel
104 threadsTimeOutInMs Synchronization timer for threads running in parallel (in milliseconds)
105 =================== ===============================================================================
110 The test was run in the background via "nohup", to prevent it from being interrupted:
114 nohup ./apache-jmeter-5.4.1/bin/jmeter.sh -n -t apexPdpStabilityTestPlan.jmx -l stabilityTestResults.jtl
121 Stability test plan was triggered for 72 hours. There were no failures during the 72 hours test.
126 ======================= ================= ================== ==================================
127 **Total # of requests** **Success %** **Error %** **Average time taken per request**
128 ======================= ================= ================== ==================================
129 428661 100 % 0.00 % 162 ms
130 ======================= ================= ================== ==================================
134 There were no failures during the 72 hours test.
136 **JMeter Screenshot**
138 .. image:: apex-s3p-results/apex_stability_jmeter_results.JPG
140 **Memory and CPU usage**
142 The memory and CPU usage can be monitored by running "top" command in the APEX-PDP pod.
143 A snapshot is taken before and after test execution to monitor the changes in resource utilization.
144 Prometheus metrics is also collected before and after the test execution.
146 Memory and CPU usage before test execution:
148 .. image:: apex-s3p-results/apex_top_before_72h.JPG
150 :download:`Prometheus metrics before 72h test <apex-s3p-results/apex_metrics_before_72h.txt>`
152 Memory and CPU usage after test execution:
154 .. image:: apex-s3p-results/apex_top_after_72h.JPG
156 :download:`Prometheus metrics after 72h test <apex-s3p-results/apex_metrics_after_72h.txt>`
158 Performance Test of APEX-PDP
159 ++++++++++++++++++++++++++++
164 Performance test of APEX-PDP is done similar to the stability test, but in a more extreme manner using higher thread count.
169 The performance test is performed on a similar setup as Stability test.
175 Performance test plan is the same as the stability test plan above except for the few differences listed below.
177 - Increase the number of threads used in the Main Phase from 5 to 20.
178 - Reduce the test time to 2 hours.
185 nohup ./apache-jmeter-5.4.1/bin/jmeter.sh -n -t apexPdpPerformanceTestPlan.jmx -l perftestresults.jtl
191 Test results are shown as below.
195 ======================= ================= ================== ==================================
196 **Total # of requests** **Success %** **Error %** **Average time taken per request**
197 ======================= ================= ================== ==================================
198 46946 100 % 0.00 % 198 ms
199 ======================= ================= ================== ==================================
201 **JMeter Screenshot**
203 .. image:: apex-s3p-results/apex_perf_jmeter_results.JPG
208 Multiple policies were executed in a multi threaded fashion for both stability and performance tests.
209 Both tests ran smoothly without any issues.