https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/NETCONF-913 netconf <p>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.</p> <p>sal-netconf-connect only cares about it exposing a (non-empty) YangInstanceIdentifier usable to create mount points.</p> <p>Extract the baseline interface and make netconf-topology implement it with its own class.</p> NETCONF-913

RemoteDeviceId should capture only MD-SAL preference

Improvement Medium Resolved Done Robert Varga Robert Varga Fri, 11 Nov 2022 22:37:20 +0000 Mon, 2 Jan 2023 11:05:00 +0000 Mon, 2 Jan 2023 11:05:00 +0000 5.0.0 netconf 0 1 <p>On further investigation, all we need is</p> <p> </p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> <span class="code-keyword">public</span> record RemoteDeviceId(<span class="code-object">String</span> name, InetAdress address); </pre> </div></div> <p>No further magic. Note: for migration reasons we still need to retain DEFAULT_TOPOLOGY_NAME as a central constant.</p> <p> </p> Blocks NETCONF-918 NETCONF-921 NETCONF-935 Development Rank 0|i043ef: