[NETCONF-25] Clustering : It should be possible to mount a netconf device on one controller instance and access it from any other node in the cluster Created: 15/May/15 Updated: 15/Mar/19 Resolved: 05/Jan/16 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | ||
| Reporter: | Moiz Raja | Assignee: | Tomas Cere |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||
| Description |
|
Today if we mount a netconf device on one controller instance and then try to change the netconf devices configuration or get it's configuration/operational data from another instance in the cluster it does not work. This is because updates to the netconf device are not routed to the right instance of the cluster. This problem also exists with rpc. |
| Comments |
| Comment by Robert Varga [ 17/May/15 ] |
|
There may be two approaches: 1) Expose the NETCONF operations via RPCs bound to a node in an inventory instance, hence routed RPCs will work. It will not solve RESTCONF datastore access 2) Make mount instances a global thing, but then we need to deal with multi-instance coexistence. |
| Comment by Tomas Cere [ 05/Jan/16 ] |
|
https://git.opendaylight.org/gerrit/#/q/topic:netconf-clustering |