You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Goal

  • scale up SDN-Controller/RESTconf interface for microserivces which are using only RESTconf (and optional websocket) interface, e.g. highstreet adapted transportPCE


Restrictions

  • RESTconf only for the device requests (up to now)
  • NodeIds have to be unique in the whole network (over multiple SDNCs /SDNC clusters)
  • only implemented services (here named multirequest services) can also be forwarded
  • things like network-topology are up to now not possible to forward (therefore the response data have to be combined)

How it works


Forwarding Rules

Uri

Description

^\/rests\/(data|operations)\/network-topology:network-topology\/topology=topology-netconf\/node=([a-zA-Z0-9\-_]+)[\?\/]+forward to odl of nodeId(match.group(2))
^\/restconf\/(config|operational)\/network-topology\/network-topology\/topology\/topology-netconf\/node\/([a-zA-Z0-9\-_]+)forward to odl of nodeId(match.group(2))
^/odluxhandled by sdnc-web
^/helphandled by sdnc-web
^/yang-schemamulti request service (with caching?)
^/odl/[a-zA-Z0-9\-](/.*)$forward to odl as match.group(1)
^/jolokia??? can be handled with /odl/... rule
  • No labels