...
We tested the use case with the following OOM configuration:
- oom Honolulu with the following changes:
- SO
- bpmn-infra at 1.9.0 (in order to fix UUI Slicing Management Section issue)
- SO
or
- oom master from 09-02-2021 (it should be good all version with AAI v23 enabled) with the following changes:
- AAI (v23 schema should be enabled):
- aai-schema-service 1.8.6
- aai-traversal at 1.8.0
- SO
- api handler infra at 1.8.1
- nssmf-adapter at 1.8.0
- bpmn-infra at 1.8.0
- SDNC
- sdnc-image version 2.1.1
- For specifics on Transport Slicing Configuration and Operation Guidance, refer to: Transport Slicing Configuration and Operation Guidance.
- AAI (v23 schema should be enabled):
...
Issue | Brief description of resolution | Components affected | Workaround | Jira(s) | Status | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ServiceProfile (Onboarding phase) | ServiceProfile_O2 in the wiki misses the step "Declare ar-invariant and ar-uuid as Input" and fill the Activity Factor param with a value (i.e. 20) (Point 14 of Template Design for Option2) | DOCS | Declare them as input | ||||||||||||||
AAI Distribution Fails (Onboarding phase) | Distribution fails into AAI for the resources SliceProfileXXX (missing Allotted Resource service model) | AAI | Add Slice_AR (the allotted resource componing each SliceProfile) as | ||||||||||||||
NST Selection | OOF returns always an empty solution array | OOF |
| FIXED | |||||||||||||
NSI Selection | Camel_to_snake/snake_to_camel schema is wrong | OOF | You will need to change several params into slicing_config.yaml file inside OOF container A working slicing_config.yaml is :
You need to restart the OOF docker container once you updated the slicing_config.yaml, you can do it using the following steps,
| ||||||||||||||
NSI Selection | Policies from WIKI page are wrong. The NSI selection response from OOF does not contain all information in order to create the Slice Management Task properly | DOCS/POLICY | new policies policies must be used
and for NSI policies, please use the following:
| ||||||||||||||
NSI Selection | subnetCapability.json file is wrong and it should be updated | DOCS/SO | Point 4 of Install Minimum Scope for Option 1 change subnetCapability.json file as following: { "AN": { "latency": 5, "maxNumberofUEs": 10, "maxThroughput": 150, "termDensity": "50" }, "CN": { "latency": 1, "maxThroughput": 5, "maxNumberofConns": 6000 }, "TN_FH": { "latency": 10, "maxThroughput": "100" }, "TN_MH": { "latency": 5, "maxThroughput": "50" }, "TN_BH": { "latency": 10, "maxThroughput": 100 }, "AN_NF": { "latency": 5, "maxNumberofUEs": 100, "maxThroughput": "150", "termDensity": "50" } } | ||||||||||||||
UUI does not display "CommunicationService" and"SlicingResouce Management" items | In the UUI, in "5G Slicing Management" Section, "Communication Service" and "Slicing Resource Management" items are not retrieved from AAI returning 500 Server error with message: "5G slicing order query failed! | MSB | You should add a new service for MSB.
| ||||||||||||||
Netconf device not mounted to SDN-R | While starting the Netconf servers (Honeycomb), the device mount should happen automatically. org.onap.ransim.rest.client.RestClient.sendMountRequestToSdnr(RestClient.java:241)||Exc in post {} | RANSimulator | Username and password to connect with SDN-R need be configured properly. Refer gerrit.onap Code Review - integration/simulators/ran-simulator.git/blob - ransim/docker/docker-compose.yml | Fixed | |||||||||||||
Certificate error in RansimController |
| RANSimulator | Use the jssecacerts cert from sdnc container (var/custom-certs) and place it in ransim package under ransim/docker/config/ransim. It needs to be replaced as it expires over time. | Fixed |
...