Overview

Scope

What is this release trying to address?

1. Upgradability (CPS, NCMP)
   1.  Version strategy to  control Continuous Delivery (CPS and NCMP)
      1. Technical debt of NCMP data be handled by Liquibase in CPS
   2. Yang Module Upgrade
      1. backward compatible
      2. backward incompatible
         1. Data Transformation/Migration
         2. Drop (and resync) 
2. Service Maturity CPS
   1. Delivery Pipelines 
   2. Helm best practices (design rules)
   3. FOSS audit
3. Service Maturity NCMP (TBC)
4. Performance (CPS, NCMP)
   1. CPS Data read 
   2. CPS Model-based query
   3. Registration algorithm change (using schemaSet hash)
5. CM Handle Connectivity State
6. Notification Configuration
   
   1. Model based
   2. Instance based
7. Query Propagation
   
   1. Amalgamate responses
   2. Capability Exchange (during registration/updates) 

Stretch Goals

1. Forwarding non-passtrough 
   
   1. data request
   2. notifications
2. Cache Configuration
   1. Model based
   2. Instance based, container, leaf
3. AAI integration
4. Extend Read(query) access to cached data (datastore ncmp-datastores:operational)
   1. cpsPath support in NCMP
   2. field' and 'depth' RestConf-Like support in CPS (and NCMP)
5. Extend CPS-Path (query) capabilities
6. CPS Target Based Access Control (TBAC)
   1. Ownership of dataspaces using OAuth2 
7. NCMP Access Control
8. Multiple Identifiers for Anchors (CM Handles)

Minimum Viable Product

N/A

Requirements

ONAP Best Practices (Global Requirements) and similar

CPS-temporal Requirements (TBC)

CPS-CORE / CPS-NCMP Requirements

9CPS-NCMPBulk Operations (Get, Query)Allow bulk operations for NCMP (and/or) CPS REST Interfaces10
CPS-NCMPCM Handle Connectivity Freshness/Staleness
11CPS-Core /
CPS-NCMPSupport for list as top level data node
12CPS-Core /
CPS-NCMPSupport for multiple top-elements from different modules in one CM handle/anchor13NCMP-CPSSupport NCMP-CPS upgrade

Currently only custom upgrade is supported. (upon request)

Requirement: It shall be possible to upgrade NCMP-CPS from release N-1 to N (without requiring manual intervention/workarounds). N is defined as any release requested by ESH

• Note. Need to agree version strategy: use current ONAP x.y.z. numbering. Ericsson to communicate when a version is to be 'delivered' and 'y' increased

Technical Debt to be addressed: Liquibase is used in CPS to manage data(upgrades) in CPS

Study: Resolve technical debt (mixed data). NCMP Data upgrade. CPS Core need to support model upgrade so that NCMP can use it,

14CPS-Core
NCMP-CPSSupport multiple identifiers (alternatives for CM Handle ID)

15
Support for 'Instance Identifier'Should be possible to identify a cmhandle using multiple instance identifiers
16CPS-NCMPInvoke YANG modelled action

Always on operational datastore.  Supported for nmcp:passthrough-operational and if executed against ncmp:operational then it is always forwarded to dmi plugin.  Is there another story for forwarding to be included as a dependency? Always run as async request.  Is this dependent on CPS-1127  - see spin-off user stories table below this on.

KMC : Can we deprioritize - this can be run against passthrough-operational for now.  Just have to agree on the API / URL for the action to progress at this stage so that the passthrough-operational form is aligned with final operational form.

17
CPS-NCMPEnhanced query support

Currently the passthrough has an 'fields' parameter to do a scoped query.  Propose to support this in non-passthrough so it is promoted to a fully supported option, e.g. {ncmp-root}/ncmp/v1/ch/335ff/data/ds/ncmp-datastore:passthrough-operational?
              resourceIdentifier=/&options=(fields=ericsson-enm-comtop:ManagedElement/ericsson-enm-
              gnbcucp:GNBCUCPFunction/EndpointResource/LocalSctpEndpoint/attributes(sctpEndpointRef),
              scope=ericsson-enm-comtop:ManagedElement/ericsson-enm-gnbcucp:GNBCUCPFunction/
               EndpointResource/LocalSctpEndpoint/attributes(interfaceUsed==X2))

KMC : Do we support restconf like queries or xpath only?

18Move above 8CPS_Core / CPS-NCMPUpdate YANG schema-set for CM handle without removing and adding it

Cached data is not in scope. Need to specify orphan handling of YANG modules.

Needed for node upgrade scenario.

19CPS-NCMPRetrieve single module resource/v1/ch/{cm-handle}/modules/definitions/{moduleName}

20
CPS-Core / CPS-NCMPExisting CPS-path based queries across all CM handles for cached data

Look to define the interface specification for this only.

(but best way is to implement for operational/cached data to determine any output formatting issues)

21
CPS-Core /
CPS-NCMPAccess control for public interfaces (NCMP, CPS-Core, DMI?)KMC : What level of access control is there today - both on CPS and NCMP interfaces?

22
CPS-NCMPFine-grained cache configuration


23
CPS-NCMPSend notification for updated CM handle metadata (public CM handle properties or YANG modules)


24
CPS-Core /
CPS-NCMP

25CPS-NCMPSupport ncmp-datastores:running 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.

26TBCCPS-Core /
CPS-NCMPSupport ncmp-datastores:running for writing data (single CM handle, synchronous only)

27TBCCPS-CoreSend notifications on write operation in ncmp-datastores:running for (single CM handle, synchronous only)


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

29(ONAP) E2E Slicing Use-Case

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

31
CPS-NCMPInvoke YANG modelled RPC