ONAP Benchmark Project Progress August 7 th 2018

ONAP Benchmark Project Progress August 7 th, 2018

Problems we came across • Resiliency test • Deploy vcpe again, encounter a new error: "status. Message": "Received vf. Module. Exception from Vnf. Adapter: category='INTERNAL' message='Exception during create VF 0 : Stack error (CREATE_FAILED): Resource CREATE failed: Forbidden: resources. my_keypair : Quota exceeded, too many key pairs. (HTTP 403) (Request-ID: req-c 6 cab 791 -255 c-4 ec 8 -aa 0 c-e 89 aa 0 e 43345) 'rolled. Back='true'". • The new error has been submitted to the onap mail group and Xi Kang.

Problems we came across • Scalability test Modify vfw's demo_artifacts_version to 1. 3. 0, Vfw vm can see the. /vpp_measurement_reporter 10. 0. 4. 1 8080 eth 1 process, However, after re-executing. /update-vfw-op-policy. sh policy. api. simpledemo. onap. org 251 fcdb 1 -c 8 e 2 -479 d 8 d 14 -e 627 d 42 c 53 d 5 ~/. ssh/id_rsa command, found an error:

Test Schedule N O TASK 1 Test Target & Test Scope 2 Environment v. CPE E 2 E Test Cases v. CPE Test 4 Indexes COMPLETION TIME PLANNED ACTUAL COMPLETION TIME 2018/4/20 We chose S 3 P of v. CPE as test scope Closed a) Infrastructure & Environment 2018/4/25 2018/4/27 The required environment to run test cases has been set up and configured Closed b) v. CPE Deployment 2018/5/1 2018/7/1 2018/5/1 2018/6/4 SUB TASK 3 5 Test Tools 6 Test Cases Running 7 Case AT Output (Test Report, Test 8 Document, etc. ) a) Southbound Simulator i. Openstack ii. Vnfm iii. Openflow Adapter v. BRG, v. BNG, v. GMUX, and Vgw (Cloud. Stress, Avalanche) b) Stress Test c) Performance Monitor PROGRESS 2018/06/14: We installed the latest R 2, and passed all the health check. Problems during installation were solved. However, we cannot run the v. FW and v. CPE test cases. 2018/6/4: 100% of the test cases have been finished till today. 2018/5/8: 30% of the test cases have been finished till today. STATUS Closed 2018/4/23 Not yet started Suspend 2018/5/1 2018/6/4 2018/6/04: Tools are ready to use. 2018/5/10: We are adjusting the topology of Metric to effectively monitor the resource consumption of core modules, and coordinating Smart. Bit. 2018/5/8: We completed the installation of Cloud. Stress and Metric and the debugging of hardware. Tomorrow we will release it to the Beijing Research Institute. Closed 2018/5/1 Preliminarily we determined to use opensource tools: Tsung/JMeter/Locust+Avalanche Use Linux opensource tools: Sar/htop/Dstat/Glances Closed Resiliency 2018/5/11 See in next slides Open Performance & Stability 2018/5/11 See in next slides Open Scalability 2018/5/11 See in next slides Open 2018/5/15 Open 2018/5/18 Open

Test Schedule TASK FINISH ED Test Cases Running PROGRESS STATUS resiliency 30% 2018/08/07: Liu Chenglong: 1. Redeploy the vcpe use case. 2. After the deployment, it was found that kea-sdnc-notify. so did not work. Consulted Xikang and found that the local kea-dhcp 4 service was not installed and deployed. 3. Clean up the vcpe data and delete the stack and instance data. 4. Deploy vcpe again, encounter a new error: "status. Message": "Received vf. Module. Exception from Vnf. Adapter: category='INTERNAL' message='Exception during create VF 0 : Stack error (CREATE_FAILED): Resource CREATE failed: Forbidden: resources. my_keypair : Quota exceeded, too many key pairs. (HTTP 403) (Request-ID: req-c 6 cab 791 -255 c-4 ec 8 -aa 0 c-e 89 aa 0 e 43345) 'rolled. Back='true'". 5. The new error has been submitted to the onap mail group and Xi Kang. Sun Xinlong: 1. Read the mso code content 2. Recreate brg vgw, analyze the running results and print content, compare the code, and analyze the code structure. Open Performance 10% 2018/08/07: 1. Use wireshark to capture the signaling interaction between so and openstack twice. 2. In-depth understanding of the vcpe code, in fact, the signaling interaction process between robot and openstack (as shown in the left) is the following part of the vcpe code execution process: nova --os-auth-url http: //172. 30. 3. 10: 5000 --os-project-domain-name onap_r 2 --os-password zhangzhch --os-region-name Region. One --os-username zhangzhch --os-user-domain-id default --os-tenant-id B 45461 e 4 b 03547 db 8 f 2869 d 2 c 9 f 9 e 29 e --os-project-domain-id default list. 3. Started to simulate the interaction between robot and openstack (python write), the code is not completed yet. Open Stability 10% Scalability 10% Open 2018/08/07: 1. Solved the problem pkg can not send a package 2. A problem mentioned before. Open

Thanks