You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 26 Next »

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 Honolulu with the following changes:
    • SO
      • bpmn-infra at 1.9.0 (in order to fix UUI Slicing Management Section issue)


or


  • 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.1
      • nssmf-adapter at 1.8.0
      • bpmn-infra at 1.8.0
    • SDNC

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: Tn_ONAP_internal_BH, EmbbAn_NF, EmbbCn_External, CST_O2
  • 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


IssueBrief description of resolutionComponents affectedWorkaroundJira(s)Status
ServiceProfile 
(Onboarding phase)		ServiceProfile_O2 in the wiki misses the step "Declare ar-invariant and ar-uuid as Input" and fill the Activity Factor param with a value (i.e. 20)
(Point 14 of Template Design for Option2)		DOCSDeclare 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
service-model into AAI



NST SelectionOOF returns always an empty solution arrayOOF

OPTFRA-909 - Getting issue details... STATUS

OPTFRA-764 - Getting issue details... STATUS

FIXED


NSI SelectionCamel_to_snake/snake_to_camel schema is wrongOOF

You will need to change several params into slicing_config.yaml file inside OOF container 

A working slicing_config.yaml is :

slicing_config.yaml

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>


NSI SelectionPolicies from WIKI page are wrong. The NSI selection response from OOF does not contain all information in order to create the Slice Management Task properlyDOCS/POLICY

new policies  must be used

policies.zip

and for NSI policies, please use the following:

nsi_policies (3).zip


Follow the points Optimization Policy Creation Steps in order to create and push the new policies (both nsi and nssi).



NSI SelectionsubnetCapability.json file is wrong and it should be updatedDOCS/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.
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


Netconf device not mounted to SDN-R

While starting the Netconf servers (Honeycomb), the device mount should happen automatically. 

org.onap.ransim.rest.client.RestClient.sendMountRequestToSdnr(RestClient.java:241)||Exc in post {}
org.springframework.web.client.HttpClientErrorException$Unauthorized: 401 Unauthorized: [no body]

RANSimulatorUsername and password to connect with SDN-R need be configured properly. Refer gerrit.onap Code Review - integration/simulators/ran-simulator.git/blob - ransim/docker/docker-compose.yml
Fixed
Certificate error in RansimController

PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target; nested exception is javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
        at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:751)
        at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:677)

RANSimulatorUse the jssecacerts cert from sdnc container (var/custom-certs) and place it in ransim package under ransim/docker/config/ransim. It needs  to be replaced as it expires over time.
Fixed

Information about simulators used in the use case:


  • No labels