Overview

Project NameEnter the name of the projectTarget Release NameMontrealProject Lifecycle StateIncubationParticipating Companies Deutsche Telecom (Tech Mahindra) , Ericsson, Fujitsu, Wipro

Scope

What is this release trying to address?

TBC

Minimum Viable Product

N/A

Requirements

Priority legend
Preliminary	Planned for current ONAP Release	In Progress	Paused/Blocked	Completed	De-scoped

ONAP Best Practices (Global Requirements) and similar

ONAP Requirement

Notes

CPS- Jira(s)

Jira

server	ONAP Jira
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	REQ-439

ONAP script might help us with common quality issues and save reviewing time

Jira

server	ONAP Jira
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	CPS-1324

CPS-CORE / CPS-NCMP Requirements

titleClosed Stories

Priority

Epic/Component/Owner/Team/Target

Description

Notes

Jira(s)

1

Jira
server ONAP Jira
serverId 425b2b0a-557c-3c0c-b515-579789cceedb
key CPS-1645
CPS-Core
Daniel Hanrahan
Community & Ericsson Team

1

2

Data Write/Read Performance

See also CPS-Core Read & Write (large load) Test Results from Wipro/Fujitsu

See Montreal Read/Write Performance for latest performance results (23/08)

Jira

server	ONAP Jira
columnIds	issuekey,summary,assignee,status
columns	key,summary,assignee,status
maximumIssues	20
jqlQuery	"Epic Link" = CPS-1645
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

2

Jira
server ONAP Jira
serverId 425b2b0a-557c-3c0c-b515-579789cceedb
key CPS-1615

Jira
server ONAP Jira
serverId 425b2b0a-557c-3c0c-b515-579789cceedb
key CPS-1616
CPS-NCMP
Priyank Maheshwari
Ericsson Team 2

Implementation of

Q3 Target

LCM Subscriptions for CM data notifications.
Forward CM data notifications

forwarded

Notifications

by NCMP from DMI to application

Implementing Data Notifications & Subscription Notifications on a US by US basis

Note. These items is now incorporated in

Jira

server	ONAP Jira

columnIds

issuekey,summary,assignee,status

columns

key,summary,assignee,status

serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	CPS-1812

(#7 below) any remaining work items have been move to that epic instead.

Notifications

Jira

server	ONAP Jira

maximumIssues20


jqlQuery	"Epic Link" = CPS-1615
count	true
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

Subscriptions

Jira

server	ONAP Jira

columnIdsissuekey,summary,assignee,statuscolumnskey,summary,assignee,statusmaximumIssues20jqlQuery"Epic Link" = CPS-1616


jqlQuery	"Epic Link" = CPS-1616
count	true
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

3

Jira
server ONAP Jira
serverId 425b2b0a-557c-3c0c-b515-579789cceedb

3

key

TBC

CPS-1713
CPS-NCMP
Priyank Maheshwari
Community Team

Support update of cached data through a message driven solution.
Respond to VES Events from Devices in ONAP

Receive VES Event and transform it into a 'standard DMI→NCMP events (schema owned by NCMP)

Jira

server	ONAP Jira
jqlQuery	"Epic Link" = CPS-1713
count	true
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

key

4

CPS-1434 JiraserverONAP Jira

Jira
server ONAP Jira

serverId425b2b0a-557c-3c0c-b515-579789cceedbkeyCPS-1411

columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

serverId 425b2b0a-557c-3c0c-b515-579789cceedb
key CPS-

1412

1515

JiraserverONAP JiraserverId425b2b0a-557c-3c0c-b515-579789cceedbkeyCPS-1413

CPS-NCMP
Sourabh Sourabh
Ericsson Team 1
Q2 Target

Batch (~~bulk~~) Operations (Get, Query)

Allow batch operations for NCMP REST and CPS-Core Java Interfaces.

All new events will comply to cloudevents.

Jira

server	ONAP Jira
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	CPS-

1559

1717

4

Jira

server	ONAP Jira

columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution

jqlQuery	"Epic Link" = CPS-1515
count	true
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

5

Jira
server ONAP Jira

columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

serverId 425b2b0a-557c-3c0c-b515-579789cceedb
key CPS-

1515

1638
CPS-

NCMP

NMCP

Sourabh Sourabh

Halil Cakal

Ericsson

Ericsson Team 1

Batch (~~bulk~~) Operations (Get, Query)Allow batch operations for NCMP REST and CPS-Core Java Interfaces

CM Handle Connectivity Freshness/Staleness

Need to model what staleness is (current CPS only has concept of model-sync state, nothing about connectivity)
kieran mccarthy to spec this

Staleness will be modelled as a public property and notification will be sent/ notifiable.
Assumption is that the solution will accommodate the same behavior's for all public properties.

Jira

server	ONAP Jira
columnIds	issuekey

JiraserverONAP JiracolumnIdsissuekey

,summary,assignee,status
columns	key,summary,assignee,status
maximumIssues	20
jqlQuery	"Epic Link" = CPS-

1515

1638
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

5

6

Jira
server ONAP Jira

serverId425b2b0a-557c-3c0c-b515-579789cceedb

columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	CPS-

1638

1733
CPS-

NMCP

NCMP

Halil Cakal

Sourabh Sourabh
Ericsson

Team 2CM Handle Connectivity Freshness/StalenessNeed to model what staleness is (current CPS only has concept of model-sync state, nothing about connectivity)
kieran mccarthy to spec this
Staleness will be modelled as a public property and notification will be sent/ notifiable.
Assumption is that the solution will accomodate the same behaviour for all public properties.

Team 1
Mid Q4 Target

Update YANG schema-set for CM handle using ModuleSetTag

Update 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 (already built in ?)
Introduce concept of ModuleSetTag to prevent unnecessary trips to nodes to get al Modules
will require NCMP module loader (for upgrade of Inventory model) instead of Liquibase steps!

Jira

server	ONAP Jira
columnIds	issuekey,summary,assignee,status
columns	key,summary,assignee,status
maximumIssues	20
jqlQuery	"Epic Link" = CPS-

1638

1733
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

6

7

TBC

Jira

CPS-NMCP

TBC

Event DigestAdditional field to help clients filter CM AVC Events
(S)

server ONAP

JiraserverONAP

Jira
columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns key,summary,type,created,updated,due,assignee,reporter,priority,status

maximumIssues20jqlQuery"Epic Link" = CPS-1704

,resolution
serverId 425b2b0a-557c-3c0c-b515-579789cceedb

7

key

TBC

CPS-1812
CPS-

NMCP

TBC

AVC Subscription, advance filterFilter on 'Type' instead of list of CM Handle IDs → 'Type' could be defined as the yang module set containing a specific module (name and version)
(S)8

NCMP
Priyank Maheshwari
Ericsson Team 2

Merge CM data subscriptions in NCMP when forwarding it to DMI

Implementing Data Notifications & Subscription Notifications on a US by US basis

Scope add: What kind of access controls are required on topics? Spike is required for this. Work Item created (23/05).

Jira

server	ONAP Jira

serverId425b2b0a-557c-3c0c-b515-579789cceedbkeyCPS-1630

CPS-CORE (& NCMP TBC)

Lee Anjella Macabuhay

Deutsche Telekom
(TechMahindra)

Support for list as top level data node JiraserverONAP JiracolumnIdsissuekey,summary,assignee,statuscolumnskey,summary,assignee,statusmaximumIssues20

columnIds	issuekey,summary,assignee,status
columns	key,summary,assignee,status
maximumIssues	20
jqlQuery	"Epic Link" = CPS-

1630

1812
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

9

8

Jira
server ONAP Jira

serverId425b2b0a

columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	CPS-

1632

1915
CPS-

CORE (&

NCMP

TBC)

Lee Anjella Macabuhay

Deutsche Telekom
(TechMahindra)

CPS & NCMP Feature Enhancement for M Release

Waqas Ikram
Ericsson Team 2

Access Control for resources to ensure that operators can restrict access control to only those users (human/machines) that are authorized to execute CRUD operations on those resources.

Jira

server	ONAP Jira
columnIds	issuekey,summary,assignee,status
columns	key,summary,assignee,status
maximumIssues	20
jqlQuery	"Epic Link" = CPS-

1632

1915
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

10

9

Jira
server ONAP Jira

serverId425b2b0a-557c-3c0c-b515-579789cceedbkeyCPS-1704

CPS-NMCP

TBC

Refactor (legacy) NCMP ASync Response Events(S) JiraserverONAP Jira

columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution

columnIdsissuekey,summary,assignee,status

columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

maximumIssues20jqlQuery"Epic Link" = CPS-1704

serverId 425b2b0a-557c-

serverId425b2b0a-557c-

3c0c-b515-579789cceedb

11Study: Resolve technical debt (mixed data). NCMP Data upgrade. CPS Core need to support model upgrade so that NCMP can use it,
(XL) - Scope needs to be defined. Risk is scope not identified, efforts might increase. JiraserverONAP JiracolumnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolutioncolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionserverId

key

TBC

Support 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

CPS-1781
CPS-NCMP
TBD
TBD

CM data subscriptions from application to DMI [Part 2].

It includes creating subscription with wildcard cmhandles.

This epic was created to take on additional scope which got added to ~~CPS-1616~~.

Jira

serverId
server	ONAP Jira
columnIds	issuekey,summary,assignee,status
columns	key,summary,assignee,status
maximumIssues	20
jqlQuery	"Epic Link" = CPS-1781

425b2b0a-557c-3c0c-b515-579789cceedb

10

key

TBC
CPS-

1345

NMCP

12

TBC
TBC

Support multiple identifiers (alternatives for CM Handle ID)

(M) - Not sure. Scope not known yet.

13Update 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.

Event Digest

Additional field to help clients filter CM AVC Events
(S)

11

TBC
CPS-NMCP
TBC
TBC

AVC Subscription, advance filter

Filter on 'Type' instead of list of CM Handle IDs → 'Type' could be defined as the yang module set containing a specific module (name and version)

(S)

12

Jira
server ONAP Jira
serverId 425b2b0a-557c-3c0c-b515-579789cceedb
key CPS-1630
CPS-CORE (& NCMP TBC)
Lee Anjella Macabuhay
Deutsche Telekom
(TechMahindra)

Support for list as top level data node

Jira

server	ONAP Jira
jqlQuery	"Epic Link" = CPS-1630
count	true
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

13

14

TBC

Support 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.
Read from operations.15TBCSupport ncmp-datastores:running for writing data (single CM handle, synchronous only)16TBC
Support relationships for 'Instance Identifier'Should be possible to identify a cmhandle using multiple instance identifiers.
(M) - Not sure. Scope not known yet.

Jira
server ONAP Jira

columnIds

serverId 425b2b0a-557c-3c0c-b515-579789cceedb
key CPS-1632
CPS-CORE (& NCMP TBC)
Priyank Maheshwari
Deutsche Telekom
(TechMahindra)

CPS & NCMP Feature Enhancement for M Release

Jira

server	ONAP Jira
columnIds	issuekey,summary,assignee,status

issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution


columns	key,summary

,type

,

created,updated,due,

assignee

,reporter

,

priority,

status

,resolution

serverId425b2b0a-

maximumIssues	20
jqlQuery	"Epic Link" = CPS-1632
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

14

key

Jira

CPS-118017Invoke 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.

server	ONAP Jira
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	CPS-1865

TBC
TBC

Yet to agree priority

A decision was made to abandon json+problem format

Jira

server	ONAP Jira
columnIds	issuekey,summary,assignee,status
columns	key,summary,assignee,status
maximumIssues	20
jqlQuery	"Epic Link" = CPS-1865
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

15

Jira
server ONAP Jira
serverId 425b2b0a-557c-3c0c-b515-579789cceedb
key CPS-1796
CPS-CORE & NCMP
TBC
TBC

Spike for documenting Kafka interfaces using AsyncAPI

- Documentation Generation
- Interface Naming
- Cloud Events specifics asyncapi-cloud-events- Roll out for legacy events

- Code Generation (contract first, stubs)

16

Jira
server ONAP Jira
serverId 425b2b0a-557c-3c0c-b515-579789cceedb
key CPS-1704
CPS-NMCP
TBC
TBC

Refactor legacy NCMP ASync Response Events to use Cloud Events format

(M)

Jira

server	ONAP Jira
columnIds	issuekey,summary,assignee,status
columns	key,summary,assignee,status
maximumIssues	20
jqlQuery	"Epic Link" = CPS-1704

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.
(S) - for passthrough. 18Enhanced query support (fields)

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),

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

(L) .

19Enhanced query support (scope)

Currently the passthrough has an 'fields' parameter to do a scoped query.
scope=ericsson-enm-comtop:ManagedElement/ericsson-enm-gnbcucp:GNBCUCPFunction/
EndpointResource/LocalSctpEndpoint/attributes(interfaceUsed==X2))

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

(L)

20Retrieve single module resource/v1/ch/{cm-handle}/modules/definitions/{moduleName}
(S)21Access control for public interfaces (NCMP, CPS-Core, DMI?)KMC : What level of access control is there today - both on CPS and NCMP interfaces?22Fine-grained cache configuration23

Support for HTTPS and authentication

Use Service-Mesh? Both ONAP and Ericsson (applied ISTIO using Envoy Proxy side-car) are working towards this. Check with Gareth Roper

Validation required whether this is still needed. JiraserverONAP Jira


serverId	425b2b0a-557c-3c0c-b515-579789cceedb

keyCPS-70324

17

TBC

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

Support 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,

(XL) - Scope needs to be defined. Risk is scope not identified, efforts might increase.

Jira

server	ONAP Jira
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

25schema-set update for CM handle with cached data presentNeed to address case with incompatible model changes.26(ONAP) E2E Slicing Use-Case

Support dynamic inventory changes (ONAP DMI Plugin)

React to events from AAI sent over DMaaP, in turn using Inventory API for updates.
Strimzi-Kafka Bridge might be an alternative, check with Fiachra Corcoran on the latest for this when implementing this ( JiraserverONAP Jira

key

serverId	425b2b0a-557c-3c0c-b515-579789cceedb

DMAAP

CPS-

1681

1345

)

Possible in a generic way or it can also listen to similar events sent by SDN-R (as suggested by Ahila P)

Jira

server	ONAP JIRA
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	CPS-392

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	CPS-393

27Automatic (optional) Data Sync Metadata (per cmHandle) controls whether this will happen or not28Invoke YANG modelled RPC

Spin-off user stories, yet to be prioritized

JiraComponent(s)Related Work ItemDescriptionNotes

Jira

server	ONAP Jira
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	CPS-1103

CPS-NCMP

Jira

server	ONAP Jira
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	CPS-1127

CPS-NCMP

Jira

server	ONAP Jira
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	CPS-1174

CPS-NCMP

Jira

server	ONAP Jira
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	CPS-1139

CPS-NCMP

Jira

server	ONAP Jira
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	CPS-1301

CPSNow handled by Fujitsu/Wpri (Work Item ?) ?

Jira

server	ONAP Jira
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	CPS-1348

CPS

Functionalities

User Stories

Expand

title	Open User Stories for 'Montreal Release'

Jira

server	ONAP Jira
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues	20
jqlQuery	project = CPS AND type = Story AND fixVersion = "Montreal Release" AND status = Open ORDER BY fixVersion ASC, priority DESC
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

Expand

title	Improvements & Technical Debt (any release)

Jira

server	ONAP Jira
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues	20
jqlQuery	filter=12620
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

Expand

18	TBC	Support multiple identifiers (alternatives for CM Handle ID)	(M) - Not sure. Scope not known yet.
19		Access control for topics which are created by NCMP .	Spike needs to be conducted.
20		Invoke 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. (S) - for passthrough. *Spec out before Sept'23. No implementation.
21		Enhanced query support (fields)	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), KMC : Do we support restconf like queries or xpath only? (L) . *Spec out before Sept'23. No implementation.
22		Enhanced query support (scope)	Currently the passthrough has an 'fields' parameter to do a scoped query. scope=ericsson-enm-comtop:ManagedElement/ericsson-enm-gnbcucp:GNBCUCPFunction/ EndpointResource/LocalSctpEndpoint/attributes(interfaceUsed==X2)) KMC : Do we support restconf like queries or xpath only? (L) *Spec out before Sept'23. No implementation.
23	TBC	Support `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. Read from operations. (S) - Forward only. No validation or data enhancements (add prefixis)
24	TBC	Support `ncmp-datastores:running` for writing data (single CM handle, synchronous only)	(S) As per #18
25	TBC	Support relationships for 'Instance Identifier'	Should be possible to identify a cmhandle using multiple instance identifiers. (M) - Not sure. Scope not known yet.

Jira

server	ONAP Jira
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,

status,resolutionmaximumIssues20jqlQueryproject = CPS AND type = Story AND fixVersion = "Montreal Release" AND

status

in (Closed, Done) ORDER BY updated DESC

,resolution
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

Longer term roadmap

key	CPS-

Core will have extended query capabilities based on XPath expression.

CPS-Core will enforce and control ownership of data it holds

NCMP will be to able to 'detect' and sync xNF in the network

Fine-cache cache control will determine what get cache for what xNF

NCMP will support the query capabilities as CPS-Core and be extend with options similar to RESTConf's 'fields' and 'depth'

1180

26

Retrieve single module resource

/v1/ch/{cm-handle}/modules/definitions/{moduleName}

(S)

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

28 Fine-grained cache configuration

29

Support for HTTPS and authentication

Use Service-Mesh? Both ONAP and Ericsson (applied ISTIO using Envoy Proxy side-car) are working towards this. Check with Gareth Roper

Validation required whether this is still needed.

Jira

server	ONAP Jira
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	CPS-703

30 TBC Send notifications on write operation in ncmp-datastores:running for (single CM handle, synchronous only)

31 schema-set update for CM handle with cached data present Need to address case with incompatible model changes.
Scope: Upgrade of model that is cached? Lee Anjella to confirm.

32 Invoke YANG modelled RPC Specification required. Rebbot/Reset type of actions on node.

33

Jira

server	ONAP Jira
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	CPS-1843

DMI Audit for DMI restarts

Jira

server	ONAP Jira
columnIds	issuekey,summary,assignee,status
columns	key,summary,assignee,status
maximumIssues	20
jqlQuery	"Epic Link" = CPS-1843
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

34

Jira

server	ONAP Jira
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	CPS-1872

Fetch a list of cmhandles along with their private properties as response from NCMP.

Spin-off user stories, yet to be prioritized

Jira

Component(s)

Related Work Item

Description

Notes

Jira

server	ONAP Jira
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	CPS-1103

CPS-NCMP

Jira

server	ONAP Jira
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	CPS-1127

CPS-NCMP

Jira

server	ONAP Jira
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	CPS-1174

CPS-NCMP

Jira

server	ONAP Jira
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	CPS-1139

CPS-NCMP

Jira

server	ONAP Jira
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	CPS-1301

CPS

Now handled by Fujitsu/Wpri (Work Item ?) ?

Jira

server	ONAP Jira
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	CPS-1348

CPS

Functionalities

User Stories

Expand

title	Open User Stories for 'Montreal Release'

Jira

server	ONAP Jira
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues	20
jqlQuery	project = CPS AND type = Story AND fixVersion = "Montreal Release" AND status = Open ORDER BY fixVersion ASC, priority DESC
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

Expand

title	Improvements & Technical Debt (any release)

Jira

server	ONAP Jira
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution

Release Deliverables

Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note, etc) of this release.

Deliverable NameDeliverable Description

onap/cps-and-ncmp

Container running CPS and NCMPonap/cps-temporalContainer running CPS Temporalonap/ncmp-dmi-pluginContainer running OMAP DMI Plugindocs.onap.org/projects/onap-cps

CPS-NCMP Documentation for R12 (incl. offered APIs and release note)

docs.onap.org/projects/onap-cps-ncmp-dmi-pluginONAP DMI-Plugin Documentation for R12 (incl. offered APIs and release note)docs.onap.org/projects/onap-cps-cps-temporalCPS-Temporal Documentation for R12 (incl. offered APIs and release note)

Sub-Components

CPS-Core
- cps-service
- cps-rest
- cps-ri (reference implementation)
NCMP
- cps-ncmp-service
- cps-ncmp-rest
- dmi-inventory
Temporal DB (no longer active)
DMI-Plugin
- DMI Data Access
- DMI Model Access

Architecture

High level architecture diagram

CPS is a new shared service in the ONAP Architecture:

Image Removed

Platform Maturity

See the centralized wiki page: London Release Platform Maturity

API Incoming Dependencies

No Incoming API changes required

API Outgoing Dependencies

API this project is delivering to other projects.

API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)

CPS-E-01
CPS-E-02
CPS-E-03

CPS Model LifeCycle
CPS Data Write
CPS Data ReadSwagger Sources (openapi.yaml)CPS-E-04Change notificationsCPS-E-05xNF Data AccessSwagger Sources (openapi.yaml)CPS-E-06Temporal Data Access
(no other component currently depends on this or plan to use it in Istanbul)Swagger Sources (openapi.yml)

Third Party Products Dependencies

Third Party Products mean products that are mandatory to provide services for your components.

NameDescriptionCPS-Core CPS-NCMPCPS-Temporal 3PP VersionDockerVM Container18 and above18 and above18 and aboveODL Yang ToolsYang model and Data Parser8.0.68.0.6 N/A Postgres Docker imageVM container for Postgres14.1-alpine14.1-alpineN/Aonap/integration-java11Java Base image8.0.08.0.08.0.0SwaggerOpenAPI library2.1.42.1.4

springdoc-openapi-ui:1.5.9

SpringFoxOpenAPI library3.0.03.0.03.0.0Hibernate typesSupport for Postgres datatype JSONB2.10.02.10.02.10.0Spring BootApplication Framework2.6.142.6.142.6.9Commons-lang33pp3.113.113.12.0Antlr4-runtimeLanguage parser4.9.24.9.2N/ALiquibaseDB Schema (version) management4.14.0-nordix4.14.0-nordix4.14.0-nordixHazelcastDistributed Cache4.2.5N/AN/A

Testing and Integration Plans
CPS has high level of built jUnit test (>97 on all components) which is enforced by our maven build scripts
CPS has built in Persistence Layer test ie. test that integrate with real DB instance covering all use cases and are part of WoW
CIST tests are part of CPS -Repo, see https://gerrit.onap.org/r/gitweb?p=cps.git;a=tree;f=csit;h=8505b66089f62b6431c1091edf820cbdbf4363d4;hb=HEAD
And executed automatically through the cps-review-verification-maven-master CI Job
E2E Integration with ONAP components was introduced in I-release and is now included in aforementioned CIST tests

Gaps

No gaps Identified

Known Defects and Issues

See dynamic Jira filter:

JiraserverONAP Jira

jqlQuery

columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues	20

project = CPS and type = bug and status = open

filter=12620
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

Risks

Risk identified related to scope-creep, see London Risk Table

Resources

Excerpt IncludeConfiguration Persistence Service Developer's Landing Page

Expand

title	Closed Stories

Jira

server	ONAP Jira
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues	20
jqlQuery	project = CPS AND type = Story AND fixVersion = "Montreal Release" AND status in (Closed, Done) ORDER BY updated DESC
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

Other Information

Platform Maturity

See the centralized wiki page: London Release Platform Maturity

Configuration Persistence Service Developer's Landing Page

Release Milestone

The milestones are defined at the Release Planning and all the supporting project agreed to comply with these dates.

Team Internal Milestone

This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is recommended to provide these agreements and dates in this section.

Documentation, Training

See the following centralized wiki: London Documentation

Other Information

Vendor Neutral

If this project is coming from an existing proprietary codebase, ensure that all proprietary trademarks, logos, product names, etc. have been removed. All ONAP deliverables must comply with this rule and be agnostic of any proprietary symbols.

Free and Open Source Software

FOSS activities are critical to the delivery of the whole ONAP initiative. The information may not be fully available at Release Planning, however to avoid late refactoring, it is critical to accomplish this task as early as possible.
List all third party Free and Open Source Software used within the release and provide License type (BSD, MIT, Apache, GNU GPL,... ).
In the case non Apache License are found inform immediately the TSC and the Release Manager and document your reasoning on why you believe we can use a non Apache version 2 license.

Each project must edit its project table available at Project FOSS.

Charter Compliance

The project team comply with the ONAP Charter.

Space shortcuts

Page tree

Versions Compared

Old Version 37

New Version Current

Key

Montreal Release (M)

Overview

Scope

Minimum Viable Product

Requirements

ONAP Best Practices (Global Requirements) and similar

CPS-CORE / CPS-NCMP Requirements

Spin-off user stories, yet to be prioritized

Functionalities

User Stories

Spin-off user stories, yet to be prioritized

Functionalities

User Stories

Release Deliverables

Sub-Components

Architecture

High level architecture diagram

Platform Maturity

API Incoming Dependencies

API Outgoing Dependencies

Third Party Products Dependencies

Testing and Integration Plans

Gaps

Known Defects and Issues

Risks

Resources

Other Information

Platform Maturity

Release Milestone

Team Internal Milestone

Documentation, Training

Vendor Neutral

Free and Open Source Software

Charter Compliance

Space shortcuts

Page tree

Page History

Versions Compared

Old Version 37

New Version Current

Key

Montreal Release (M)

Overview

Scope

Minimum Viable Product

Requirements

ONAP Best Practices (Global Requirements) and similar

CPS-CORE / CPS-NCMP Requirements

Spin-off user stories, yet to be prioritized

Functionalities

User Stories

Spin-off user stories, yet to be prioritized

Functionalities

User Stories

Release Deliverables

Sub-Components

Architecture

High level architecture diagram

Platform Maturity

API Incoming Dependencies

API Outgoing Dependencies

Third Party Products Dependencies

Testing and Integration Plans

Gaps

Known Defects and Issues

Risks

Resources

Other Information

Platform Maturity

Release Milestone

Team Internal Milestone

Documentation, Training

Vendor Neutral

Free and Open Source Software

Charter Compliance