Versions Compared

Key

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

...

MethodPathDescription
POSTonos/cordvtn/service-dependency/{tenant service network UUID}/{provider service netework UUID}Creates a service dependency with unidirectional access from a tenant service to a provider service
POSTonos/cordvtn/service-dependency/{tenant service network UUID}/{provider service netework UUID}/[u/b]Creates a service dependency with access type extension. "u" is implied to a unidirectional access from a tenant service to a provider service and "b" for bidirectional access between two services.
DELETEonos/cordvtn/service-dependency/{tenant service network UUID}/{provider service netework UUID}Removes services dependency from a tenant service to a provider service.

 

CLI Commands

CommandUsageDescription
cordvtn-nodescordvtn-nodesShows the list of compute nodes that registered to COR-VTN service
cordvtn-node-checkcordvtn-node-check [hosthame]Shows the state of each node bootstrap steps
cordvtn-node-initcordvtn-node-init [hostname]Initializes the node including creating "br-int" bridge and setting the controller to ONOS cluster, creating "vxlan" port, adding "dataPlaneIntf", assigning "localMgmtIp" and "dataPlaneIp" to "br-int" interface, and populating flows for the VMs connected to the "br-int". It is no harm to repeat this command multiple times.
cordvtn-node-deletecordvtn-node-delete [hostname]Removes the node from the CORD-VTN service
cordvtn-flush-rulescordvtn-flush-rulesFlushes all the rules installed by CORD-VTN in the data plane. This command might be useful when the data plane is messed up. You can flush the data plane with this command and re-initialize the nodes by running "cordvtn-node-init" command or pushing the network-cfg.json again. It would refresh the data plane.