In this example, for region UID 713def9a-4f96-485f-990c-8924bc06c8d8 and controller
172.17.6.70 (master), the devices are 192.168.1.101, 192.168.1.102, 192.168.1.103,
192.168.1.104, and 192.168.1.105.
Regardless of how many IPs are configured for the devices in the region, this GET command
indicates only those that are actually active and owned by the specified controller.
Example command
curl --noproxy controllerIp --header "X-Auth-Token:token" -ksS --request GET --url
https://controllerIp>:8443/sdn/v2.0/owners/region_uid/devices
Example output
{
"ownership":{
"uid":"713def9a-4f96-485f-990c-8924bc06c8d8",
"name":"Region-Red",
"owningControllerIp":"172.17.6.70",
"devices":[
{
"deviceIp":"192.168.1.101"
},
{
"deviceIp":"192.168.1.102"
},
{
"deviceIp":"192.168.1.103"
},
{
"deviceIp":"192.168.1.104"
},
{
"deviceIp":"192.168.1.105"
}
]
}
}
Getting the status of a specific region using curl
This GET command retrieves the current status of the region with the specified UID, including its
configured devices and the controller that currently owns each device.
In this example, for region UID 713def9a-4f96-485f-990c-8924bc06c8d8, the command
output shows the status of all the devices, including their datapaths. In this example all devices
are owned by the master controller 172.17.6.70.
Example command
curl --noproxy teamIp --header "X-Auth-Token:token" -ksS --request GET --url
https://teamIp:8443/sdn/v2.0/owners/region_uid/state?dataPathDetails=yes
Example output
{
"regions":[
{
"uid":"713def9a-4f96-485f-990c-8924bc06c8d8",
"name":"Region-Red",
"prioritizedControllerIps":[
"172.17.6.70",
"172.17.6.71",
"172.17.6.72"
],
"devices":[
{
"deviceIp":"192.168.1.101",
Team configuration using curl commands 195