The 72 hour Stability Test for APPC has the goal of introducing a steady flow of transactions initiated from a Test Client server running JMeter. The transactions will be submitted through a DMaaP (Message Router) instance where APPC will pick up and process those requests. The JMeter test will look for a synchronous ACCEPT response to the request along with an waiting for an asynchronous response from APPC (SUCCESS or FAILURE). The initial testing will consist of three generic VMs running Ubuntu instantiated in the WindRiver OpenStack environment. The JMeter testing will exercise the following LCM API Actions:
- VM Restart
- VM Stop
- VM Start
- VM Restart
The 72 hour test will loop through these actions and VMs for the duration of the 72 hour window.
The test is divided up into 3 tests across 3 VMs:
- Stability-Test-VM1 LCM Group (Restart VM)
- Stability-Test-VM2 LCM Group (Stop VM & Start VM)
- Stability-Test-VM3 LCM Group (Rebuild VM)
Each of these tests has an accompanying csv file containing data for the test. The csv files have the following information:
DMaaP IP, APPC LCM READ Topic name, APPC LCM WRITE Topic name, VNF ID, VM ID
The test itself can be set to loop indefinitely or a set number of loops. The LCM action request is submitted from the Test Client server to DMaaP where APPC picks up the request. APPC will send back an ACCEPT or REJECT for the request in a synchronous fashion. However, the response for the completed action (SUCCESS or FAILURE) is returned in an asynchronous fashion. The JMeter test is developed in such a way that it polls (Does a GET) DMaaP checking for the presence of the response based on the request_id. If the response is not receive ed within a set time the Async Listener will timeout.
Additionally, The JMeter Performance Monitor (jpgc-perfmon-2.1) is installed on the APPC VM in order to gather metrics on the APPC VM itself.
The JMeter test can be kicked off via the following command "nohup ./jmeter.sh -n -t ../APPC-LCM-Action-V1.jmx -l ../APPC-LCM-Action-V1.jtl > /dev/null 2>&1 &" the loops within the test are set to run indefinitely. Therefore, the test will execute until the process is killed. The test output is logged in the APPC-LCM-Action.V1.jtl file.