<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:15:01 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-432] add RESTCONF capability for schemaless mount</title>
                <link>https://jira.opendaylight.org/browse/NETCONF-432</link>
                <project id="10142" key="NETCONF">netconf</project>
                    <description>&lt;p&gt;it would be good if we could use the RESTCONF (and NETCONF) NBs to access schemaless mounts.  The current schemaless mount code doesn&apos;t allow this.&lt;/p&gt;

&lt;p&gt;Given that there&apos;s no YANG model to infer the URL structure for RESTCONF I suspect the best way to handle this is to create new RPCs that get, edit and delete data for schemaless devices - and which take the device name, subtree or xpath, and (for edit) the anyxml data to write as parameters.&lt;/p&gt;

&lt;p&gt;This was requested by Hu Wenbo &amp;lt;huwenbo1988@gmail.com&amp;gt;.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="21445">NETCONF-432</key>
            <summary>add RESTCONF capability for schemaless mount</summary>
                <type id="10100" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10310&amp;avatarType=issuetype">Improvement</type>
                                                <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="-1">Unassigned</assignee>
                                    <reporter username="giheron@cisco.com">Giles Heron</reporter>
                        <labels>
                    </labels>
                <created>Fri, 23 Jun 2017 10:08:44 +0000</created>
                <updated>Fri, 15 Mar 2019 22:22:42 +0000</updated>
                                                                            <component>restconf-nb</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="40104" author="jatoth@cisco.com" created="Tue, 1 Aug 2017 08:50:44 +0000"  >&lt;p&gt;Hi,&lt;/p&gt;

&lt;p&gt;NETCONF part is prepared for work with schemaless mounts. It seems to be good idea to use RPCs to handle this. It should work.&lt;/p&gt;</comment>
                            <comment id="40105" author="giheron@cisco.com" created="Tue, 1 Aug 2017 09:09:08 +0000"  >&lt;p&gt;is it possible to make a rough estimate of how much work would be required?&lt;/p&gt;

&lt;p&gt;it&apos;d be great if we could get this in Oxygen.&lt;/p&gt;</comment>
                            <comment id="40106" author="huwenbo1988@gmail.com" created="Tue, 1 Aug 2017 12:06:03 +0000"  >&lt;p&gt;Just like what I wrote before.&lt;br/&gt;
Maybe we can use a specific endpoint which accepts any xml payload and outputs the response directly from netconf device.&lt;br/&gt;
Or write a kind of meta yang model that everything is anyxml and it is loaded as a default model, so that we can get rid of irrelevant model errors.&lt;/p&gt;</comment>
                            <comment id="40107" author="jatoth@cisco.com" created="Mon, 7 Aug 2017 14:41:16 +0000"  >&lt;p&gt;Hi guys,&lt;/p&gt;

&lt;p&gt;I got problem with use of anyxml. But there exists solution by replacing anyxml with leaf as string (string can be converted into DOMSource/DOM doc and build anyxml node)&lt;/p&gt;

&lt;p&gt;I think it would take around 5MD (3-4 MD for implementation, 1MD for junit tests)&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>8732</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=8732]]></customfieldvalue>

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

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

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

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