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.
TBAC - 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.
TBAC Study still ongoing, schedule an internal meeting to go through study doc, until sidecar is well define and implemented cps can't do nothing. Sidecar should specify the interfaces
CM data subscriptions from application to DMI [Part 2].
For all cmhandle (general)
This epic was created to take on additional scope which got added toCPS-1616.
Jira
server
ONAP Jira
columnIds
issuekey,summary,assignee,status
columns
key,summary,assignee,status
maximumIssues
20
jqlQuery
"Epic Link" = CPS-1781
serverId
425b2b0a-557c-3c0c-b515-579789cceedb
910
write epic
CPS-NMCP
TBC
TBC
Support multiple identifiers (alternatives for CM Handle ID)
Implement FDN base CMhandle, this should be done before patternmatch cmhandle can be implemeted
We should raise a spike.
1011
write epic
CPS-NMCP
TBC
TBC
AVC Subscription, advance filter. Part 2 of cmhandles
It includes creating subscription with patternmatch cmhandles.
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)
Kolawole to chase on IDUN
1112
TBC
CPS-NMCP
TBC
TBC
Event Digest
Additional field to help clients filter CM AVC Events (S)
1213
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
Study: Resolve technical debt (mixed data). NCMP Data upgrade. CPS Core need to support model upgrade so that NCMP can use it,
Liquibase is used in CPS to manage data(upgrades) - Now available.
Still need to discuss the 'backward incompatible' → What interfaces should NOT be impacted Kieran mention NBI - northbound interfaces
Propose workshop, Spike needed from CPS
(XL) - Scope needs to be defined. Risk is scope not identified, efforts might increase.
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) Add label of techdebt Kolawole Adebisi-Adeolokun not an immediate req for
1516
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) TBC
Jira
server
ONAP Jira
columnIds
issuekey,summary,assignee,status
columns
key,summary,assignee,status
maximumIssues
20
jqlQuery
"Epic Link" = CPS-1704
serverId
425b2b0a-557c-3c0c-b515-579789cceedb
1617
Access control for topics which are created by NCMP.
Spike needs to be conducted. Dependent of TBAC implementations.
1718
Continue from here on next
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.
1819
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.
1920
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.
2021
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)
2122
TBC
Support ncmp-datastores:running for writing data (single CM handle, synchronous only)
(S) As per #18
2223
TBC
Support relationships for 'Instance Identifier'
Should be possible to identify a cmhandle using multiple instance identifiers. (M) - Not sure. Scope not known yet.
