<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:13:57 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-12] Sideload of models for nodes from remote yang sources repository</title>
                <link>https://jira.opendaylight.org/browse/NETCONF-12</link>
                <project id="10142" key="NETCONF">netconf</project>
                    <description>&lt;p&gt;The system should allow for easy sideload of models for devices that do not support netconf monitoring. An operator should be able to specify in the device configuration (along with IP address and credentials) where to load the models from. &lt;/p&gt;

&lt;p&gt;A user should be able to specify a URI for each model that the user wants to be loaded into the controller for the device. The URI can point to an http/https download, ftp download, or a local file.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="21025">NETCONF-12</key>
            <summary>Sideload of models for nodes from remote yang sources repository</summary>
                <type id="10100" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10310&amp;avatarType=issuetype">Improvement</type>
                                                <status id="5" iconUrl="https://jira.opendaylight.org/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="jmorvay@cisco.com">Jakub Morvay</assignee>
                                    <reporter username="jmedved@cisco.com">Jan Medved</reporter>
                        <labels>
                    </labels>
                <created>Mon, 10 Nov 2014 16:11:36 +0000</created>
                <updated>Fri, 15 Mar 2019 22:22:09 +0000</updated>
                            <resolved>Thu, 5 May 2016 15:40:41 +0000</resolved>
                                                                    <component>netconf</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>7</watches>
                                                                                                                <comments>
                            <comment id="38718" author="mmarsale@cisco.com" created="Thu, 19 Mar 2015 09:15:15 +0000"  >&lt;p&gt;This feature is (with limits) already present in ODL:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://wiki.opendaylight.org/view/OpenDaylight_Controller:Config:Examples:Netconf#Connecting_to_a_device_not_supporting_netconf_monitoring&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://wiki.opendaylight.org/view/OpenDaylight_Controller:Config:Examples:Netconf#Connecting_to_a_device_not_supporting_netconf_monitoring&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;It allows for side-loading of schemas from the cache/schemas folder&lt;/p&gt;</comment>
                            <comment id="38719" author="rovarga" created="Fri, 13 Nov 2015 12:57:50 +0000"  >&lt;p&gt;Move to NETCONFI project.&lt;/p&gt;</comment>
                            <comment id="38720" author="jmorvay@cisco.com" created="Tue, 26 Apr 2016 07:18:39 +0000"  >&lt;p&gt;Hi Alexis,&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://jira.opendaylight.org/browse/NETCONF-152&quot; title=&quot;Add support for yang-library in addition to netconf-monitoring&quot; class=&quot;issue-link&quot; data-issue-key=&quot;NETCONF-152&quot;&gt;&lt;del&gt;NETCONF-152&lt;/del&gt;&lt;/a&gt; is actually not a duplicate of this bug and this bug is not about adding support for ietf-yang-library to netconf. &lt;/p&gt;

&lt;p&gt;This new feature is about side-loading schemas for device from some remote yang sources repository. You can think of it as a remote cache/schema folder schema side-loading.&lt;/p&gt;

&lt;p&gt;You should be able to specify URL in the device configuration (either via netconf-topology or via netconf-connector) where to load the models from. We are using ietf-netconf-yang-library model for this, so maybe this is causing a confusion here. From the specified URL we download yang-library data (that is the list of modules with some basic information about each of them and URL that represents the YANG schema resource for each module or submodule) and register obtained schemas to schema registry.&lt;/p&gt;

&lt;p&gt;Part of the implementation will be also the ODL application (part of netconf project), where you can specify folder with schemas that you want to serve. The application will then generate URL for each present model and serve them on generated URLs. Application will also write list of present models and generated urls to yang-libray model. So you can use ODL as a central remote yang source library for other applications or other ODL instances or for its own netconf connections.&lt;/p&gt;

&lt;p&gt;Hope this is more clear now.&lt;/p&gt;</comment>
                            <comment id="38721" author="adetalhouet" created="Tue, 26 Apr 2016 12:35:01 +0000"  >&lt;p&gt;Hey Jakub,&lt;/p&gt;

&lt;p&gt;Ok I think I got the difference between the two bugs now:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://jira.opendaylight.org/browse/NETCONF-152&quot; title=&quot;Add support for yang-library in addition to netconf-monitoring&quot; class=&quot;issue-link&quot; data-issue-key=&quot;NETCONF-152&quot;&gt;&lt;del&gt;NETCONF-152&lt;/del&gt;&lt;/a&gt; is about adding support to the ietf-netconf-yang-library&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://jira.opendaylight.org/browse/NETCONF-12&quot; title=&quot;Sideload of models for nodes from remote yang sources repository&quot; class=&quot;issue-link&quot; data-issue-key=&quot;NETCONF-12&quot;&gt;&lt;del&gt;NETCONF-12&lt;/del&gt;&lt;/a&gt; (this one) is using ietf-netconf-yang-library to sideload schemas from remote repository&lt;/p&gt;

&lt;p&gt;What confused me was separating the support of the new ietf model and its usage to sideload schemas.&lt;/p&gt;

&lt;p&gt;Sorry for having mess-up the bugs and thanks for having clarifying that.&lt;/p&gt;</comment>
                            <comment id="38722" author="jmorvay@cisco.com" created="Wed, 4 May 2016 07:25:05 +0000"  >&lt;p&gt;Patch for sideloading schemas from remote yang schemas sources repositories:&lt;br/&gt;
&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/37630&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/37630&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="38723" author="jmorvay@cisco.com" created="Wed, 4 May 2016 19:25:45 +0000"  >&lt;p&gt;ODL application providing YANG schemas through web sercice:&lt;br/&gt;
&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/38348&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/38348&lt;/a&gt;&lt;/p&gt;</comment>
                    </comments>
                    <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_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2343</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10201" key="com.atlassian.jira.plugin.system.customfieldtypes:url">
                        <customfieldname>External issue URL</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[https://bugs.opendaylight.org/show_bug.cgi?id=2343]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10206" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Issue Type</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10308"><![CDATA[New Feature]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10204" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>ODL SR Target Milestone</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10338"><![CDATA[Boron-M3]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i01vwv:</customfieldvalue>

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