<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:16:10 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-892] Reorganize NETCONF source code repository</title>
                <link>https://jira.opendaylight.org/browse/NETCONF-892</link>
                <project id="10142" key="NETCONF">netconf</project>
                    <description>&lt;p&gt;Current netconf.git layout and artifact naming and artifact split up is far from navigable. Reorganize the repository and artifacts to split the individual layers and interactions, so that common RESTCONF/NETCONF bits are shared and there is a clear distinction as to which layer a particular artifact belongs to.&lt;/p&gt;

&lt;p&gt;Overall theme here is that we have three basic layers:&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;protocol handlers, i.e. session setup, communication and low-level logic&lt;/li&gt;
	&lt;li&gt;protocol plugins, i.e. how protocols interact with MD-SAL&lt;/li&gt;
	&lt;li&gt;applications, i.e. high-level components providing things like netconf-topology&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;Baseline layout is something along the lines of:&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;protocol/common
protocol/netconf
protocol/restconf
plugin/netconf-nb
plugin/netconf-sb
plugin/restconf-nb
apps/netconf-topology
apps/openapi-nb&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;This will entail renaming artifacts and moving code around to fit the architecture. On netconf side, this also means we need to take into account for the &lt;a href=&quot;#page-9&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;4 layers in NETCONF&lt;/a&gt;,] i.e.&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;transport (Netty, SSHD)&lt;/li&gt;
	&lt;li&gt;messages (netconf.xsd and its manifestation in Java)&lt;/li&gt;
	&lt;li&gt;operations (specific operations, bound to NormalizedNode&lt;img class=&quot;emoticon&quot; src=&quot;https://jira.opendaylight.org/images/icons/emoticons/help_16.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;)&lt;/li&gt;
	&lt;li&gt;content (NormalizedNode backend)&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;This split seems to be beneficial to RESTCONF as well, although the boundaries there are less clear (transport is HTTP, messages map 1:1 to operations, operations are HTTP requests).&lt;/p&gt;</description>
                <environment></environment>
        <key id="36015">NETCONF-892</key>
            <summary>Reorganize NETCONF source code repository</summary>
                <type id="10000" iconUrl="https://jira.opendaylight.org/images/icons/issuetypes/epic.svg">Epic</type>
                                            <priority id="1" iconUrl="https://jira.opendaylight.org/images/icons/priorities/blocker.svg">Highest</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="10002">Duplicate</resolution>
                                        <assignee username="rovarga">Robert Varga</assignee>
                                    <reporter username="rovarga">Robert Varga</reporter>
                        <labels>
                    </labels>
                <created>Tue, 12 Jul 2022 22:56:14 +0000</created>
                <updated>Fri, 5 May 2023 23:24:16 +0000</updated>
                            <resolved>Fri, 5 May 2023 23:24:16 +0000</resolved>
                                                                    <component>netconf</component>
                    <component>restconf-nb</component>
                    <component>restconf-openapi</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="71816" author="rovarga" created="Wed, 11 Jan 2023 01:18:29 +0000"  >&lt;p&gt;We have updated layout a bit:&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;/transport
/protocol
/plugins
/apps&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;are a thing now. More cleanup is needed, but that also entails modifying more code.&lt;/p&gt;</comment>
                            <comment id="72205" author="rovarga" created="Fri, 5 May 2023 23:24:16 +0000"  >&lt;p&gt;For some reason we have &lt;a href=&quot;https://jira.opendaylight.org/browse/NETCONF-944&quot; title=&quot;Reorganize source code layout&quot; class=&quot;issue-link&quot; data-issue-key=&quot;NETCONF-944&quot;&gt;NETCONF-944&lt;/a&gt;, which executes on this work and has way more items. There is no point in having two epics, and since &lt;a href=&quot;https://jira.opendaylight.org/browse/NETCONF-944&quot; title=&quot;Reorganize source code layout&quot; class=&quot;issue-link&quot; data-issue-key=&quot;NETCONF-944&quot;&gt;NETCONF-944&lt;/a&gt; wins in terms of links, I am choosing to close this down.&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_10005" key="com.pyxis.greenhopper.jira:gh-epic-color">
                        <customfieldname>Epic Color</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>ghx-label-1</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10004" key="com.pyxis.greenhopper.jira:gh-epic-label">
                        <customfieldname>Epic Name</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Reorganize netconf.git</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10003" key="com.pyxis.greenhopper.jira:gh-epic-status">
                        <customfieldname>Epic Status</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10000"><![CDATA[To Do]]></customfieldvalue>

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

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