<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:16:05 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[NETCONF-857] Export supported features to ietf-yang-library</title>
                <link>https://jira.opendaylight.org/browse/NETCONF-857</link>
                <project id="10142" key="NETCONF">netconf</project>
                    <description>&lt;p&gt;Multiple netconf components deal with ietf-yang-library. Audit all of them and update them:&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;when we are creating a view from EffectiveModelContext we need to examine FeatureEffectiveStatements (or FeatureDefinitions) present in a particular module to construct the list of supported features&lt;/li&gt;
	&lt;li&gt;when we are creating an EffectiveModelContext, we need to pass down the set of supported features to the parser&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;The following need to be updated:&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;org.opendaylight.netconf.mdsal.yang.library.YangLibraryWriter&lt;/li&gt;
	&lt;li&gt;org.opendaylight.netconf.sal.connect.netconf.NetconfDevice (based on LibraryModulesSchemas)&lt;/li&gt;
	&lt;li&gt;org.opendaylight.yanglib.impl.YangLibProvider (this might be a bit tricky, it seems it&apos;s doing multple things)&lt;/li&gt;
&lt;/ol&gt;
</description>
                <environment></environment>
        <key id="35207">NETCONF-857</key>
            <summary>Export supported features to ietf-yang-library</summary>
                <type id="10100" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10310&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="2" iconUrl="https://jira.opendaylight.org/images/icons/priorities/critical.svg">High</priority>
                        <status id="10003" iconUrl="https://jira.opendaylight.org/images/icons/status_generic.gif" description="">Confirmed</status>
                    <statusCategory id="2" key="new" colorName="blue-gray"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="PeterSuna">Peter Suna</assignee>
                                    <reporter username="rovarga">Robert Varga</reporter>
                        <labels>
                            <label>pick-next</label>
                            <label>pt</label>
                    </labels>
                <created>Thu, 3 Feb 2022 08:53:04 +0000</created>
                <updated>Mon, 22 Jan 2024 21:54:47 +0000</updated>
                                                            <fixVersion>7.0.0</fixVersion>
                    <fixVersion>5.0.10</fixVersion>
                    <fixVersion>6.0.7</fixVersion>
                                    <component>netconf</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="70709" author="JIRAUSER14403" created="Mon, 4 Apr 2022 12:12:36 +0000"  >&lt;p&gt;YangLibraryWriter is done and merged. Only other two left.&lt;/p&gt;</comment>
                            <comment id="71564" author="petersuna" created="Tue, 25 Oct 2022 09:51:35 +0000"  >&lt;p&gt;I found out that &lt;a href=&quot;https://github.com/opendaylight/netconf/blob/master/netconf/sal-netconf-connector/src/main/java/org/opendaylight/netconf/sal/connect/netconf/LibraryModulesSchemas.java&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;LibraryModulesSchemas&lt;/a&gt; is not working properly and contains several issues.&lt;/p&gt;

&lt;p&gt;Wrong initialization of &lt;a href=&quot;https://github.com/opendaylight/netconf/blob/master/netconf/sal-netconf-connector/src/main/java/org/opendaylight/netconf/sal/connect/netconf/LibraryModulesSchemas.java#L93&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;LIBRARY_CONTEXT&lt;/a&gt; constant could be fixed with this:&lt;br/&gt;
&lt;a href=&quot;https://git.opendaylight.org/gerrit/c/netconf/+/102761/5&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/c/netconf/+/102761/5&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Wrong handling response from device could be fixed with this:&lt;br/&gt;
&lt;a href=&quot;https://git.opendaylight.org/gerrit/c/netconf/+/102827/1&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/c/netconf/+/102827/1&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;But the bigger problem is that the wrong RPC request is sent to the device. Instead of &lt;a href=&quot;https://github.com/opendaylight/netconf/blob/master/model/rfc6241/src/main/yang/ietf-netconf%402011-06-01.yang#L732&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;get&lt;/a&gt; RPC from ietf-netconf should be used &lt;a href=&quot;https://github.com/opendaylight/netconf/blob/9ab3c42bbf50e2a506f31f641548e06c0681f1e0/model/rfc8526/src/main/yang/ietf-netconf-nmda%402019-01-07.yang#L111&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;get-data&lt;/a&gt; from ietf-netconf-nmda in LibraryModulesSchemas#create:&lt;br/&gt;
&lt;a href=&quot;https://github.com/opendaylight/netconf/blob/9ab3c42bbf50e2a506f31f641548e06c0681f1e0/plugins/netconf-client-mdsal/src/main/java/org/opendaylight/netconf/client/mdsal/LibraryModulesSchemas.java#L166&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/opendaylight/netconf/blob/9ab3c42bbf50e2a506f31f641548e06c0681f1e0/plugins/netconf-client-mdsal/src/main/java/org/opendaylight/netconf/client/mdsal/LibraryModulesSchemas.java#L166&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;b&gt;YANG Library&lt;/b&gt; - &lt;a href=&quot;https://www.rfc-editor.org/rfc/rfc8525&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://www.rfc-editor.org/rfc/rfc8525&lt;/a&gt;&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;This version of the YANG library supports the Network Management Datastore&lt;br/&gt;
&#160; &#160;Architecture (NMDA) by listing all datastores supported by a network&lt;br/&gt;
&#160; &#160;management server and the schema that is used by each of these&lt;br/&gt;
&#160; &#160;datastores. &#160;&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;&lt;b&gt;NETCONF Extensions to Support the NMDA&lt;/b&gt; &lt;a href=&quot;https://www.rfc-editor.org/rfc/rfc8526&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://www.rfc-editor.org/rfc/rfc8526&lt;/a&gt;&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;The update to RFC 6241&lt;br/&gt;
&#160; &#160;adds new &amp;lt;get-data&amp;gt; and &amp;lt;edit-data&amp;gt; operations and augments existing&lt;br/&gt;
&#160; &#160;&amp;lt;lock&amp;gt;, &amp;lt;unlock&amp;gt;, and &amp;lt;validate&amp;gt; operations. &#160;The update to RFC 7950&lt;br/&gt;
&#160; &#160;requires the usage of the YANG library (described in RFC 8525) by&lt;br/&gt;
&#160; &#160;NETCONF servers implementing the NMDA.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;So ietf-yang-library should be used with NMDA because data saved in ietf-yang-library model are visible only in operation data store.&lt;br/&gt;
&lt;a href=&quot;https://www.rfc-editor.org/rfc/rfc8525#page-6&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://www.rfc-editor.org/rfc/rfc8525#page-6&lt;/a&gt;&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;All data nodes in the &quot;ietf-yang-library&quot; module are &quot;config&lt;br/&gt;
   false&quot; and thus only accessible in the operational state datastore. &lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Therefore, data from ietf-yang-library could be retrieved only with &lt;a href=&quot;https://github.com/opendaylight/netconf/blob/9ab3c42bbf50e2a506f31f641548e06c0681f1e0/model/rfc8526/src/main/yang/ietf-netconf-nmda%402019-01-07.yang#L111&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;get-data&lt;/a&gt; which can specified target data-store.&lt;/p&gt;</comment>
                            <comment id="71603" author="petersuna" created="Tue, 8 Nov 2022 11:55:17 +0000"  >&lt;p&gt;I have added supported features to YangLibProvider. But these changes are not properly tested due to issues I have found.&lt;br/&gt;
&lt;a href=&quot;https://jira.opendaylight.org/browse/NETCONF-910&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://jira.opendaylight.org/browse/NETCONF-910&lt;/a&gt;&lt;br/&gt;
&lt;a href=&quot;https://jira.opendaylight.org/browse/NETCONF-909&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://jira.opendaylight.org/browse/NETCONF-909&lt;/a&gt;&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                                                <inwardlinks description="is blocked by">
                                        <issuelink>
            <issuekey id="36301">NETCONF-909</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="36302">NETCONF-910</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="34941">YANGTOOLS-1368</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="35205">MDSAL-719</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i041dj:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>