This page describes how to demonstrate the entire flow from the OSC Non-RT RIC Control-Panel → ONAP A1 Policy Management Service → ONAP A1 Controller in SDNC -> OSC near-RT-RIC/A1 Simulator
Table of Contents
Overview of the End to End call
Details of the architecture can be found from the following link: London Montreal Release
End to End call
From OSC NONRTRIC Control Panel to OSC Near-RT RIC simulator via ONAP A1 Policy Management Service & ONAP A1 Adapter
Preparation
See instructions on configuring & running the A1 Policy functions (londonMontreal).
Perform Policy Operations via Dashboard
Open Dashboard UI at http://localhost:8080/ (or) http://<yourvmip>:8080/
...
An entry to the chosen Near-RT RIC simulator console/log should appear (see, for example, docker logs ric3 in case ric3 policy was created):
127.0.0.1 - - [23/Aug/2023 202x 11:18:56] "PUT //A1-P/v2/policytypes/STD_QOS2_0.1.0/policies/c897eabc-82cb-4bac-baa6-a5dbaef71694 HTTP/1.0" 200 -
Other logs can also be checked, for example is A1-Adapter.log that can be found inside sdnc-controller container, path: /opt/opendaylight/data/logs
...
Modifications are submitted in the same way as in creation, and the resulting simulator log should also be same as the one we saw in creation
127.0.0.1 - - [23/Aug/2023 202x 13:32:09] "PUT //A1-P/v2/policytypes/STD_QOS2_0.1.0/policies/c063a1e3-455a-41a5-b119-c25eadab7fd4 HTTP/1.0" 200 -
...
Confirm deletion and verify the log on simulator side:
127.0.0.1 - - [23/Aug/2023 202x 13:35:22] "DELETE //A1-P/v2/policytypes/STD_QOS2_0.1.0/policies/c063a1e3-455a-41a5-b119-c25eadab7fd4 HTTP/1.0" 204 -