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-22 netconf <p>Given the with clustering enabled data is persistent, how will Netconf behave in the light of bugs 2920 and 2921?</p> <p>SFC relies on Netconf maintaining the netconf topology accurately so defining the behavior in the light of data persistence and fixing any bugs is paramount for SFC to work properly. </p> <p>In the case of Netconf, it seems there is a further complication in that it maintains a list of netconf nodes it knows about in current_config.xml across Karaf reboots.</p> <p>Operating System: All<br/> Platform: All</p> NETCONF-22

Need to define Netconf Clustering/Data Persistence Behavior

Bug Resolved Done Tomas Cere Reinaldo Penno Tue, 31 Mar 2015 07:19:48 +0000 Fri, 15 Mar 2019 22:22:10 +0000 Mon, 22 Feb 2016 13:24:48 +0000 netconf Thu, 3 Dec 2015 00:00:00 +0000 0 4 <p>Move to NETCONFI project.</p> <p><a href="https://git.opendaylight.org/gerrit/#/q/topic:netconf-clustering" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/q/topic:netconf-clustering</a></p> <p>I don't see where in those patches we actually "define Netconf Clustering/Data Persistence Behavior". Did I miss something? It would be nice to actually understand what the desired behavior was.</p> <p>Configuration persistance as of now is defined by CDS behaviour instead of seperate behaviour model inherited via use of config subsystem.</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/27052/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/27052/</a></p> Development External issue ID 2922 External issue URL ODL SR Target Milestone Rank 0|i01vz3: