OpenDaylight JIRA https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 [NETCONF-10] Separate schema context for config subsystem and md-sal https://jira.opendaylight.org/browse/NETCONF-10 netconf <p>Operating System: All<br/> Platform: All</p> NETCONF-10 Separate schema context for config subsystem and md-sal Improvement Resolved Won't Do Unassigned Viera Zelcamova Tue, 4 Nov 2014 15:33:16 +0000 Fri, 15 Mar 2019 22:22:09 +0000 Tue, 24 Nov 2015 14:16:29 +0000 netconf 0 4 <p>Config subsystem has a view of the entire schema context in ODL. Its view should be limited only to config subsystem related yang models using e.g. proxy schema context provider. The entire schema context with all models is confusing to the users of config subsystem especially using NETCONF interface.</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/14599/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/14599/</a></p> <p><a href="https://git.opendaylight.org/gerrit/#/c/14599/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/14599/</a></p> <p><a href="https://git.opendaylight.org/gerrit/#/c/14599/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/14599/</a></p> <p>This improvement remains in Waiting for review. The feature is finished, however it is not activated. To activate the feature use following commit:</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/14599/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/14599/</a></p> <p>The reasons for leaving this commit unmerged are stated in gerrit.</p> <p>Move to NETCONFI project.</p> <p>From the gerrit patchset:<br/> There are 2 issues with using this:<br/> 1. If a config file anywhere in the downstream project mentions yang schema that is not directly in use by config subsystem, the config pusher will fail to push such config. It is guaranteed that such cases are present in at least one downstream project. This means we will break the features of downstream projects during the startup of a controller.<br/> 2. Is there any benefit of mentioning non-config yang files (yang files for md-sal) in the initial config file ? e.g. it makes a guarantee (to some extent) that the module will be spawned after the md-sal knows about yang model that is going to be used by the module towards the md-sal ? If yes, this might cause further intermittent breakage for the controller startup.</p> Development External issue ID 2307 External issue URL Issue Type Rank 0|i01vwf: