You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

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

InterfaceResponsibilitiesTarget AudienceCurrent PrefixProposed PrefixExamples URI'sURI's after proposed changes
xNF Model Sync
CPS-NCMP-I-01
  1.  Register Plug-in CM-Handles
DMI Plugin Instance/ncmp

/ncmpInventory1

OR

/ncmpDmi

/ncmp/v1/ch

/ncmpInventory/v1/ch

OR

/ncmpDmi/v1/ch

DMI-I-01
  1. Retrieve module-references
  2. Retrieve yang module resources
  3. Add Cm-Handle (temporary)
Internal/dmi/dmi/modules2

dmi/v1/ch/{cmHandle}/modules/

dmi/v1/ch/{cmHandle}/moduleResources

dmi/v1/inventory/cmHandles

dmi/modules/v1/ch/{cmHandle}/references/

dmi/modules/v1/ch/{cmHandle}/resources

dmi/v1/inventory/cmHandles

xNF Data Access
CPS-E-05
  1. Read xNF Data
  2. Create (add) xNF Data
  3. Update xNF Data
  4. Delete xNF Data

External clients, CM Data consumers

(northbound)

/ncmp/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-02
  1. Read xNF Data
  2. Create (add) xNF Data
  3. Update xNF Data
  4. Delete xNF Data
Internal
(NCMP)		/dmi/dmi/data3

dmi/v1/ch/{cmHandle}/data/ds/ncmp-datastore:passthrough-operational

dmi/v1/ch/{cmHandle}/data/ds/ncmp-datastore:passthrough-running

dmi/data/v1/ch/{cmHandle}/ds/ncmp-datastore:passthrough-operational

dmi/data/v1/ch/{cmHandle}/ds/ncmp-datastore:passthrough-running

Proposed Changes (for clear interface separation)

  1. Change prefix for CPS-NCMP-I-01 from ncmp to ncmpInventory  or ncmpDmi
  2. Change prefix for DMI-I-01 from dmi to dmi/modules The methods on this interface do NOT need to complete 'generic data request body' (see below) developed for the data access methods.
    1. "Retrieve module-references" method only requires 'cmHandleProperties' in request body (payload)
    2. "Retrieve yang module resources" method requires both  'cmHandleProperties' and 'data' payload. 'Data' will contain a well defined  json (object) of module references
    3. Temporary hosted on this interface no changes required at all. "Add Cm-Handle" method does not require a request body at all
  3. Change prefix for DMI-I-02 from dmi to dmi/data
    1. All methods on this interface will use the 'generic data request body' for data access

CPS-645 - Getting issue details... STATUS Will cover item #1 above

CPS-706 - Getting issue details... STATUS The fact that DMI-I-01 and DMI-I-02 were not clearly separated lead to this bug. Items #2 and #3 are now being suggested to fix this bug and introduce clear separation off the DMI Interfaces

Request Format for Data Access

request body
{
  “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