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/MDSAL-62 mdsal <p>Config subsystem modules should follow naming convention:</p> <p>odl-{$module}-cfg for configuration of components </p> <p>Opendaylight specific MD-SAL related models should follow conventions:</p> <p>odl-{$module}</p> <p>Operating System: All<br/> Platform: All</p> MDSAL-62

Rename Opendaylight specific YANG modules to format odl-{$module}

Improvement Confirmed Unresolved Unassigned Tony Tkacik Thu, 13 Nov 2014 13:24:28 +0000 Mon, 19 Aug 2019 15:47:07 +0000 models 0 4 <p>This bug is part of the project to Move all ADSAL associated component bugs to ADSAL</p> <p>Hi carol,<br/> I am thinking of working on this bug.</p> <p>can you please tell me know if i can work on this bug individually and </p> <p>if yes, I suppose making naming changes in POM of these config modules will be enough.<br/> Is that what, this bug is intend to descibe?</p> <p>Hi Ankit,<br/> this bug is far-reaching that seems obvious - renaming YANG models<br/> may result in API and cross-project change which is not obvious at first sight:</p> <ul class="alternate" type="square"> <li>models are imported by name</li> <li>RESTCONF URIs uses model name</li> <li>some of Java generated APIs uses model name as base for their name</li> </ul> <p>&gt; odl-{$module}-cfg</p> <p>I would recommend $module to be decomposed as $project-$functionality<br/> to give each project a freedom to name their functionalities freely, without risking name conflicts with other projects.</p> <p>Simplified example: odl-bgpcep-bgp for a mdsal module, odl-bgpcep-bgp-cfg for corresponding config subsystem module.<br/> (Of course bgpcep already has several BGP-related modules.)</p> <p>Note that ideally this should also apply to fundamental ODL modules, for example not "config", but "odl-controller-config".</p> Blocks MDSAL-55 Development External issue ID 2380 External issue URL Rank 0|i02w2v: