Network Slicing - Issues and Solutions

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"
      }
    ]
  }
}

This page explains the manual configurations required for setting up E2E network slicing use case - option 1.

1. SDC

ONAP Portal: https://portal.api.simpledemo.onap.org:30225/ONAPPORTAL/login.htm (Username:cs0008, Password:demo123456!)

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

In uui-server microservice, modify the following configuration file, /home/UUI/config/slicing.properties

Add or update the parameters slicing.serviceInvariantUuid and parameter slicing.serviceUuid.

The values of these two parameters come from CST template which can be find on SDC page.

3.MSB Configuration

Register so-orchestrationTasks and so-serviceInstances interface to MSB.

Interface registration can be done through portal.

Steps(Portal):

Link: https://{{master server ip}}:30284/iui/microservices/default.html

 1.Select ‘Service Discover’ in the left pane

 2. Click 'Service Register' button.

 3. Input the basic info as the picture shows(also refer to the registration info provided above)

4. Click Add Host button.

    Input IP Address and Port then click the 'SAVE' button. （Use cmd ’kubectl get svc -n onap so‘ to confirm IP and port.）

5.  Input the basic info as the picture shows for so-orchestrationTasks (also refer to the registration info provided above)

6. You should add a  aai-business service for MSB.
Steps:

• Got to msb https://{{master server ip}}:30284/iui/microservices/default.html
• Select "Service Discover" from left panel
• Click "Service Register" button
  • ADD the following info:
    Service Name: aai-business
    Url: /aai/v13/business
    Protocol: REST
    Enable SSL to True
    Version: v13
    Load balancer: round-robin
    Visualranfe: InSystem
  • Add host:
    AAI service ip and port (8443)
• Save all

7. You should add a  aai-externalSystem service for MSB.
Steps:

• Got to msb https://{{master server ip}}:30284/iui/microservices/default.html
• Select "Service Discover" from left panel
• Click "Service Register" button
  • ADD the following info:
    Service Name: aai-externalSystem
    Url: /aai/v11/external-system
    Protocol: REST
    Enable SSL to True
    Version: v11
    Load balancer: round-robin
    Visualranfe: InSystem
  • Add host:
    AAI service ip and port (8443)
• Save all

8. You should add a  aai-network service for MSB.
Steps:

• Got to msb https://{{master server ip}}:30284/iui/microservices/default.html
• Select "Service Discover" from left panel
• Click "Service Register" button
  • ADD the following info:
    Service Name: aai-network
    Url: /aai/v21/network
    Protocol: REST
    Enable SSL to True
    Version: v21
    Load balancer: round-robin
    Visualranfe: InSystem
  • Add host:
    AAI service ip and port (8443)
• Save all

4. SO

Copy subnetCapability.json to SO-API Handler pod to configure subnet capabilities at run time.

You can copy the file to the pod using the following command

SO Database Update

Insert ORCHESTRATION_URI into service_recipe,  SERVICE_MODEL_UUID replaced by CST.ModelId.

Insert ORCHESTRATION_URI into service_recipe,  SERVICE_MODEL_UUID is ServiceProfile.ModelId

5.OOF Configuration

HAS-API/HAS-DATA - Add datadictionary 

Go to (conductor/conductor/data/plugins/inventory_provider/candidates/slice_profiles_candidate.py) 
add the following :
    "max_bandwidth": copy_first,
    "jitter": sum,
    "sst": copy_first,
    "latency": sum,
    "resource_sharing_level": copy_first,
    "s_nssai": copy_first,
    "s_nssai_list": copy_first,
    "plmn_id_list": copy_first,
    "plmn_id_List": copy_first,
    "availability": copy_first,
    "throughput": min,
    "reliability": copy_first,
    "max_number_of_ues": copy_first,
    "exp_data_rate_ul": copy_first,
    "exp_data_rate_dl": copy_first,
    "ue_mobility_level": copy_first,
    "activity_factor": copy_first,
    "survival_time": copy_first,
    "max_number_of_conns": copy_first,
    "coverage_area_ta_list": copy_first,
    "max_number_of_pdu_session": copy_first,
    "max_throughput": copy_first,
    "perf_req": copy_first,
    "terminal_density": copy_first

update those and restart the container

OSDF - Change slicing_config.yaml

• add mapping :

   plmn_id_list: pLMNIdList    plmn_id_List: plmnIdList

• change mapping (remove characther 's'): maxNumberofPDUSessions

  max_number_of_pdu_session: maxNumberofPDUSession 

6. Policy Creation Steps

Refer Optimization Policy Creation Steps for optimization policy creation and deployment steps

policies.zip

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/nsi

python3 policy_utils.py create_policy_types policy_types

python3 policy_utils.py create_and_push_policies nst_policies

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

NOTE:

• The service name given for creating the policy must match with the service name in the request
• The scope fields in the policies should match with the value in the resourceSharingLevel(non-shared/shared). Do modify the policy accordingly.
• Check the case of the attributes with the OOF request with the attribute map (camel to snake and snake to camel) in config/slicing_config.yaml, if any mismatch found modify the attribute map accordingly.

• You need to restart the OOF docker container once you updated the slicing_config.yaml, you can do it using the following steps,

  • Login to the worker VM where the OOF container is running. You can find the worker node by running (kubectl get pods -n onap -o wide | grep dev-oof)
  • Find the container using docker ps | grep optf-osdf
  • Restart the container using docker restart <container id>

  
  

7.AAI Configuration

Create customer id  : 

curl --user AAI:AAI -X PUT -H "X-FromAppId:AAI" -H  "X-TransactionId:get_aai_subscr" -H "Accept:application/json" -H "Content-Type:application/json" -k -d '{ 

"global-customer-id":"5GCustomer", 

"subscriber-name":"5GCustomer", 

"subscriber-type":"INFRA" 

}' "https://<worker-vm-ip>:30233/aai/v21/business/customers/customer/5GCustomer" 

Create service type:

curl --user AAI:AAI -X PUT -H "X-FromAppId:AAI" -H  "X-TransactionId:get_aai_subscr" -H "Accept:application/json" -H "Content-Type:application/json" -k https://<worker-vm-ip>:30233/aai/v21/business/customers/customer/5GCustomer/service-subscriptions/service-subscription/5G 

8.ConfigDB

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://wiki.onap.org/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.

Necessary RAN network functions data are preloaded in config DB while booting the maria DB container.

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

Check the below in SDNC pod (dev-sdnc-0).

1. Change the properties  file  ran-slice-api-dg.properties available at /opt/onap/ccsdk/data/properties/
   1. 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 
   2. 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
   3. 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

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

ACTN Simulator:

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

  • You need to update the sdnc statefulset k8s resource by adding the new env param SDNC_NORTHBOUND = true

    SDNR_NORTHBOUND:                true

    - name: SDNR_NETCONF_CALLHOME_ENABLED
      value: "true"
    - name: SDNR_NORTHBOUND
      value: "true"
    image: nexus3.onap.org:10001/onap/sdnc-image:2.2.1

• Rebuild the SDNC package and redeploy it.

Skipping TN Allocation 

In file oom/kubernetes/so/components/so-bpmn-infra/resources/config/overrides/override.yaml, we add a new config flag:

mso: 
   workflow:
       TnNssmf:
            enableSDNCNetworkConfig: 'false'