This page explains the manual configurations required for setting up E2E network slicing use case - option 1.
...
SDC UUI: https://sdc.api.fe.simpledemo.onap.org:30207/sdc1/portal#!/dashboard
Refer for Template Design for Option 1 respective template creation and distribution.
2.UUI Configuration
Configure CST template UUID and Invariant UUID in slicing.properties file of uui-server microservice
...
6. Policy Creation Steps
Refer Optimization Policy Creation Steps for optimization policy creation and deployment steps
| View file |
|---|
| name | policies.zip |
|---|
| height | 150 |
|---|
|
Copy the policy files
unzip policies.zip
kubectl cp policies -n onap <oof-pod-name>:/opt/osdf
kubectl exec -ti -n onap <oof-pod-name> bash
cd policies/ |
nstnsi
python3 policy_utils.py create_policy_types policy_types
python3 policy_utils.py create_and_push_policies nst_policies
|
cd policies/nsi
python3 policy_utils.py generate_nsi_policies NSTO1
python3 policy_utils.py create_and_push_policies gen_nsi_policies
cd policies/nssi
python3 policy_utils.py generate_nsi_policies TESTRANTOPNSST
python3 policy_utils.py create_and_push_policies gen_nsi_policies
python3 policy_utils.py generate_nssi_policies RAN_NF_NSST minimize latency
python3 policy_utils.py create_and_push_policies gen_nssi_policies
python3 policy_utils.py generate_nssi_policies CN_NSST minimize latency
python3 policy_utils.py create_and_push_policies gen_nssi_policies
|
Refer Policy Models and Sample policies - NSI selection for sample policies
Updated slice/service profile mapping - https://gerrit.onap.org/r/gitweb?p=optf/osdf.git;a=blob;f=config/slicing_config.yaml;h=179f54a6df150a62afdd72938c2f33d9ae1bd202;hb=HEAD
...
Config DB is a spring boot application that works with mariaDB. DB schema details are available at Config DB.
Install config DB application in a separate VM. MariaDB container should be up and running to access the config DB APIs.
Refer https://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/Config+DB+setup for configDB setup. Latest source is available at Image versions, preparation steps and useful info-Config DB Preload Info Section.
...
- 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
Note:
...
- 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
kubectl get configmap -n onap --no-headers=true | awk '/dev-sdnc/{print $1}' | xargs kubectl delete configmap -n onap
kubectl get svc -n onap --no-headers=true | awk '/^sdn/{print $1}' | xargs kubectl delete svc -n onap
kubectl get deployment -n onap --no-headers=true | awk '/dev-sdnc/{print $1}' | xargs kubectl delete deployment -n onap
kubectl get statefulsets -n onap --no-headers=true | awk '/dev-sdnc/{print $1}' | xargs kubectl delete statefulsets -n onap
kubectl get jobs -n onap --no-headers=true | awk '/dev-sdnc/{print $1}' | xargs kubectl delete jobs -n onap
kubectl get pvc -n onap --no-headers=true | awk '/dev-sdnc/{print $1}' | xargs kubectl delete pvc -n onap
kubectl get pv -n onap --no-headers=true | awk '/dev-sdnc/{print $1}' | xargs kubectl delete pv -n onap
kubectl get secrets -n onap --no-headers=true | awk '/dev-elastic/{print $1}' | xargs kubectl delete secrets -n onap
kubectl get configmap -n onap --no-headers=true | awk '/dev-elastic/{print $1}' | xargs kubectl delete configmap -n onap
kubectl get svc -n onap --no-headers=true | awk '/^elastic/{print $1}' | xargs kubectl delete svc -n onap
kubectl get deployment -n onap --no-headers=true | awk '/dev-elastic/{print $1}' | xargs kubectl delete deployment -n onap
kubectl get statefulsets -n onap --no-headers=true | awk '/dev-elastic/{print $1}' | xargs kubectl delete statefulsets -n onap
kubectl get jobs -n onap --no-headers=true | awk '/dev-elastic/{print $1}' | xargs kubectl delete jobs -n onap
kubectl get pvc -n onap --no-headers=true | awk '/dev-elastic/{print $1}' | xargs kubectl delete pvc -n onap
kubectl get pv -n onap --no-headers=true | awk '/dev-elastic/{print $1}' | xargs kubectl delete pv -n onap
kubectl get secrets -n onap --no-headers=true | awk '/dev-neng/{print $1}' | xargs kubectl delete secrets -n onap
kubectl get configmap -n onap --no-headers=true | awk '/dev-neng/{print $1}' | xargs kubectl delete configmap -n onap
kubectl get svc -n onap --no-headers=true | awk '/^neng/{print $1}' | xargs kubectl delete svc -n onap
kubectl get deployment -n onap --no-headers=true | awk '/dev-neng/{print $1}' | xargs kubectl delete deployment -n onap
kubectl get statefulsets -n onap --no-headers=true | awk '/dev-neng/{print $1}' | xargs kubectl delete statefulsets -n onap
kubectl get jobs -n onap --no-headers=true | awk '/dev-neng/{print $1}' | xargs kubectl delete jobs -n onap
kubectl get pvc -n onap --no-headers=true | awk '/dev-neng/{print $1}' | xargs kubectl delete pvc -n onap
kubectl get pv -n onap --no-headers=true | awk '/dev-neng/{print $1}' | xargs kubectl delete pv -n onap
kubectl delete secret -n onap dev-aai-keystore
kubectl delete secret -n onap dev-pol-basic-auth-secret
kubectl get configmap -n onap --no-headers=true | awk '/dev-sdnr/{print $1}' | xargs kubectl delete configmap -n onap
kubectl get pvc -n onap --no-headers=true | tail -n+2 | awk '/dev-sdn/{print $1}' | xargs kubectl patch pvc -n onap -p '{"metadata":{"finalizers":null}}'
kubectl get deployment -n onap --no-headers=true | awk '/dev-sdn/{print $1}' | xargs kubectl delete deployment -n onap
kubectl delete deployment -n onap dev-network-name-gen
kubectl get statefulsets -n onap --no-headers=true | awk '/dev-sdnr/{print $1}' | xargs kubectl delete statefulsets -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
kubectl delete pv -n onap dev-sdnrdb-master-pv-1 --grace-period=0 --force
kubectl delete pv -n onap dev-sdnrdb-master-pv-2 --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.
...
This Simulator section is bypassed and a workaround is used to continue the flow. Workaround is done in the SDNC DG. <>
ranSliceApi not deployed into SDNC
This issue occurs because you need to set the env SDNR_NORTHBOUND=true for the sdnc-image. This is by default set to false. With this flag all sdnr-northbound features are installed during startup.
How to fix it?
- Setting env into SDNC HELM CHART
- Rebuild the SDNC package and redeploy it.