...
| 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" (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 Jira ticket is opening soon) | ||||||||||
| 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 must be used
| ||||||||||
| 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.
|
Info:
Information about simulators used in the use case:
- External RAN Simulator: External RAN NSSMF
- External Core Simulator: External Core NSSMF Simulator Use Guide
- Transport Simulator: not usedy
- In order to skip
- SDNC workflow for the Transport domain, please follow:
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key SO-3444