Refactor NETCONF node defaults 40/98940/9
authorIvan Hrasko <ivan.hrasko@pantheon.tech>
Mon, 6 Dec 2021 10:58:02 +0000 (11:58 +0100)
committerRobert Varga <robert.varga@pantheon.tech>
Mon, 20 Dec 2021 12:01:51 +0000 (13:01 +0100)
commit2dfc7efb77c6704a0cd397dbd82c2709b14d29ee
treea0af6ebbdadd41671cbfb4ea2b50efa027b389ae
parent4b11379209aafd2bcaf9a9ee874dcb1569bdde8f
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>
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