https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/NETCONF-98 netconf <p>Currently on Beryllium there is <a href="https://jira.opendaylight.org/browse/BGPCEP-306" title="Module &quot;bgp&quot; name conflict" class="issue-link" data-issue-key="BGPCEP-306"><del>BGPCEP-306</del></a> where conflict on "bgp" model seems to have a consequence of Resconf not becoming available (/restconf/modules keeps returning 503).</p> <p>Is there a reason to prevent Restconf to function?<br/> Is there a way to allow majority of correct models to work?</p> <p>Combination of <a href="https://jira.opendaylight.org/browse/BGPCEP-306" title="Module &quot;bgp&quot; name conflict" class="issue-link" data-issue-key="BGPCEP-306"><del>BGPCEP-306</del></a> and this is currently causing failure of integration/distribution verify job, which prevents projects to add or edit their integration features.</p> <p>Operating System: All<br/> Platform: All</p> NETCONF-98

Module name conflict limits unrelated functionality

Bug Resolved Won't Do Unassigned Vratko Polak Mon, 9 Nov 2015 17:18:42 +0000 Fri, 15 Mar 2019 22:22:16 +0000 Wed, 2 Dec 2015 13:01:05 +0000 netconf 0 5 <p>Moving to netconf project.</p> <p>RESTCONF specification requires the use of module name as the prefix for namespace resolution in URLs. Therefore modulename-to-namespace mapping has to be unique for URLs to be properly resolved.</p> <p>I think this needs coordinated effort across all projects to give odl-specific models a structure which will be non-colliding. The OpenBGP model is a standard one &#8211; I am afraid we cannot move that one.</p> <p>&gt; Therefore modulename-to-namespace mapping has to be unique for URLs to be properly resolved.</p> <p>This Change Request is about what happens when the mapping is not unique anyway (for example users may be installing their own poorly named modules).</p> <p>Improper resolution could lead to HTTP status 400 response on affected module name, but it is hardly a reason for status 503 on all restconf requests.</p> <p>This is a property of the protocol and a well known limitation of ODL.</p> <p>&gt; a well known limitation of ODL.</p> <p>Well, the correct response is WONTFIX if this limitation is practically unavoidable,<br/> or set milestone to Boron (or later) if it just low priority.</p> <p>I do not think this Change Request is INVALID.</p> <p>Ok, changed to WONTFIX, since given current constraints it can not be fixed (supporting both at same time).</p> Development External issue ID 4600 External issue URL Issue Type ODL SR Target Milestone Rank 0|i01wfz: