Ok, I made a sample application, the yang files are here.
https://github.com/careerscale/opendaylight-demo/tree/master/api/src/main/yang
Please note this is with Boron. I found the
http://host:8181/restconf/operations/system-connector-xyz-rpc:add-connector
{
"input": {
"config":
{ "description": "connector created for testing", "host": "10.100.10.100", "name": "hari server", "admin-status": "system-connector:locked" }}
}
POST
http://host:8181/restconf/operations/sal-remote:create-notification-stream
{
"input": {
"notifications": [
"(urn:abc:system:connector:xyz:notification?revision=2016-10-10)connector-lifecycle-event"
],
"notification-output-type":"JSON"
}
}
GET
http://host:8181/restconf/streams/stream/create-notification-stream/system-connector-xyz-notification:connector-lifecycle-event
response of Boron notification here
{"notification":{"xmlns":"urn:ietf:params:xml:ns:netconf:notification:1.0","eventTime":"2016-10-17T05:20:05-07:00","create-notification-stream":{"notification":{"connector-lifecycle-event":{"xmlns":"urn:abc:system:connector:xyz:notification","event-type":"add","id":"connector-id=1476750005425","config":{"admin-status":
{"xmlns:x":"urn:abc:system:connector","content":"x:locked"},"host":"10.100.10.100","name":"rajath","description":"connector created for testing"}}},"xmlns":"urn:opendaylight:params:xml:ns:yang:controller:md:sal:remote"}}
----Original Message----
From: Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco) jatoth@cisco.com
Sent: Monday, October 17, 2016 2:41 AM
To: Harinath Mallepally <hmallepally@infinera.com>
Subject: RE: Change in netconf[stable/beryllium]: NETCONF-245 - Notifications stream output is not same as restco...
Thanks
----Original Message----
From: Harinath Mallepally hmallepally@infinera.com
Sent: Saturday, October 15, 2016 12:45 AM
To: Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco) <jatoth@cisco.com>
Subject: RE: Change in netconf[stable/beryllium]: NETCONF-245 - Notifications stream output is not same as restco...
Sure, let me build a sample app and send it across.
----Original Message----
From: Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco) jatoth@cisco.com
Sent: Friday, October 14, 2016 6:34 AM
To: Harinath Mallepally <hmallepally@infinera.com>
Subject: FW: Change in netconf[stable/beryllium]: NETCONF-245 - Notifications stream output is not same as restco...
It is because I have to know the case. Then I can write test for.
----Original Message----
From: Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco)
Sent: Friday, October 14, 2016 3:11 PM
To: 'Harinath Mallepally' <hmallepally@infinera.com>
Subject: RE: Change in netconf[stable/beryllium]: NETCONF-245 - Notifications stream output is not same as restco...
Thanks.
How is this container calling from another yang ? Can you send to me both yangs (or only parts with place where is the container calling and place of container int that yang) ? Or any info about structure of this please ?
----Original Message----
From: Harinath Mallepally hmallepally@infinera.com
Sent: Wednesday, October 12, 2016 3:12 PM
To: Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco) <jatoth@cisco.com>
Subject: Re: Change in netconf[stable/beryllium]: NETCONF-245 - Notifications stream output is not same as restco...
Within container as leaf.
The container itself is in another yang. I think this was working earlier.
Get Outlook for iOS<https://aka.ms/o0ukef>
On Tue, Oct 11, 2016 at 11:54 PM -0700, "Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco)" <jatoth@cisco.com<jatoth@cisco.com>> wrote:
Do you have this schema node in your yang file ? And which statement is this node (I mean leaf or list or container or etc..) ?
----Original Message----
From: Harinath Mallepally hmallepally@infinera.com
Sent: Wednesday, October 12, 2016 12:54 AM
To: Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco) <jatoth@cisco.com>
Subject: RE: Change in netconf[stable/beryllium]: NETCONF-245 - Notifications stream output is not same as restco...
Looks like my problem now, for one notification, rest seem to be fine, but is it possible to leave some space for this exception message?
2016-10-11 15:47:05,803 | ERROR | pool-30-thread-1 | RestCodec | 212 - org.opendaylight.netconf.sal-rest-connector - 1.3.4.SNAPSHOT | Schema node of (urn:infinera:system:connector:otsv:notification?revision=2016-05-10)update_statusdoesn't exist in (urn:infinera:system:connector:otsv:notification?revision=2016-05-10)config
2016-10-11 15:47:05,803 | ERROR | pool-30-thread-1 | DOMNotificationRouterEvent | 116 - org.opendaylight.controller.sal-broker-impl - 1.3.3.Beryllium-SR3 | Delivery of notification org.opendaylight.controller.md.sal.binding.impl.LazySerializedDOMNotification@590ed404 caused an error in listener org.opendaylight.netconf.sal.streams.listeners.NotificationListenerAdapter@3dd965bf
org.opendaylight.netconf.sal.restconf.impl.RestconfDocumentedException: errors: [error-type: application, error-tag: operation-failed, error-message: Schema node of (urn:infinera:system:connector:otsv:notification?revision=2016-05-10)update_statusdoesn't exist in (urn:infinera:system:connector:otsv:notification?revision=2016-05-10)config]]
at org.opendaylight.netconf.sal.streams.listeners.ParserOfSchemaNode.parseFrom(ParserOfSchemaNode.java:78)[212:org.opendaylight.netconf.sal-rest-connector:1.3.4.SNAPSHOT]
at org.opendaylight.netconf.sal.streams.listeners.ParserOfSchemaNode.parseFrom(ParserOfSchemaNode.java:80)[212:org.opendaylight.netconf.sal-rest-connector:1.3.4.SNAPSHOT]
at org.opendaylight.netconf.sal.streams.listeners.ParserOfSchemaNode.parseFrom(ParserOfSchemaNode.java:80)[212:org.opendaylight.netconf.sal-rest-connector:1.3.4.SNAPSHOT]
at org.opendaylight.netconf.sal.streams.listeners.ParserOfSchemaNode.parseFrom(ParserOfSchemaNode.java:57)[212:org.opendaylight.netconf.sal-rest-connector:1.3.4.SNAPSHOT]
at org.opendaylight.netconf.sal.streams.listeners.NotificationListenerAdapter.prepareValueByType(NotificationListenerAdapter.java:312)[212:org.opendaylight.netconf.sal-rest-connector:1.3.4.SNAPSHOT]
at org.opendaylight.netconf.sal.streams.listeners.NotificationListenerAdapter.innerChildToJSON(NotificationListenerAdapter.java:196)[212:org.opendaylight.netconf.sal-rest-connector:1.3.4.SNAPSHOT]
at org.opendaylight.netconf.sal.streams.listeners.NotificationListenerAdapter.addContainerNodeToJSON(NotificationListenerAdapter.java:171)[212:org.opendaylight.netconf.sal-rest-connector:1.3.4.SNAPSHOT]
at org.opendaylight.netconf.sal.streams.listeners.NotificationListenerAdapter.innerChildToJSON(NotificationListenerAdapter.java:202)[212:org.opendaylight.netconf.sal-rest-connector:1.3.4.SNAPSHOT]
at org.opendaylight.netconf.sal.streams.listeners.NotificationListenerAdapter.addContainerNodeToJSON(NotificationListenerAdapter.java:171)[212:org.opendaylight.netconf.sal-rest-connector:1.3.4.SNAPSHOT]
at org.opendaylight.netconf.sal.streams.listeners.NotificationListenerAdapter.innerChildToJSON(NotificationListenerAdapter.java:202)[212:org.opendaylight.netconf.sal-rest-connector:1.3.4.SNAPSHOT]
at org.opendaylight.netconf.sal.streams.listeners.NotificationListenerAdapter.addContainerNodeToJSON(NotificationListenerAdapter.java:171)[212:org.opendaylight.netconf.sal-rest-connector:1.3.4.SNAPSHOT]
at org.opendaylight.netconf.sal.streams.listeners.NotificationListenerAdapter.prepareJson(NotificationListenerAdapter.java:149)[212:org.opendaylight.netconf.sal-rest-connector:1.3.4.SNAPSHOT]
at org.opendaylight.netconf.sal.streams.listeners.NotificationListenerAdapter.onNotification(NotificationListenerAdapter.java:129)[212:org.opendaylight.netconf.sal-rest-connector:1.3.4.SNAPSHOT]
at org.opendaylight.controller.md.sal.dom.broker.impl.DOMNotificationRouterEvent.deliverNotification(DOMNotificationRouterEvent.java:56)[116:org.opendaylight.controller.sal-broker-impl:1.3.3.Beryllium-SR3]
at org.opendaylight.controller.md.sal.dom.broker.impl.DOMNotificationRouter$1.onEvent(DOMNotificationRouter.java:68)[116:org.opendaylight.controller.sal-broker-impl:1.3.3.Beryllium-SR3]
at org.opendaylight.controller.md.sal.dom.broker.impl.DOMNotificationRouter$1.onEvent(DOMNotificationRouter.java:65)[116:org.opendaylight.controller.sal-broker-impl:1.3.3.Beryllium-SR3]
at com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128)[113:com.lmax.disruptor:3.3.2]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_77]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_77]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_77]
----Original Message----
From: Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco) jatoth@cisco.com
Sent: Tuesday, October 11, 2016 3:18 PM
To: Harinath Mallepally <hmallepally@infinera.com>
Subject: RE: Change in netconf[stable/beryllium]: NETCONF-245 - Notifications stream output is not same as restco...
Ok, thanks
----Original Message----
From: Harinath Mallepally hmallepally@infinera.com
Sent: Tuesday, October 11, 2016 6:45 PM
To: Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco) <jatoth@cisco.com>
Subject: RE: Change in netconf[stable/beryllium]: NETCONF-245 - Notifications stream output is not same as restco...
Ok, will check today
----Original Message----
From: Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco) jatoth@cisco.com
Sent: Tuesday, October 11, 2016 8:18 AM
To: Harinath Mallepally <hmallepally@infinera.com>
Subject: RE: Change in netconf[stable/beryllium]: NETCONF-245 - Notifications stream output is not same as restco...
Should be fixed.
----Original Message----
From: Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco)
Sent: Monday, October 10, 2016 1:17 PM
To: 'Harinath Mallepally' <hmallepally@infinera.com>
Subject: RE: Change in netconf[stable/beryllium]: NETCONF-245 - Notifications stream output is not same as restco...
No, it doesn't. I'm working on.
----Original Message----
From: Harinath Mallepally hmallepally@infinera.com
Sent: Wednesday, October 5, 2016 1:40 AM
To: Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco) <jatoth@cisco.com>
Subject: RE: Change in netconf[stable/beryllium]: NETCONF-245 - Notifications stream output is not same as restco...
Is this expected?
016-10-04 16:45:12,792 | ERROR | pool-30-thread-1 | DOMNotificationRouterEvent | 116 - org.opendaylight.controller.sal-broker-impl - 1.3.3.Beryllium-SR3 | Delivery of notification org.opendaylight.controller.md.sal.binding.impl.LazySerializedDOMNotification@60d4bde caused an error in listener org.opendaylight.netconf.sal.streams.listeners.NotificationListenerAdapter@39c30057
java.lang.NullPointerException
at org.opendaylight.netconf.sal.streams.listeners.NotificationListenerAdapter.prepareValueByType(NotificationListenerAdapter.java:218)[212:org.opendaylight.netconf.sal-rest-connector:1.3.4.SNAPSHOT]
at org.opendaylight.netconf.sal.streams.listeners.NotificationListenerAdapter.addMapNodeToJSON(NotificationListenerAdapter.java:179)[212:org.opendaylight.netconf.sal-rest-connector:1.3.4.SNAPSHOT]
at org.opendaylight.netconf.sal.streams.listeners.NotificationListenerAdapter.innerChildToJSON(NotificationListenerAdapter.java:160)[212:org.opendaylight.netconf.sal-rest-connector:1.3.4.SNAPSHOT]
at org.opendaylight.netconf.sal.streams.listeners.NotificationListenerAdapter.addContainerNodeToJSON(NotificationListenerAdapter.java:148)[212:org.opendaylight.netconf.sal-rest-connector:1.3.4.SNAPSHOT]
at org.opendaylight.netconf.sal.streams.listeners.NotificationListenerAdapter.innerChildToJSON(NotificationListenerAdapter.java:168)[212:org.opendaylight.netconf.sal-rest-connector:1.3.4.SNAPSHOT]
at org.opendaylight.netconf.sal.streams.listeners.NotificationListenerAdapter.addContainerNodeToJSON(NotificationListenerAdapter.java:148)[212:org.opendaylight.netconf.sal-rest-connector:1.3.4.SNAPSHOT]
at org.opendaylight.netconf.sal.streams.listeners.NotificationListenerAdapter.innerChildToJSON(NotificationListenerAdapter.java:168)[212:org.opendaylight.netconf.sal-rest-connector:1.3.4.SNAPSHOT]
at org.opendaylight.netconf.sal.streams.listeners.NotificationListenerAdapter.addContainerNodeToJSON(NotificationListenerAdapter.java:148)[212:org.opendaylight.netconf.sal-rest-connector:1.3.4.SNAPSHOT]
at org.opendaylight.netconf.sal.streams.listeners.NotificationListenerAdapter.prepareJson(NotificationListenerAdapter.java:140)[212:org.opendaylight.netconf.sal-rest-connector:1.3.4.SNAPSHOT]
at org.opendaylight.netconf.sal.streams.listeners.NotificationListenerAdapter.onNotification(NotificationListenerAdapter.java:125)[212:org.opendaylight.netconf.sal-rest-connector:1.3.4.SNAPSHOT]
at org.opendaylight.controller.md.sal.dom.broker.impl.DOMNotificationRouterEvent.deliverNotification(DOMNotificationRouterEvent.java:56)[116:org.opendaylight.controller.sal-broker-impl:1.3.3.Beryllium-SR3]
at org.opendaylight.controller.md.sal.dom.broker.impl.DOMNotificationRouter$1.onEvent(DOMNotificationRouter.java:68)[116:org.opendaylight.controller.sal-broker-impl:1.3.3.Beryllium-SR3]
at org.opendaylight.controller.md.sal.dom.broker.impl.DOMNotificationRouter$1.onEvent(DOMNotificationRouter.java:65)[116:org.opendaylight.controller.sal-broker-impl:1.3.3.Beryllium-SR3]
at com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128)[113:com.lmax.disruptor:3.3.2]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_77]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_77]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_77]
----Original Message----
From: Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco) jatoth@cisco.com
Sent: Monday, October 03, 2016 6:01 AM
To: Harinath Mallepally <hmallepally@infinera.com>
Subject: RE: Change in netconf[stable/beryllium]: NETCONF-245 - Notifications stream output is not same as restco...
OK, It's there new patch - https://git.opendaylight.org/gerrit/#/c/44052/ . I believe, this should be better.
And about upgrade to Boron.. you can checkout stable/boron branch, download Boron release or adapt poms.
----Original Message----
From: Harinath Mallepally hmallepally@infinera.com
Sent: Tuesday, September 27, 2016 7:01 PM
To: Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco) <jatoth@cisco.com>
Subject: RE: Change in netconf[stable/beryllium]: NETCONF-245 - Notifications stream output is not same as restco...
Thanks. btw do you know any instructions to upgrade to boron?
----Original Message----
From: Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco) jatoth@cisco.com
Sent: Tuesday, September 27, 2016 9:55 AM
To: Harinath Mallepally <hmallepally@infinera.com>
Subject: FW: Change in netconf[stable/beryllium]: NETCONF-245 - Notifications stream output is not same as restco...
OK, I find where I made mistake. I'm going to fix it.
----Original Message----
From: Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco)
Sent: Tuesday, September 27, 2016 9:32 AM
To: 'Harinath Mallepally' <hari@harinath.in>
Subject: RE: Change in netconf[stable/beryllium]: NETCONF-245 - Notifications stream output is not same as restco...
Yes, I know. I'm going to write more tests now to find and solve the problem (or all problems).
And thanks for your previous response 
----Original Message----
From: Harinath Mallepally hari@harinath.in
Sent: Tuesday, September 27, 2016 12:24 AM
Cc: Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco) <jatoth@cisco.com>
Subject: Re: Change in netconf[stable/beryllium]: NETCONF-245 - Notifications stream output is not same as restco...
I have not seen this patch too working.
Sent from my iPhone
> On Sep 26, 2016, at 12:14 PM, Gerrit Code Review <gerrit@opendaylight.org> wrote:
>
> From jenkins-releng <jenkins-releng@opendaylight.org>:
>
> jenkins-releng has posted comments on this change.
>
> Change subject: NETCONF-245 - Notifications stream output is not same as
> restconf data ......................................................................
>
>
> Patch Set 8: Verified+1
>
> Build Successful
>
> https://jenkins.opendaylight.org/releng/job/netconf-verify-beryllium-m
> vn33-openjdk8/20/ : SUCCESS
>
> Logs:
> https://logs.opendaylight.org/releng/jenkins092/netconf-verify-berylli
> um-mvn33-openjdk8/20
>
> https://jenkins.opendaylight.org/releng/job/netconf-distribution-check
> -beryllium/18/ : SUCCESS
>
> Logs:
> https://logs.opendaylight.org/releng/jenkins092/netconf-distribution-c
> heck-beryllium/18
>
> https://jenkins.opendaylight.org/releng/job/netconf-verify-beryllium-m
> vn33-openjdk7/20/ : SUCCESS
>
> Logs:
> https://logs.opendaylight.org/releng/jenkins092/netconf-verify-berylli
> um-mvn33-openjdk7/20
>
> –
> To view, visit https://git.opendaylight.org/gerrit/44052
> To unsubscribe, visit https://git.opendaylight.org/gerrit/settings
>
> Gerrit-MessageType: comment
> Gerrit-Change-Id: I24ceb02d10f0a142fb1b21664b600cad8f69df87
> Gerrit-PatchSet: 8
> Gerrit-Project: netconf
> Gerrit-Branch: stable/beryllium
> Gerrit-Owner: Jakub Toth <jatoth@cisco.com>
> Gerrit-Reviewer: Harinath Mallepally <hari@harinath.in>
> Gerrit-Reviewer: Jakub Toth <jatoth@cisco.com>
> Gerrit-Reviewer: jenkins-releng <jenkins-releng@opendaylight.org>
> Gerrit-HasComments: No
Hi Jakub,
Sorry for the delay.
I see the data/attributes missing for all.
I built the netconf module and took the built sal-rest-connector and renamed it to 1.3.3-Beryllium-SR3 version as we are using SR3.
From: Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco) jatoth@cisco.com
Sent: Thursday, September 22, 2016 11:47 PM
To: Harinath Mallepally <hmallepally@infinera.com>
Subject: FW: NETCONF-245
Hi,
do you have any news about this, please ?
Regards,
Jakub Toth
From: Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco)
Sent: Friday, September 9, 2016 2:55 PM
To: 'Harinath Mallepally' <hmallepally@infinera.com>
Subject: RE: NETCONF-245
Thanks. I made few changes. I add new part of parser for leaf types. Can you try it with your data, please ?
https://git.opendaylight.org/gerrit/#/c/44052/5
From: Harinath Mallepally hmallepally@infinera.com
Sent: Wednesday, September 7, 2016 12:53 AM
To: Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco) <jatoth@cisco.com>
Subject: RE: NETCONF-245
Looks like I didn’t see any difference (fix)
Through restconf
"leaf": "mod-name:value"
Through notification
"leaf":"(urn:mod?revision=xxx)value",
From: Harinath Mallepally
Sent: Tuesday, September 06, 2016 9:57 AM
To: 'Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco)' <jatoth@cisco.com>
Subject: RE: NETCONF-245
It was long weekend, so will check and confirm today. Thanks
From: Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco) jatoth@cisco.com
Sent: Monday, September 05, 2016 1:55 AM
To: Harinath Mallepally <hmallepally@infinera.com>
Subject: RE: NETCONF-245
Do you have still problem with augmentation, please ? https://git.opendaylight.org/gerrit/#/c/44052/2
From: Harinath Mallepally hmallepally@infinera.com
Sent: Friday, August 26, 2016 2:26 AM
To: Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco) <jatoth@cisco.com>
Subject: RE: NETCONF-245
Did you happen to look at this one?
From: Harinath Mallepally
Sent: Friday, August 19, 2016 5:42 AM
To: Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco) <jatoth@cisco.com>
Subject: Re: NETCONF-245
Identity
Get Outlook for iOS
On Fri, Aug 19, 2016 at 5:33 AM -0700, "Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco)" <jatoth@cisco.com> wrote:
It seams to be problem, that I‘m using value in leaf node, which type is String.
Leaf oper-status is node with value, which type is Qname. I can try to fix it in this parser. But I have now a critical bug in Restconf project so I have to fix it like first. I’ll fix it as soon as possible.
From: Harinath Mallepally hmallepally@infinera.com
Sent: Tuesday, August 16, 2016 4:30 PM
To: Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco) <jatoth@cisco.com>
Subject: RE: NETCONF-245
Pls note the format difference alone, the values are different because the restconf data was from my old mail. (so connected/not-reachable is not difference)
From: Harinath Mallepally
Sent: Tuesday, August 16, 2016 7:27 AM
To: Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco) <jatoth@cisco.com>
Subject: RE: NETCONF-245
I see one difference still
The identity value reference is not same in both the cases:
Notification:
"leaf":"(urn:mod?revision=xxx)value"
Rest conf:
"leaf": "mod-name:value"
From: Harinath Mallepally
Sent: Tuesday, August 16, 2016 5:50 AM
To: Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco) <jatoth@cisco.com>
Subject: Re: NETCONF-245
thanks will check and get back today
Get Outlook for iOS
On Tue, Aug 16, 2016 at 3:50 AM -0700, "Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco)" <jatoth@cisco.com> wrote:
Thanks.
Soo I made any changes there. Here is gerrit https://git.opendaylight.org/gerrit/#/c/44052/. Can you try it please ?
Jakub Toth
----Original Message----
From: Harinath Mallepally hmallepally@infinera.com
Sent: Monday, August 15, 2016 3:21 PM
To: Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco) <jatoth@cisco.com>
Subject: Re: NETCONF-245
Yes
Get Outlook for iOS<https://aka.ms/o0ukef>
On Mon, Aug 15, 2016 at 2:49 AM -0700, "Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco)" <jatoth@cisco.com<jatoth@cisco.com>> wrote:
Hi,
I have another question. Are you working with beryllium please ?
Jakub Toth
From: Harinath Mallepally hmallepally@infinera.com
Sent: Friday, August 12, 2016 7:03 PM
To: Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco) <jatoth@cisco.com>
Subject: RE: NETCONF-245
Hi Jakub
Here are the differences that I can see at the outset. The requirement for me is to have the consumer of the notification using same code to parse restconf data as well as notification data.
1. Order of attributes, probably this is something we can live with it.
2. Difference with namespace approach.
In the notification:
"leaf":
{ "xmlns:x":"urn:mod", "value-leaf":"x:value" }In the restconf
"leaf": "mod-name:value"
3. Augmentation reference
In notification:
"node-a":{
"node-b":{
In the restconf
"mod-name:node-a": {
Hope this helps!
Thanks
Hari
From: Harinath Mallepally
Sent: Wednesday, August 10, 2016 6:43 AM
To: 'Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco)' <jatoth@cisco.com<jatoth@cisco.com>>
Subject: RE: NETCONF-245
Hi Jakub, will do today.
From: Jakub Toth -X (jatoth - PANTHEON TECHNOLOGIES at Cisco) jatoth@cisco.com
Sent: Tuesday, August 09, 2016 12:54 AM
To: Harinath Mallepally <hmallepally@infinera.com<hmallepally@infinera.com>>
Subject: NETCONF-245
Hi,
can you send me more information about https://bugs.opendaylight.org/show_bug.cgi?id=6324 please ? I mean examples etc..
Best regards,
Jakub Toth