[NETCONF-154] Deprecate Netconf Loopback Mount Through Config Subsystem Created: 23/Feb/16  Updated: 15/Mar/19  Resolved: 11/Jan/17

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

Type: Improvement
Reporter: Ryan Goulding Assignee: Alexis de Talhouët
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


 Description   

Deprecate the Netconf Loopback mounting mechanism (through config subsystem) in favor of CDS (spawning netconf connectors through topology configuration). The latter topic is discussed in detail here:

https://wiki.opendaylight.org/view/OpenDaylight_Controller:Config:Examples:Netconf#Spawning_netconf_connectors_via_topology_configuration

A description of Upgrade Considerations for existing data is here:

https://wiki.opendaylight.org/view/OpenDaylight_Controller:Config:Examples:Netconf#Upgrade_Considerations

The idea is that this enhancement bug requires replacement of missing mechanisms that are needed to successfully deprecate mount via config subsystem. Namely, this includes:
1) Providing a mechanism to automatically mount a device at controller startup.
2) Mounting the controller at startup.

 Comments   
Comment by Vratko Polak [ 15/Mar/16 ]

> Mounting the controller at startup.

Which one?
In cluster, each member should have its own device, which needs a unique name.
Is there a way to query akka configuration to see role (like "member-1")?

> Providing a mechanism to automatically mount a device at controller startup.

Config datastore is persisted by default, so that may give a simple workaround.

Comment by Alexis de Talhouët [ 07/Nov/16 ]

https://git.opendaylight.org/gerrit/#/c/47906/

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