...
- docker/intradomain – three openNSA nodes in one domain using DUD backends
- docker/interdomain – the domains each containing three openNSA nodes all using DUD backends
- docker/ciena6500 – environemnt used during the development of the Ciena 6500 backend (OTN)
- docker/junosspace – environment used during the development of the JunOS-space backend
Testing the Intra-domain Setup
This Docker setup simulates a simple three nodes, one aggregator setup.
![Network drawing](nwlayout.png)
## Sample usage
Suppose we want to create a connection between node11 and node12, and we are a user in domain1 with access to nsi1.
We are going to use onsa tool to reserve and provision this connection.
The complete command sequence will be:
```bash
$ $TESTOPENNSA/docker/intradomain/setup init
$ $OPENNSA/onsa reserve \
-p domain1:nsa \
-u http://10.50.0.2:9445/NSI/services/CS2 \
--source node11.domain1:topology:port1?vlan=123 \
--dest node12.domain1:topology:port2?vlan=123
$ $OPENNSA/onsa provision \
-p domain1:nsa \
-u http://10.50.0.2:9445/NSI/services/CS2 \
-c DO-015774acaa
$ $OPENNSA/onsa queryrec \
-p domain1:nsa \
-u http://10.50.0.2:9445/NSI/services/CS2 \
-c DO-e0b4f25a66
$ $OPENNSA/onsa terminate \
-p domain1:nsa \
-u http://10.50.0.2:9445/NSI/services/CS2 \
-c DO-e0b4f25a66
$ $TESTOPENNSA/docker/intradomain/setup exit