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
}
}
...
5. OOF Configuration - Policy Creation Steps
Refer Optimization Policy Creation Steps for optimization policy creation and deployment steps
...
Updated slice/service profile mapping - slicing_config.yaml
HAS-API/HAS-DATA - Add data dictionary
Go to (/opt/has/conductor/conductor/data/plugins/inventory_provider/candidates/slice_profiles_candidate.py) addin OOF HAS pod update the following : "max_bandwidth": copy_first, "jitter": sum, "sst": copy_first, "latency": sum, "resource_sharing_level": copy_first, "s_nssai": copy_first, "s_nssai_list": copy_first, "plmn_id_list": copy_first, "plmn_id_List": copy_first, "availability": copy_first, "throughput": min, "reliability": copy_first, "max_number_of_ues": copy_first, "exp_data_rate_ul": copy_first, "exp_data_rate_dl": copy_first, "ue_mobility_level": copy_first, "activity_factor": copy_first, "survival_time": copy_first, "max_number_of_conns": copy_first, "coverage_area_ta_list": copy_first, "max_number_of_pdu_session": copy_first, "max_throughput": copy_first, "perf_req": copy_first, "terminal_density": copy_first update those and restart the container
...
- The service name given for creating the policy must match with the service name in the request
- The scope fields in the policies should match with the value in the resourceSharingLevel(non-shared/shared). Do modify the policy accordingly.
- Check the case of the attributes with the OOF request with the attribute map (camel to snake and snake to camel) in config/slicing_config.yaml, if any mismatch found modify the attribute map accordingly.
You need to restart the OOF docker container once you updated the slicing_config.yaml, you can do it using the following steps,
- Login to the worker VM where the OOF container is running. You can find the worker node by running (kubectl get pods -n onap -o wide | grep dev-oof)
- Find the container using docker ps | grep optf-osdf
- Restart the container using docker restart <container id>
CPS Configuration:
Refer CPS Configuration to setup standalone CPS and configuration of OOF and CPS.
6. External RAN NSSMF Simulator
...
python3 setup.py install --user python3 -m RanNssmfSimulator.MainApp |
Register to ONAP ESR
1. Add an esr-thirdparty-sdnc and esr-system-info to ESR:
Run command: |
---|
curl |
-k - |
X PUT "https://AAI: |
AAI@<worker-vm-ip>:30233/aai/v23/external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/sdnc-an-01 |
Run command:
Example of sdnc-an-01.json: |
---|
{ " \ -H 'Accept: application/json' \ -H 'X-FromAppId: AAI' \ -H 'X-TransactionId: 1' \ -H 'Content-Type: application/json' \ -d '{ "thirdparty-sdnc-id":"sdnc-an-01" } |
2. Add an esr-system-info (RAN NSSMF) to ESR:
, "product-name": "nssmf", "esr-system-info-list |
":{"esr-system-info |
Example of nssmf-an-01.json: |
---|
{ ":[{ "esr-system-info-id": "nssmf-an-01", "system-name": "E2E", "vendor": "huawei", "type": " anan", "user-name": "admin", " vendorpassword": " huawei123456", "system-type": "thirdparty-sdnc", "ip-address": " 192.168.35.83<ip-address-of-simulator>", "port": "8443", " user-name": "admin","password": "123456", " ssl-cacert": "test.ca" }]} }' |
Where, ip-address is the IP address or hostname which runs the External RAN NSSMF Simulator, port is the listening port of RESTful API of the simulator,
user-name and password are set in config file RanNssmfSimulator/etc/auth.json of the simulator.
...
Where, ip-address is the IP address or hostname which runs the External RAN NSSMF Simulator, port is the listening port of RESTful API of the simulator.
9. ACTN Simulator
Refer ACTN Simulator User Guide to setup ACTN-simulator or follow the below steps to launch and initialize domain controllers,
Refer Transport Slicing Configuration and Operation Guidance for NextHop details of AN &CN
Step 1. Fetch the simulator docker image
...
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
curl -k -X PUT "https://AAI:AAI@<worker-vmIp>:30233/aai/v23/external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/ff9ef162-951d-4e14-9ce6-b4fa0adf896b" \ -H 'Accept: application/json' \ -H 'X-FromAppId: AAI' \ -H 'X-TransactionId: 1' \ -H 'Content-Type: application/json' \ -d '{ "thirdparty-sdnc-id":"ff9ef162-951d-4e14-9ce6-b4fa0adf896b", "location": "edge", "product-name": "TSDN", "esr-system-info-list":{"esr-system-info":[{ "esr-system-info-id": "7c29b9df-feef-4fa7-b56d-3e39f5ef4a90", "system-name": "sdnc2", "vendor": "HUAWEI", "type": "WAN", "version": "v1.0", "service-url": "http://<simulator-ip>:<simulator-port>", "user-name": "onos", "password": "rocks", "system-type": "thirdparty_SDNC", "protocol": "restconf" }]} }' |
...