Page Comparison

/wm/core/controller/switches/json

GET

List of all switch DPIDs connected to the controller

none

/wm/core/controller/summary/json

GET

Controller summary (# of Switches, # of Links, etc.)

none

/wm/core/module/all/json

GET

Retrieve all registered (but not loaded) modules.

none

/wm/core/module/loaded/json

GET

Retrieve all modules actively loaded by the module loader.

none

/wm/core/counter/<moduleName>/<counterTitle>/json

GET

List of counters per module, including switch counters.

moduleName: The name of the specific module for which to fetch counters. "OFSwitchManager" should be used for switch counters.
counterTitle: "all" or the name of the counter as defined in the module. Counters are defined in a hierarchical fashion and can be queried in groups by their common parent path in the counter hierarchy. 
For example, switch counters are defined at the root as "<dpid>:0x<aux-id>" or "00:00:00:00:00:00:00:01:0x01" where <dpid> is the switch DPID in hex-string form and <aux-id> is the OpenFlow connection ID in hexadecimal.
Among many counters in the hierarchy, all switches have specific "read" and "write" counters, which can be added to the counterTitle e.g. "00:00:00:00:00:00:00:01:0x01/read".

/wm/core/memory/json  

GET

Current controller memory usage

none

/wm/core/health/json

GET

Status/Health of REST API

none

/wm/core/system/uptime/json

GET

Controller uptime

none

/wm/core/storage/tables/json

GET

Tables present in Storage.

none

{"role":"<new-role>"}

new-role: "MASTER", "SLAVE", or "EQUAL"

{"role":"<role>"}

role: "MASTER", "SLAVE", or "EQUAL"

POST

PUT

Send empty string

POST

PUT

switchId: Valid Switch DPID as colon-delimited hex string or integer. Use "all" for all switches.

portId: Valid switch port number

/wm/device/

GET

List of all devices tracked by the controller. This includes MACs, IPs, and attachment points

Passed as GET parameters: mac (colon-separated hex-encoded), ipv4 (dotted decimal), vlan, dpid attachment point DPID (colon-separated hex-encoded) and port the attachment point port.

/networkService/v1.1/tenants/<tenant>/networks/<network> 

PUT/POST/DELETE 

Creates a new virtual network. Name and ID are required, gateway is optional.

URI argument: tenant: Currently ignored. network: ID (not name) of the network 

HTTP data: {"network": { "gateway": "<IP>", "name": "<Name>" }} 
IP: Gateway IP in "1.1.1.1" format, can be null   
Name: Network name as string 

/networkService/v1.1/tenants/<tenant>/networks/<network>/ports/<port>/attachment

PUT/DELETE

Attaches a host to a virtual network.

URI argument: tenant: Currently ignored. network: ID (not name) of the network. port: Logical port name 

HTTP data: {"attachment": {"id": "<Network ID>", "mac": "<MAC>"}} 
Network ID: Network ID as string, the one assigned at create 
MAC: MAC address in "XX:XX:XX:XX:XX:XX" format 

/networkService/v1.1/tenants/<tenant>/networks

GET

Shows all networks and their gateway, ID, and hosts mac in json format. 

URI argument: tenant: Currently ignored. 

More information available on Virtual Network Filter REST API

Add a rule

'{"<key>":"<value>", "<key>":"<value>", ...}'

<key>:value> pairs can be any of:

"nw-proto" : "any valid network protocol number"

"src-ip" : "ip/mask"

"dst-ip" : "ip/mask"

"tp-dst" : "any valid transport port number"

"action" : "ALLOW | DENY"

Delete a rule.

{"ruleid":"<rule>"}