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-668 netconf <p>Currently we have two places where RFC7895 was implemented independently (mdsal-netconf-yang-library and restconf-nb modules).  See SchemaServiceToMdsalWriter and SchemaContextHandler classes.<br/> It could be an issue if we install these two modules together and they independently will change module-state.<br/> This functionality should be independent of both modules in a separate feature and lives in md-sal, alongside of yanglib client implementations there. And both restconf and netconf should be pulling it to runtime as a dependency.</p> <p>As a first step towards that, evaluate the content of netconf.git and create a apps/yanglib-mdsal-writer which both netconf-nb and restconf-nb will pull in.</p> NETCONF-668

RFC7895/RFC8525 implementation should be independent of any other modules in a separate feature

Improvement Highest Resolved Done Stephanie Brey Dee Vladyslav Marchenko pt Thu, 23 Apr 2020 12:45:21 +0000 Fri, 15 Dec 2023 01:04:16 +0000 Tue, 19 Sep 2023 06:28:47 +0000 7.0.0 netconf restconf-nb 0 2 <p>So the long-term solution for this would be to have a separate, dynamic datastore shard, which would not need to be written but rather would react to schema being populated, and project that information as a datastore (i.e. similar to a JMX bean). The trouble is a bit clustered environment – DOMSchemaService is a local property, yet the datastore is replicated, hence ... yanglib really becomes a per-datastore (in sense of <a href="https://tools.ietf.org/html/rfc8342)" class="external-link" target="_blank" rel="nofollow noopener">https://tools.ietf.org/html/rfc8342)</a> thing and DOMSchemaService is really on its way out.</p> <p>Unfortunately we are not there yet with the respective interfaces, so a simple split here, perhaps an integration with singleton-service and we could call it a day.</p> Relates MDSAL-833 MDSAL-835 NETCONF-1093 MDSAL-834 NETCONF-1196 Development Rank 0|i03s2f: