- Created by Toine Siebelink, last modified on Oct 05, 2021
Interface Overview
Current Interface Description
There are 3 distinct parts to the DMI
i) Inventory: The Server side is NCMP, the client the DMI-Plugin
ii) model: The Server side is the DMI-Plugin, the client side is NCMP
iii) data: The server side is DMI-Plugin, the client side is NCMP
Interface | Responsibilities | Target Audience | Current Prefix | Examples URI's | Proposed Change |
---|---|---|---|---|---|
xNF Model Sync | |||||
CPS-NCMP-I-01 |
| DMI Plugin Instance | /ncmp | /ncmp/v1/ch | |
DMI-I-01 |
| Internal | /dmi | dmi/v1/ch/{cmHandle}/modules/ dmi/v1/ch/{cmHandle}/moduleResources dmi/v1/inventory/cmHandles | No Uri Changes but 'Generic Data Request Body' is not needed for these methods:
CPS-706 - Getting issue details... STATUS |
xNF Data Access | |||||
CPS-E-05 |
| External clients, CM Data consumers (northbound) | /ncmp | ncmp/v1/ch/{cm-handle}/data/ds/ncmp-datastore:passthrough-operational ncmp/v1/ch/{cm-handle}/data/ds/ncmp-datastore:passthrough-running | No Changes |
DMI-I-01 |
| Internal (NCMP) | /dmi | dmi/v1/ch/{cmHandle}/data/ds/ncmp-datastore:passthrough-operational dmi/v1/ch/{cmHandle}/data/ds/ncmp-datastore:passthrough-running | No changes required, all methods on this interface will use the 'generic data request body' for data access |
Request Format for Data Access
{
“operation”: “<operation>”, // Valid operations are: “create”, “read”, “update”, “patch” and “delete”.
"dataType": "<dataType>", // e.g. "application/yang.data"
“data”: { // Embedded data as a String.
<data> // required for create and update operations. Optional filter-data for read-operations
},
“cmHandleProperties”: { // Additional properties for CM handle previously added by DMI plugin and stored in NCMP.
<properties>
}
}
- No labels