This page describes how to demonstrate the entire flow from Non-Rt RIC Controlpanel -> Policy Agent -> (A1 controller in SDNC) -> Near Realtime Ric Simulator. Optionally A1 controller can be left out.
Details of the architecture can be found from the following link: Release A
See Release A - Build/Run for building and starting the environment.
Either option A or B can be setup and all end to end actions from Dashboard should work same way.
172.18.0.3 - - [02/Apr/2020 07:33:57] "PUT /A1-P/v1/policies/ac3e914a-b39c-4d93-b77c-d2ebac756267?policyTypeId=STD_QoSNudging_0.2.0 HTTP/1.1" 201 -
172.18.0.3 - - [02/Apr/2020 07:51:19] "PUT /A1-P/v1/policies/ac3e914a-b39c-4d93-b77c-d2ebac756267?policyTypeId=STD_QoSNudging_0.2.0 HTTP/1.1" 201 -
172.18.0.3 - - [02/Apr/2020 08:02:21] "DELETE /A1-P/v1/policies/ac3e914a-b39c-4d93-b77c-d2ebac756267 HTTP/1.1" 204 -
Limited tests to verify just OSC CCSDK A1 Controller calls towards NearRT-RIC simulator can be done by using ODL GUI. Dashboard and policy-agent are not needed in this case.
See Release A - Build/Run for building and starting the environment. If following those instructions, just skip the following steps:
Now only "a1-controller-container" and "sdnc_db_container" and simulators are running.
Payload
{ "A1-ADAPTER-API:input": { "near-rt-ric-url": "http://ric1:8085/" } } |
Payload
{ "A1-ADAPTER-API:input": { "near-rt-ric-url": "http://ric1:8085/", "policy-id": "my-policy-instance1", "policy-type-id": "STD_QoSNudging_0.2.0", "policy": '{ "scope": { "qosId": "999", "ueId": "5001" }, "statement": { "priorityLevel": 5 } }' } } |
Payload
{ "A1-ADAPTER-API:input": { "near-rt-ric-url": "http://ric1:8085/" } } |