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.
| Drawio |
|---|
| border | true |
|---|
| |
|---|
| diagramName | NCP DMI Plugin Options |
|---|
| simpleViewer | false |
|---|
| width | |
|---|
| links | auto |
|---|
| tbstyle | top |
|---|
| lbox | true |
|---|
| diagramWidth | 1021 |
|---|
| revision | 1 |
|---|
|
To realize this request the cmhandle registration (as well as update and delete when implemented in Jakarta) interfaces need updates to support a dmiDataPlugin and a dmiModelPlugin definition.
...
| DMI notifies NCMP of new , deleted or changed cmhandles DMI Plugin NCMP. Including initial registration | POST | {ncmpRoot}/ncmp/v1/ch/ | Scenario : DMI notifies NCMP of new cmhandles
Method : POST
URI : {ncmpRoot}/ncmp/v1/ch/
Header :
Content-Type: application/json
Request BodyRequest Body : {
"dmiDataPlugin" : "onap.dmi.data-plugin",
"dmiModelPlugin" : "onap.dmi.model-plugin",
"createdCmHandles" : [ { "cmHandle" : "rf4er5454",
"cmHandleProperties" :
{ "subSystemId" : "system-001" }
}, {..} ],
"updatedCmHandles" : [ .. ],
"removedCmHandles" : [ "node-1", "node-2" , ... ]
}
|
json attributes: - "dmiDataPlugin"/"dmiModel" are resolvable service names
- "createdCmHandles" used for initial cm handle registrations or subsequent
cmhandle creations - "updatedCmHandles"
Used for updates to cmhandles. Same structure as for create handles - "removedCmHandles" array of cmhandles that have been deleted
|
openAPI Updates
To support this the equivalent openAPI will be similar to the below in bold.
...