The SDN-R Websocketmanager is a server which a client can connect to, to receive NETCONF-notifications forwarded by the the devicemanagers( up to now, until we have a generic solution). To get rid of all old protocol issues we redesigned all the messages.
...
In fact there are a lot of use cases to receive a lot of different notifications or specific notifications for a bunch of nodes, most properties are optional
property | optional | description |
---|---|---|
node-id | yes | filter for notifications only from node with node-id |
schema | yes | filter for specific notifications implemented by a model |
schema.namespace | no | if schema is set, namespace has to be set, otherwise a schema is not valid |
schema.revision | yes | filter for a specific revision of the implemented model |
schema.notification | yes | filter for specific notification types of the model |
If the user scope registration succeeds you will get a response with your submitted scopes
...
Code Block |
---|
{ "event-time": "2021-03-12T05:08:55.3Z", "type": "urn:opendaylight:params:xml:ns:yang:devicemanager@2019-01-09:object-creation-notification", "node-id": "SDN-Controller-0", "data": { "object-id-ref": "sim1", "counter": 7, "time-stamp": "2021-03-12T05:08:55.2Z" } } |
property | description |
---|---|
node-id | node-id which is the source the notification |
event-time | timestamp of the notification |
type | <namespace>@<revision>:<notification-type> |
data | notification itself |