Refactor NETCONF node defaults 33/99133/3
authorIvan Hrasko <ivan.hrasko@pantheon.tech>
Mon, 6 Dec 2021 10:58:02 +0000 (11:58 +0100)
committerRobert Varga <nite@hq.sk>
Wed, 22 Dec 2021 12:50:40 +0000 (12:50 +0000)
commit23a0035c3e7c633990619b10f133c31b0f1fc3d1
tree95db127ad0ed9ed895487d9bec8d65f72c8c7f05
parent0dd89ad5c09a3814480da7ad0e29d3ad5c189600
Refactor NETCONF node defaults

In fact, the difference between devices connected by call-home and
created manually in NETCONF topology is that call-home devices do
not have any data in configuration data-store.

Configuration data is used during the connection setup.

We can create full default configuration node for call-home connected
device to unify the processing of both kind of devices.

In addition, MDSAL now supports default values in data-store so we
can remove those values from AbstractNetconfTopology.

JIRA: NETCONF-832
Change-Id: Ib58ca344a7d74612cb7d049805a3e3c9279986d4
Signed-off-by: Ivan Hrasko <ivan.hrasko@pantheon.tech>
Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
(cherry picked from commit 2dfc7efb77c6704a0cd397dbd82c2709b14d29ee)
netconf/callhome-provider/src/main/java/org/opendaylight/netconf/callhome/mount/CallHomeMountSessionContext.java
netconf/callhome-provider/src/test/java/org/opendaylight/netconf/callhome/mount/CallHomeMountSessionContextTest.java
netconf/netconf-topology-impl/src/test/java/org/opendaylight/netconf/topology/impl/NetconfTopologyImplTest.java
netconf/netconf-topology/src/main/java/org/opendaylight/netconf/topology/spi/AbstractNetconfTopology.java