<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:16:14 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-919] Do not touch configuration datastore during netconf-topology init</title>
                <link>https://jira.opendaylight.org/browse/NETCONF-919</link>
                <project id="10142" key="NETCONF">netconf</project>
                    <description>&lt;p&gt;&lt;a href=&quot;https://jira.opendaylight.org/browse/NETCONF-128&quot; title=&quot;Cannot detect netconf up and running when odl-netconf-connector-* is not used&quot; class=&quot;issue-link&quot; data-issue-key=&quot;NETCONF-128&quot;&gt;&lt;del&gt;NETCONF-128&lt;/del&gt;&lt;/a&gt; introduced an explicit merge into configuration during initialization. As such, configuration is introduced by user &#8211; if they do not wish the configuration to be there, it will not be there.&lt;/p&gt;

&lt;p&gt;This is lifecycle problem as well &#8211; if an ODL instance has netconf-topology installed, but then it gets uninstalled, the configuration will still remain and at some point will end up being invalid because the corresponding models are not there. At that point CDS will prune it (IIRC), but this is just magic and a problem waiting to happen.&lt;/p&gt;

&lt;p&gt;As such, if there is nothing configured, there should equally be nothing in operational datastore and netconf topology should be just lying dormant waiting for configuration to appear.&lt;/p&gt;

&lt;p&gt;As for the detection &#8211; the CSIT suite knows what it installs and the ready service reports when all components are initialized &#8211; which is enough indicate things.&lt;/p&gt;</description>
                <environment></environment>
        <key id="36423">NETCONF-919</key>
            <summary>Do not touch configuration datastore during netconf-topology init</summary>
                <type id="10100" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10310&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="3" iconUrl="https://jira.opendaylight.org/images/icons/priorities/major.svg">Medium</priority>
                        <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="rovarga">Robert Varga</assignee>
                                    <reporter username="rovarga">Robert Varga</reporter>
                        <labels>
                    </labels>
                <created>Mon, 5 Dec 2022 19:50:58 +0000</created>
                <updated>Thu, 8 Dec 2022 02:20:03 +0000</updated>
                            <resolved>Thu, 8 Dec 2022 02:20:03 +0000</resolved>
                                                    <fixVersion>5.0.0</fixVersion>
                                    <component>netconf</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                    <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="21141">NETCONF-128</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </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|i043nr:</customfieldvalue>

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