Table of Contents

Overview

Scope

What is this release trying to address?

...

Minimum Viable Product

N/A

Requirements

CPS-Core Requirements

NCMP Requirements

Priority legend: 

CPS-CORE / CPS-NCMP Requirements

Responses always published by NCMP to the client topic.

dmi-plugin may publish to NCMP on a local/private topic.  Response event payload contains the public topic name. NCMPSupport public CM handle propertiesBasic support for public properties + query capability
10CPS-Core /
CPS-NCMPInvestigate Horizontal Scaling

11CPS-NCMP

Implement -async option for CRUD and Patch operations (for one CM-Handle)

Required for potentially long running requests

Note below to be agreed.,,

Responses always published by NCMP to the client topic.

dmi-plugin may publish to NCMP on a local/private topic.  Response event payload contains the public topic name. 

12CPS-NCMPRead access at datastore level
13CPS-821CoreYANG language extension supportInvestigation
12Read access at datastore level14CPS-NCMPSend notification for updated CM handle metadata (public CM handle properties or YANG modules)


15CPS-NCMP[investigation/spec] CM data notifications from NCMP to applications including subscriptionsIncludes definition of notification and payload format

16CPS-792NCMPImplementation of CM data notifications forwarded by NCMP from DMI to application


1713YANG language extension supportInvestigationCPS-73514Send notification for updated CM handle metadata (public CM handle properties or YANG modules)15[investigation/spec] CM data notifications from NCMP to applications including subscriptionsIncludes definition of notification and payload format16Implementation of CM data notifications forwarded by NCMP from DMI to application17Core /
CPS-NCMPSupport for HTTPS and authentication


18CPS-Core /
CPS-NCMPAccess control for public interfaces (NCMP, CPS-Core, DMI?)


19
CPS-NCMPSupport ncmp-datastores:operational for reading data (single CM handle, synchronous only)See CPS-391 page for details about supported operations and combinations. Note: There can be some overlap between work items for #5, #6, #11 and #12. Note: This item doesn't include accessing cached data as data sync is not available yet.
20
CPS-NCMPSupport ncmp-datastores:running for reading and writing data (single CM handle, synchronous only)See CPS-391 page for details about supported operations and combinations. Note: There can be some overlap between work items for #5, #6, #11 and #12.#12.

21
CPS-Core /
CPS-NCMP21Support for list as top level data node

22
CPS-Core /
CPS-NCMPSupport for multiple roots from different modules in one CM handle/anchor
23
CPS-NCMPExplicit (initial) data-sync for a CM handle (extend model-sync delivered in Istanbul)Triggered by client using REST endpoint on NCMP. Note: This item includes extended support for datastores to access the synced data.
24
CPS-NCMPSupport retrieval of YANG module sources for CM handle on the NCMP interface


25
CPS-Core /
CPS-NCMPUpdate YANG schema-set for CM handle without removing and adding itCached data is not in scope. Need to specify orphan handling of YANG modules.

26
CPS-Core /
CPS-NCMPschema-set update for CM handle with cached data presentNeed to address case with incompatible model changes.

27(ONAP) E2E Slicing Use-Case

28
CPS-NCMPAutomatic (optional) Data Sync Metadata (per cmHandle) controls whether this will happen or not

29
CPS-NCMPFine-grained cache configuration


30
CPS-Core /
CPS-NCMPExisting CPS-path based queries across multiple CM handles for cached data


31
CPS-NCMPInvoke YANG modelled action


32
CPS-NCMPInvoke YANG modelled RPC