Versions Compared

Key

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

...

  • A1 Controller must be started first to set up docker network
  • Change directory to
    cd nonrtric/sdnc-a1-controller/oam/installation/src/main/yaml
  • Run docker container using the command below  
    docker-compose up a1-controller
    • the container is ready once message "Healthcheck Passed in XX seconds." appears
    • note that certificate-related errors "cp: can't stat '/opt/opendaylight/current/certs/*': No such file or directory" and "Error: File not found in path entered" can be ignored 
  • The Karaf logs of A1 controller can be followed e.g. by using command 
    docker exec a1-controller-container sh -c "tail -f /opt/opendaylight/data/log/karaf.log"

...

  • Start docker containers for each ric defined in nonrtric/policy-agent/config/application_configuration.yaml  in previous steps (in this example for ric1 and ric2) and providing A1 interface version OSC_2.1.0 with the following commands:: 
    docker run -p 8085:8085 -e A1_VERSION=OSC_2.1.0 --network=nonrtric-docker-net --name=ric1 near-rt-ric-simulator:latest
    docker run -p 8086:8085 -e A1_VERSION=OSC_2.1.0 --network=nonrtric-docker-net --name=ric2 near-rt-ric-simulator:latest
  • Change directory to:  
    cd a1-interface/near-rt-ric-simulator/test/OSC_2.1.0/jsonfiles
  • Put an example policy_type into 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/a1-p/policytypes/123" -H "accept: application/json" \
    -H "Content-Type: application/json" --data-binary @pt1.json
    curl -X PUT -v "http://localhost:8086/a1-p/policytypes/123" -H "accept: application/json" \
    -H "Content-Type: application/json" --data-binary @pt1.json

...

  • Run docker container using this command once A1 Controller and simulators have been fully started (see note below)
    docker run -p 8081:8081 --network=nonrtric-docker-net --name=policy-agent-container o-ran-sc/nonrtric-policy-agent:1.0.0-SNAPSHOT

  • Once policy-agent is up and running, it establishes connections to all configured NearRT-RICs
  • If policy-agent-container is configured to log at DEBUG level, the following logs should appear to log to show that connection to the configured RICs has been established successfully via A1 Controller.

...