This user guide explains how to launch the pnc-simulator/ACTN simulator and initialize it with administrative APIs. "pnc-simulator" is our internal project name for ACTN simulator, throughout this guide, these two names are used interchangeably.
Step 1. Fetch the simulator docker image
...
It should be noted that, we redirect the request from host:18181 to container:8181. You can configure whatever port, mapping to container:8181 at your discretion. Be careful, if setting up multiple domain controllers, make sure to assign different external ports for them.
After starting the container, you should be able to verify the running container by:
| Code Block |
|---|
docker container ps –a | grep pncsimu |
Step 3. Initialize the simulator(s)
The simulator offers a set of administrative APIs which are designed for initialization and management purposes.
To initialize the simulator for each domain:
| Code Block |
|---|
curl –X POST –H "content-type:application/json" http://${SERVER_IP:SERVER_PORT}/pncsimu/v1/reload-data -d @INITIAL_DATA_FILE |
...
| Code Block |
|---|
curl –X POST –H "content-type:application/json" http://${SERVER_IP:SERVER_PORT}/pncsimu/v1/reload-data -d'{}' |
Please be noted that, in the perspective of ONAP eco-system, ACTN simulators act like local domain controllers. Therefore, to demonstrate ONAP/SDNC's cross-domain managing capabilities, at least two domain controllers are expected from ONAP/SDNC.
For demonstration purposes, two domain controllers are required, both need to be properly launched and initialized. The respective initialization payloads are attached below.
...