> odl-{$module}-cfg

I would recommend $module to be decomposed as $project-$functionality
to give each project a freedom to name their functionalities freely, without risking name conflicts with other projects.

Simplified example: odl-bgpcep-bgp for a mdsal module, odl-bgpcep-bgp-cfg for corresponding config subsystem module.
(Of course bgpcep already has several BGP-related modules.)

Note that ideally this should also apply to fundamental ODL modules, for example not "config", but "odl-controller-config".

Hi Ankit,
this bug is far-reaching that seems obvious - renaming YANG models
may result in API and cross-project change which is not obvious at first sight:

• models are imported by name

• RESTCONF URIs uses model name

• some of Java generated APIs uses model name as base for their name

Hi carol,
I am thinking of working on this bug.

can you please tell me know if i can work on this bug individually and

if yes, I suppose making naming changes in POM of these config modules will be enough.
Is that what, this bug is intend to descibe?

This bug is part of the project to Move all ADSAL associated component bugs to ADSAL