[NETCONF-913] RemoteDeviceId should capture only MD-SAL preference Created: 11/Nov/22 Updated: 02/Jan/23 Resolved: 02/Jan/23 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0 |
| Type: | Improvement | Priority: | Medium |
| Reporter: | Robert Varga | Assignee: | Robert Varga |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Description |
|
RemoteId currently has a strong binding to network-topology. That model is a prototype and what it really expresses is the identifier coupled to DOMMountPointService. sal-netconf-connect only cares about it exposing a (non-empty) YangInstanceIdentifier usable to create mount points. Extract the baseline interface and make netconf-topology implement it with its own class. |
| Comments |
| Comment by Robert Varga [ 01/Jan/23 ] |
|
On further investigation, all we need is
public record RemoteDeviceId(String name, InetAdress address); No further magic. Note: for migration reasons we still need to retain DEFAULT_TOPOLOGY_NAME as a central constant.
|