[CONTROLLER-994] Migrate to use new APIs for normalized nodes (also for rpcs, notifications etc.) Created: 04/Nov/14  Updated: 25/Jul/23  Due: 19/Mar/15  Resolved: 16/Mar/15

Status: Resolved
Project: controller
Component/s: netconf
Affects Version/s: None
Fix Version/s: None

Type: Improvement
Reporter: Viera Zelcamova Assignee: Maros Marsalek
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Issue Links:
Blocks
blocks CONTROLLER-993 Milestone: Cleanup netconf code Resolved
blocks MDSAL-55 Topic: Continuos: Decrease technical ... Resolved
is blocked by CONTROLLER-978 Define a NormalizedNode-based notific... Resolved
is blocked by CONTROLLER-1092 Design NormalizedNode RPC Broker APIs... Resolved

 Comments   
Comment by Martin Sunal [ 13/Nov/14 ]

When a netconf device is connected as a mount point the side effect of using old APIs is that <get-config> RPC is sent for each element in instance-identifier.

for example REST call:
PUT
http://localhost:8080/restconf/config/opendaylight-inventory:nodes/node/NetconfDevice/yang-ext:mount/example:foo1/foo2/foo3/foo4

<foo4>
<data>hello</data>
</foo4>

would send 4 <get-config> RPCs = huge overhead!

This side effect is in binding aware world as well.

Comment by Maros Marsalek [ 16/Mar/15 ]

Done.

Regarding "Ensure parents" overhead:
When using new Binding aware APIs, it is possible to turn it ensure parents.
When using RESTCONF, its a RESTCONF thing and this functionality is required by the RESTCONF specification.

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