Versions Compared

Old Version 6

changes.mady.by.user Martin Skorupski

Saved on

compared with

New Version 7

changes.mady.by.user Martin Skorupski

Saved on

Key

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

Status: 2020-06-27: under construction

The OpenDaylight project has implemented the RestConf interface according RCF8040. The previous in OpenDaylight implemented RestConf(-like) interface is supported too and both interfaces can be installed in parallel within the Apache Karaf container. Please see the documentation of NetConf project of OpenDaylight.  

TODOs
http://10.20.5.5:8181/restconf/operations/data-provider:create-network-element-connection
http://10.20.5.5:8181/restconf/operations/data-provider:read-network-element-connection-list
http://10.20.5.5:8181/restconf/config

Status: 2020-06-27: under construction

The OpenDaylight project has implemented the RestConf interface according RCF8040. The previous in OpenDaylight implemented RestConf(-like) interface is supported too and both interfaces can be installed in parallel within the Apache Karaf container. Please see the documentation of NetConf project of OpenDaylight.  


This wiki shows difference between both interfaces based on examples.

The syntax is as defined by the vsCode/rest-client.


Info regarding RFC8040 and RFC8527

  1. RFC8040 defines RESTCONF
  2. The latest open-source implementation of RFC8040 is today in OpenDaylight Aluminium. However OpenDaylight Sodium and OpenDaylight Magnesium are good enough for our purposes.
  3. RFC8527 extends RFC8040 to support new datastores as defined in RFC8525, but RFC8527 does not make RFC8040 obsolete.

Description

Biermann

RestConf (RFC8040)

Get OpenDaylights YANG capabilities.

GET {{baseUrl}}/restconf/modules
Authorization:Basic {{user}} {{password}}
Accept:application/json
Content-Type:application/json

(currently not found... 404 (wink) )

Get NetConf Topology from configuration datastore

GET {{baseUrl}}/restconf/config/network-topology:network-topology/topology-netconf
Authorization:Basic {{user}} {{password}}
Accept:application/json
Content-Type:application/json

GET {{baseUrl}}/rests/data/network-topology:network-topology/topology=topology-netconf?content=config
Authorization:Basic {{user}} {{password}}
Accept:application/json
Content-Type:application/json

Get NetConf Topology from operational datastore

GET {{baseUrl}}/restconf/operational/network-topology:network-topology/topology/topology-netconf
Authorization:Basic {{user}} {{password}}
Accept:application/json
Content-Type:application/json

GET {{baseUrl}}/rests/data/network-topology:network-topology/topology=topology-netconf?content=nonconfig  
Authorization:Basic {{user}} {{password}}
Accept:application/json
Content-Type:application/json

Get NetConf Topology from both datastores at the same time

n/a

GET {{baseUrl}}/rests/data/network-topology:network-topology/topology=topology-netconf 
Authorization:Basic {{user}} {{password}}
Accept:application/json
Content-Type:application/json

Get only the node-ids from both datastores

n/a

GET {{baseUrl}}/rests/data/network-topology:network-topology/topology=topology-netconf?fields=node(node-id)
Authorization:Basic {{user}} {{password}}
Accept:application/json
Content-Type:application/json

Get only the node-ids from operational datastores

n/a

GET {{baseUrl}}/rests/data/network-topology:network-topology/topology=topology-netconf?content=nonconfig&fields=node(node-id)
Authorization:Basic {{user}} {{password}}
Accept:application/json
Content-Type:application/json

Get only the node-ids and their connection-status

n/a

GET {{baseUrl}}/rests/data/network-topology:network-topology/topology=topology-netconf?fields=node(node-id;netconf-node-topology:connection-status)
Authorization:Basic {{user}} {{password}}
Accept:application/json
Content-Type:application/json

Get only the node-ids and their capabilities

n/a

GET {{baseUrl}}/rests/data/network-topology:network-topology/topology=topology-netconf?content=nonconfig&fields=node(node-id;netconf-node-topology:available-capabilities/available-capability/capability)
Authorization:Basic {{user}} {{password}}
Accept:application/json
Content-Type:application/json

Get  capabilities of a given node-id

Description

Biermann

RestConf (RFC8040)

Get OpenDaylights YANG capabilities.

GET {{baseUrl}}/restconf/modulesGET {{baseUrl}}/restconf/operational/network-topology:network-topology/topology/topology-netconf/

node/robot-ORAN-sim-lifecycle

This wiki shows difference between both interfaces based on examples.

The syntax is as defined by the vsCode/rest-client.

Info regarding RFC8040 and RFC8527

  1. RFC8040 defines RESTCONF
  2. The latest open-source implementation of RFC8040 is today in OpenDaylight Aluminium. However OpenDaylight Sodium and OpenDaylight Magnesium are good enough for our purposes.
  3. RFC8527 extends RFC8040 to support new datastores as defined in RFC8525, but RFC8527 does not make RFC8040 obsolete.

node/{{mountPoint}}/netconf-node-topology:available-capabilities
Authorization:Basic {{user}} {{password}}
Accept:application/json
Content-Type:application/json

GET {{baseUrl}}/rests/data/network-topology:network-topology/topology=topology-netconf/node={{mountPoint}}/netconf-node-topology:available-capabilities?fields=available-capability(capability)
Authorization:Basic {{user}} {{password}}
Accept:application/json
Content-Type:application/json

(currently not found... 404 (wink) )

Get NetConf Topology from configuration datastore

GETCreate new NetworkElement connection with SDN-R data-provider.

POST {{baseUrl}}/restconf/configoperations/networkdata-topologyprovider:create-network-topology/topology-netconfelement-connection
Authorization:Basic {{user}} {{password}}
Accept:application/json
Content-Type:application/jsonGET {{baseUrl}}/rests/data/network-topology:network-topology/topology=topology-netconf?content=config
Authorization:Basic {{user}} {{password}}
Accept:application/json
Content-Type:application/json

Get NetConf Topology from operational datastore

GET {{baseUrl}}/restconf/operational/network-topology:network-topology/topology/topology-netconf
Authorization:Basic {{user}} {{password}}
Accept:application/json
Content-Type:application/jsonGET {{baseUrl}}/rests/data/network-topology:network-topology/topology=topology-netconf?content=nonconfig  
Authorization:Basic {{user}} {{password}}
Accept:application/json
Content-Type:application/json

Get NetConf Topology from both datastores at the same time

n/a

GET{
  "data-provider:input": {
    "data-provider:id": "new-mountpoint-name",
    "data-provider:node-id": "new-mountpoint-name",
    "data-provider:host": "10.10.10.10",
    "data-provider:port": "830",
    "data-provider:username": "netconf",
    "data-provider:password": "netconf",
    "data-provider:is-required": "true"
  }
}

# Note: the http body is the same!

POST {{baseUrl}}/rests/operations/data/network-topologyprovider:create-network-topology/topology=topology-netconf element-connection
Authorization:Basic {{user}} {{password}}
Accept:application/json
Content-Type:application/json

Get only the node-ids from both datastores

n/a

GET {{baseUrl}}/rests/data/network-topology:network-topology/topology=topology-netconf?fields=node(node-id)
Authorization:Basic {{user}} {{password}}
Accept:application/json
Content-Type:application/json

Get only the node-ids from operational datastores

n/a

GET {{baseUrl}}/rests/data/network-topology:network-topology/topology=topology-netconf?content=nonconfig&fields=node(node-id)
Authorization:Basic {{user}} {{password}}
Accept:application/json
Content-Type:application/json

Get only the node-ids and their connection-status

n/a

GET {{baseUrl}}/rests/data/network-topology:network-topology/topology=topology-netconf?fields=node(node-id;netconf-node-topology:connection-status)

{
  "data-provider:input": {
    "data-provider:id": "new-mountpoint-name",
    "data-provider:node-id": "new-mountpoint-name",
    "data-provider:host": "10.10.10.10",
    "data-provider:port": "830",
    "data-provider:username": "netconf",
    "data-provider:password": "netconf",
    "data-provider:is-required": "true"
  }
}

# Note: the http body is the same! Just the URL is different

Read SDN-R Connection List

POST {{baseUrl}}/restconf/operations/data-provider:read-network-element-connection-list
Authorization:Basic {{user}} {{password}}
Accept:application/json
Content-Type:application/json

Get only the node-ids and their capabilities

n/a

GET {{baseUrl}}/rests/data/network-topology:network-topology/topology=topology-netconf?content=nonconfig&fields=node(node-id;netconf-node-topology:available-capabilities/available-capability/capability)
Authorization:Basic {{user}} {{password}}
Accept:application/json
Content-Type:application/json

Get  capabilities of a given node-id

GET

{
  "input": {
    "filter": [{
      "property": "status",
      "filtervalue": "Connecting"
      }
    ],
    "sortorder": [{
      "property": "node-id",
      "sortorder": "descending"
      }
    ],
    "pagination": {
      "size": 5,
      "page": 3
     }
  }
}

POST {{baseUrl}}/restconfrests/operationaloperations/networkdata-topologyprovider:read-network-topology/topology/topology-netconf/node/{{mountPoint}}/netconf-node-topology:available-capabilitieselement-connection-list
Authorization:Basic {{user}} {{password}}
Accept:application/json
Content-Type:application/json

GET{{baseUrl}}/rests/data/network-topology:network-topology/topology=topology-netconf/node={{mountPoint}}/netconf-node-topology:available-capabilities?fields=available-capability(capability)
Authorization:Basic {{user}} {{password}}
Accept:application/json
Content-Type:application/json
  "input": {
    "filter": [{
      "property": "status",
      "filtervalue": "Connecting"
      }
    ],
    "sortorder": [{
      "property": "node-id",
      "sortorder": "descending"
      }
    ],
    "pagination": {
      "size": 5,
      "page": 3
     }
  }
}