| commit | aeceb842d144b7676eaf718de0a93f1617fca8d8 | [log] [tgz] |
|---|---|---|
| author | Girish Gowdra <girish@opennetworking.org> | Fri Aug 21 12:10:39 2020 -0700 |
| committer | Girish Gowdra <girish@opennetworking.org> | Mon Aug 24 13:43:06 2020 -0700 |
| tree | 67b8cdea6cbcb5eef8428cc06c645ff75b281db1 | |
| parent | c3d08cdafe3d3eda750658265360358e8b68e01b [diff] |
VOL-3431: Following enhancement/changes are done in this patch - Process ONUs in bulk rather than serial, significantly improves run time - Used a separate API to get flow-id. This flow-id is not freed on failure, as this adds to unnecessary complexity and unwarranted for a test tool . - Print the total execution time at the end of the test - Fixed the Dockerfile to not build vendor module at each docker build time - Introduced new functions to retry scheduler, queue and flow adds on failure, but these are not currently used - Add vendor modules to repo just like all other ONF VOLTHA golang projects do - Tested all three workflows - ATT, DT and TT - Bump version to 1.1.0 Change-Id: I6102cb206e78ea04b49b7125b101946ca6f36bfb
This is used for scale testing of OpenOLT Agent + BAL (or other underlying platform)
The proposed design is here https://docs.google.com/document/d/1hQxbA8jvG1BEHeeLkM5L3sYrvgJUX7z2Tk7j1sPdd1s
make build
Make sure openolt-agent and dev_mgmt_daemon are running. Then run the below command from openolt-scale-tester folder.
DOCKER_HOST_IP=<your-host-ip-here> OPENOLT_AGENT_IP_ADDRESS=<olt-ip-address-here> TAG=<docker-tag-here> docker-compose -f compose/openolt-scale-tester.yml up -d
Lets say your workflow name is XYZ, and the techprofile IDs needed by your workflow is 64 (there could be more than one techprofiles too). Create XYZ-64.json file with your techprofile in tech_profiles folder. Edit the compose/openolt-scale-tester.yml file to reflect your workflow name, i.e., XYZ for parameter --workflow_name.
Create xyz_workflow.go (see sample att_workflow.go) which complies to WorkFlow interface defined in workflow_manager.go file and complete the implementation.
If there are more than one techprofiles needed by your workflow, then you need to create as many techprofiles with appropriate name as described above. Edit the compose/openolt-scale-tester.yml file, parameter --tp_ids with comma separated techprofile IDs.
Below parameters are currently configurable from compose/openolt-scale-tester.yml file.
openolt_agent_ip_address [default: 10.90.0.114] openolt_agent_port [default: 9191] openolt_agent_nni_intf_id [default: 0] num_of_onu [default: 128] subscribers_per_onu [default: 1] workflow_name [default: ATT] time_interval_between_subs [default: 5] kv_store_host[default: 192.168.1.11] kv_store_port [default: 2379] tp_ids [ default: 64]
The following are known issues and limitations with the openolt-scale-tester tool.