...
Issue Description | Option1/Option2 | Solution/Work around | JIRA | Status | Comments |
---|---|---|---|---|---|
"Connection to ASDC server failed" in SO and AAI logs after re-distribution of templates in SDC. | Option 2 | Redeploy SO and AAI with the latest charts. | |||
NST Selection Failure | Option 2 | NST template in SDC should have the property "latency" as a separate property of type integer instead of type NSCapabilities. | |||
Distribution fails into AAI for the resources SliceProfileXXX (missing Allotted Resource service model) | Option 1 | Add Slice_AR (the allotted resource componing each SliceProfile) as service-model into AAI PUT https://{{k8s}}:30233/aai/v21/service-design-and-creation/models/model/5d179b7a-8d8a-4317-9318-349b09fcde2c { "model-invariant-id": "5d179b7a-8d8a-4317-9318-349b09fcde2c", "model-type": "Resource", "model-vers": { "model-ver": [ { "model-version-id": "3c532edd-4c72-4558-b892-8d518ca03c56", "model-name": "Slice_AR", "model-version": "1.0" } ] } } | |||
CDS cba package error (during Core allocation) | Option 1 | Change cds blueprint-processor image to onap/ccsdk-blueprintsprocessor:1.1.4 | |||
This page explains the manual configurations required for setting up E2E network slicing use case - option 1.
...
Note: Refer the latest templates from gerrit which are committed in June 2021. https://gerrit.onap.org/r/gitweb?p=ccsdk/distribution.git;a=commit;h=8b86f34f6ea29728e31c4f6799009e8562ef3b6f
9. SDNC
Install SDNC using OOM charts and the below pods should be running. As ran-slice RPCs are not visible in the latest SDN-C image, use the image version 2.1.0 for sdnc-image and dmaap listener. Manually, load the RANSlice DGs like below:
- Copy the DG XMLs from /distribution/platform-logic/ran-slice-api/src/main/xml (gerrit repo) to /opt/onap/sdnc/svclogic/graphs/ranSliceapi(sdnc container)
- Install the DGs : a) Navigate to /opt/onap/sdnc/svclogic/bin (Sdnc container) (b) Run ./install.sh
SDNC Pods
...
kubectl get pods -n onap | grep sdnc
dev-sdnc-0 2/2 Running 0 46d
dev-sdnc-ansible-server-6b449f8d8-7mjld 1/1 Running 0 46d
dev-sdnc-dbinit-job-mwr8s 0/1 Completed 0 46d
dev-sdnc-dgbuilder-86c9cb55bb-svcsh 1/1 Running 0 46d
dev-sdnc-dmaap-listener-6bd7fbc64f-dl4ch 1/1 Running 0 46d
dev-sdnc-sdnrdb-init-job-824vl 0/1 Completed 0 46d
dev-sdnc-ueb-listener-769f74cb4b-wgcw7 1/1 Running 0 46d
dev-sdnc-web-5b75c68fd8-zfsn6 1/1 Running 0 46d
Check the below in SDNC pod (dev-sdnc-0).
- Change the properties file ran-slice-api-dg.properties available at /opt/onap/ccsdk/data/properties/
- Enable Configdb = true at https://gerrit.onap.org/r/gitweb?p=ccsdk/distribution.git;a=blob;f=odlsli/src/main/properties/ran-slice-api-dg.properties;h=eac71569b301c6c375b68cd2efe234959687ef64;hb=refs/heads/master#l6
- Disable cps= false at https://gerrit.onap.org/r/gitweb?p=ccsdk/distribution.git;a=blob;f=odlsli/src/main/properties/ran-slice-api-dg.properties;h=eac71569b301c6c375b68cd2efe234959687ef64;hb=refs/heads/master#l7
- Update the configdb ip address, according your env at https://gerrit.onap.org/r/gitweb?p=ccsdk/distribution.git;a=blob;f=odlsli/src/main/properties/ran-slice-api-dg.properties;h=eac71569b301c6c375b68cd2efe234959687ef64;hb=refs/heads/master#l158
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Check the below in SDNC pod (dev-sdnc-0).
- Latest ran-slice-api-dg.properties (/distribution/odlsli/src/main/properties/ran-slice-api-dg.properties) should be available at /opt/onap/ccsdk/data/properties/
- All ranSlice*.json template files (/distribution/platform-logic/restapi-templates/src/main/json) should present at /opt/onap/ccsdk/restapi/templates/
- DG XML files from /distribution/platform-logic/ran-slice-api/src/main/xml should present at /opt/onap/sdnc/svclogic/graphs/ranSliceapi
- Go to /opt/onap/sdnc/svclogic/bin
Run ./install.sh << this should re-install and activate all DG's>>
Note:
If SDN-C deletion is unsuccessful due to the leftover residues, use the below commands to delete it completely.
Expand | ||
---|---|---|
| ||
kubectl get secrets -n onap --no-headers=true | awk '/dev-sdnc/{print $1}' | xargs kubectl delete secrets -n onap to delete PV: kubectl get pv -n onap --no-headers=true | tail -n+2 | awk '/dev-sdn/{print $1}' | xargs kubectl patch pv -n onap -p '{"metadata":{"finalizers":null}}' kubectl delete pv -n onap dev-sdnrdb-master-pv-0 --grace-period=0 --force |
DMAAP Messages
Refer SDN-R_impacts for Dmaaps messages that can be used as an SDN-R input for RAN slice instantiation, modification, activation, deactivation and termination.
ACTN Simulator:
This Simulator section is bypassed and a workaround is used to continue the flow. Workaround is done in the SDNC DG. <>
...