Versions Compared

Key

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

This page describes how to get the release A version of NonRTRIC up and running locally with two separate NearRT-RIC simulator docker containers.

...

  • Download the nonrtric repo: 
     git clone "https://gerrit.o-ran-sc.org/r/nonrtric" -b Amber
  • To support local test with two separate NearRT-RIC simulator instances the following modifications must be done:  
    • change the 'a1ControllerBaseUrl' in nonrtric/policy-agent/config/application.yaml file of policy-agent to http://a1-controller-container:8181 
      • The above hostname and port values come from and must match those defined in nonrtric/sdnc-a1-controller/oam/installation/src/main/yaml/docker-compose.yml
      • The default URL to be replaced (http://sdnc.onap:8282) is used in Kubernetes-based ONAP deployment
    • The following step is required only if you want to run more than the default ric1 nearRT-RIC simulator instance
      • replace the content of nonrtric/policy-agent/config/application_configuration.yaml with the
      following:
      • configuration below
      • any defined ric names must match the given docker container names in nearRT-RIC simulator startup - port is always the simulator's internal 8085

Code Block
languageyml
titleapplication_configuration.yaml
{
   "config": {
      "//description": "Application configuration",
      "ric": [
         {
            "name": "ric1",
            "baseUrl": "http://ric1:8085/",  
            "managedElementIds": [
               "kista_1",
               "kista_2"
            ]
         },
         {
            "name": "ric2",
            "baseUrl": "http://ric2:8085/",
            "managedElementIds": [
               "kista_3",
               "kista_4"
            ]
         }
      ]
   }
}

...

Run Near-RT-RIC Simulator Docker Containers

  • Start two docker containers using following commandsfor each ric defined in nonrtric/policy-agent/config/application_configuration.yaml  in previous steps using following commands (in this example for ric1 and ric2)
    docker run -p 8085:8085 --network=nonrtric-docker-net --name=ric1 o-ran-sc/near-rt-ric-simulator:1.0.1-SNAPSHOT
    docker run -p 8086:8085 --network=nonrtric-docker-net --name=ric2 o-ran-sc/near-rt-ric-simulator:1.0.1-SNAPSHOT
  • Change directory to:  
    cd nonrtric/near-rt-ric-simulator/ric-plt/a1
  • Put an example policy_type into all the started near-rt-ric-simulator instances by running these curl commands (in this example to ric1 exposed to port 8085 and ric2 exposed to port 8086):
    curl -X PUT -v "http://localhost:8085/policytypes/STD_QoSNudging_0.2.0" -H "accept: application/json" \
    -H "Content-Type: application/json" --data-binary @policy_type_STD_QoSNudging_0.2.0.json


    curl -X PUT -v "http://localhost:8086/policytypes/STD_QoSNudging_0.2.0" -H "accept: application/json" \
    -H "Content-Type: application/json" --data-binary @policy_type_STD_QoSNudging_0.2.0.json

...