DRAFT - Copy of Release E

This wiki describes how to deploy the NONRTRIC components within Kubernetes cluster.

...

1. Control Panel
2. Policy Management Service
3. Information Coordinator Service
4. Non RT RIC Gateway (reuse of existing kong proxy is also possible)
5. R-App catalogue Service
6. NearRT RIC A1 Simulator (3 A1 interface versions - previously called Near-RT RIC A1 Interface)
7. A1 Controller (currently using SDNC from ONAP)
8. Helm Manager
9. Dmaap Adapter Service
10. Dmaap Mediator Service
11. Use Case rApp O-DU Slice Assurance
12. Use Case rAPP O-RU Closed loop recovery

...

• Verify the PMS logs to make sure that the connection between PMS and a1controller is successful. 

  • Command to check pms logs

    Code Block
    language bash title Kubernetes command to get PMS logs
    kubectl logs policymanagementservice-0 -n nonrtric

    
    

  • Command to enable debug logs in PMS (Command below should be executed inside k8s pods or the host address needs to be updated with the relevant port forwarding)

    Code Block
    language bash title Enabling debug logs in PMS
    curl --request POST \ --url http://policymanagementservice:9080/actuator/loggers/org.onap.ccsdk.oran.a1policymanagementservice \ --header 'Content-Type: application/json' \ --data '{ "configuredLevel": "DEBUG" }'

    
    

• Try removing the controller information in specific simulator configuration and verify the simulator are working without a1controller.

  Code Block
  language bash title application_configuration.json collapse true
  ... { "name":"ric1", "baseUrl":"https://a1-sim-osc-0.a1-sim:8185", "managedElementIds":[ "kista_1", "kista_2" ] }, ...

  
  

• Curl can be used in control panel pod.

...