Versions Compared

Old Version 26

changes.mady.by.user Alexander Dehn

Saved on

compared with

New Version 27

changes.mady.by.user Bruno Lainé

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

250



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

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

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyOPTFRA-909

Jira
serverONAP Jira
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyOPTFRA-764

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 :

View file
nameslicing_config.yaml
height250


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



View file
namepolicies.zip
height250
and for NSI policies, please use the following:
View file
namensi_policies (3).zip
height

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

...