Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

1. UUI Configuration

...

Copy subnetCapability.json to SO-API Handler pod to configure subnet capabilities at run time.

Sample subnetCapability.json

{
"AN_NF": {
"latency": 5,
"maxNumberofUEs": 200,
"maxThroughput": 90,
"termDensity": 40
},
"AN": {
"latency": 20,
"maxNumberofUEs": 100,
"maxThroughput": 150,
"termDensity": 50
},
"CN": {
"latency": 10,
"maxThroughput": 50,
"maxNumberofConns": 100
},
"TN_FH": {
"latency": 10,
"maxThroughput": 90
},
"TN_MH": {
"latency": 5,
"maxThroughput": 90
},
"TN_BH": {
"latency": 10,
"maxThroughput": 100
}
}

...

unzip policies.zip

kubectl cp policies -n onap <oof-pod-name>:/opt/osdf

kubectl exec -ti -n onap <oof-pod-name> bash

cd policies/nsi

python3 policy_utils.py create_policy_types policy_types

python3 policy_utils.py create_and_push_policies nst_policies

python3 policy_utils.py generate_nsi_policies NSTO1

python3 policy_utils.py create_and_push_policies gen_nsi_policies

cd policies/nssi

python3 policy_utils.py generate_nsi_policies TESTRANTOPNSST

python3 policy_utils.py create_and_push_policies gen_nsi_policies

python3 policy_utils.py generate_nssi_policies RAN_NF_NSST minimize latency

python3 policy_utils.py create_and_push_policies gen_nssi_policies

python3 policy_utils.py generate_nssi_policies TN_FH_NSST  minimize latency

python3 policy_utils.py create_and_push_policies gen_nssi_policies

python3 policy_utils.py generate_nssi_policies TN_MH_NSST  minimize latency

python3 policy_utils.py create_and_push_policies gen_nssi_policies

python3 policy_utils.py generate_nssi_policies TN_BH_NSST  minimize latency

python3 policy_utils.py create_and_push_policies gen_nssi_policies

python3 policy_utils.py generate_nssi_policies CN_NSST minimize latency

python3 policy_utils.py create_and_push_policies gen_nssi_policies

...

Install config DB application in a separate VM. MariaDB container should be up and running to access the config DB APIs.

Refer https://wiki.onap.org/display/DW/Config+DB+setup for configDB setup. Latest source is available at Image versions, preparation steps and useful info-Config DB Preload Info Section.

...

  1. Restart datalake-feeder container after loading above configurations in the DB.

POLICY :

     The following policies are to be included for the OOF optimisation based on resource occupancy . Refer Optimization Policy Creation Steps for optimization policy creation and deployment steps.

View file
nameresource-occupancy-policies.zip
height150

RANSIM :

  1. RANSIM and honeycomb containers should be running
  2. You can update/add/delete data(throughput, PRBs, maxNoConns etc) in mariadb container(credentials in docker-compose file) if required before generation of PM data.
  3. RANSIM must contain 'plmninfo' of the service which is to be shared with other services. Then generate closed-loop PM data which will be stored in mongo-db by datalake-feeder.
  4. Sample closed loop data: closed-loop-data.txt
  5. Run the following command to generate Closed Loop PM data:
    1. curl -X POST http://localhost:8081/ransim/api/generateClosedLoopPmData -i
  6. Run the following command to stop Closed Loop PM data(When enough PM data is generated): 
    1. curl -X GET http://localhost:8081/ransim/api/stopClosedLoopPmData -i
  7. Access the DU honeycomb containers to view the logs:
    1. docker container logs -f 110
  8. Check the folder(where SFTP setup is done) to view the generated PM data files.
  9. Access VES, data file collector, dmaap-dr, PM mapper and slice-analysis logs to verify.

...