The following fixes were tested on scenario 2 (e.g. External NSSMFs), non-shared slice.
We tested the use case with the following OOM configuration:
- 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.0-20210305T0423
- nssmf-adapter at 1.8.0
- bpmn-infra at 1.8.0-20210210T0420
- AAI (v23 schema should be enabled):
For configuration, we used the instructions reported in points 2, 3, 4, 5, 6, 7 at Install Minimum Scope for Option 1
For onboarding phase, plese use this guide Template Design for Option2 with the following fix:
- Fill in the "Service Role" field with the value "ONAP_internal" (in the General section, in SDC ) for the resources: Tn_ONAP_internal_BH
- Fill in the "Service Role" field with the value "huawei" (in the General section, in SDC ) for the resources: EmbbCn_External, EmbbAn_NF
- Fill in the "Service Role" field with the value "option2" (in the General section, in SDC ) for the resources: EmbbNst_O2
- Fill in the "Service Type" field with the value "embb" (in the General section, in SDC ) for the resources: EmbbAn_NF, EmbbCn_External
- Fill in the "Vendor Name" field with the value "huawei" (in the General section, in SDC ) for the resources: EmbbCn_External_AR, EmbbAn_NF_AR
| 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 | OPTFRA-909 - Getting issue details... STATUS | 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"
}
} |
Info:
- Skip SDNC workflow for the Transport domain: SO-3444 - Getting issue details... STATUS