...
| # | Issue | Notes | Decision |
|---|---|---|---|
| 1 | Separating of Interfaces | Tony recommended NOT to split the interfaces.
| Check with stakeholders (Peter and Kieran) |
Description
Currently it is only possible to register a single dmi-plugin service name with NCMP.
...
These changes must be backward compatible with the existing Istanbul release where the dmi-plugin is a single service managing both model and data requests.
Register 2 separate plugins for different responsibilities model v. data (for scaling purposes)
Backward compatible! ie can stil register 1 plugin for both (ONAP plugin will keep using that)
Basic checks while registering: Either 2 separate Plugins OR 1 common plugin for both responsibilities. If not reject registration!
Required DB Schema update, see https://wiki.onap.org/display/DW/CPS-352+%3A+Create+yang-model+for+DMI-registry+data (new revision of that model) Possible add 2 new leaves for separate registration
Proposal Diagram
| draw.io Diagram | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...