Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

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

Description

Currently we have two places where RFC7895 was implemented independently (mdsal-netconf-yang-library and restconf-nb modules).  See SchemaServiceToMdsalWriter and SchemaContextHandler classes.
It could be an issue if we install these two modules together and they independently will change module-state.
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.

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.

Activity

Show:

Robert Varga April 26, 2020 at 8:48 PM

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 https://tools.ietf.org/html/rfc8342) thing and DOMSchemaService is really on its way out.

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.

Done

Details

Assignee

Reporter

Labels

Components

Fix versions

Priority

Created April 23, 2020 at 12:45 PM
Updated February 6, 2025 at 2:16 PM
Resolved September 19, 2023 at 6:28 AM