[NETCONF-194] documentation on stream creation for yang notifications Created: 13/May/16  Updated: 15/Mar/19  Resolved: 13/Jun/16

Status: Resolved
Project: netconf
Component/s: restconf-nb
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Harinath Mallepally Assignee: Jakub Toth
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Issue Links:
Duplicate
duplicates NETCONF-56 create-notification-stream can not be... Resolved
External issue ID: 5886

 Description   

The current information seems limited and only works for data change event notifications.
https://github.com/opendaylight/docs/blob/master/manuals/developer-guide/src/main/asciidoc/controller/websocket-notifications.adoc

It will be really nice if it can be updated with working stream creation for yang notifications.

When I tried

http://<host>:8181/restconf/operations/sal-remote:create-notification-stream

{
"input":

{ "notifications":["(urn:ietf:params:xml:ns:yang:ietf-te-topology?revision=2016-03-17)te-node-event"] }

}

Response is

{
"errors": {
"error": [

{ "error-type": "application", "error-tag": "operation-failed", "error-message": "Instance identifier was not normalized correctly " }

]
}
}

I think I am providing correct information and not able to understand what else is missing.

 Comments   
Comment by Martin Ciglan [ 19/May/16 ]

moving to Restconf

Comment by Martin Ciglan [ 19/May/16 ]

Hi Harinath

by looking at code base, this is not implemented yet
it works only for data change event notifications
as it is documented

Comment by Harinath Mallepally [ 25/May/16 ]

is this something my team can fix and commit to ODL? can we do that? or we will fix it and use it and then come back? will that be OK?

Comment by Martin Ciglan [ 25/May/16 ]

Hi Harinath

Sure, you're welcome to help.
Once your patch is ready, just let us know via gerrit review. Thank you.

Martin

Generated at Wed Feb 07 20:14:24 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.