Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

KMC : What level of access control is there today - both on CPS and NCMP interfaces?
PriorityEpic/Component/Owner/Team/TargetDescriptionNotesJira(s)
1
  • Jira
    serverONAP Jira
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyCPS-1645
  • CPS-Core
  • Daniel Hanrahan 
  • Community & Ericsson Team 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
serverONAP Jira
columnIdsissuekey,summary,assignee,status
columnskey,summary,assignee,status
maximumIssues20
jqlQuery"Epic Link" = CPS-1645
serverId425b2b0a-557c-3c0c-b515-579789cceedb

2
  • Jira
    serverONAP Jira
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyCPS-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
serverONAP Jira
jqlQuery"Epic Link" = CPS-1713
counttrue
serverId425b2b0a-557c-3c0c-b515-579789cceedb


3
  • Jira
    serverONAP Jira
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyCPS-1638
  • CPS-NMCP
  • Halil Cakal 
  • Ericsson Team 1
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
serverONAP Jira
columnIdsissuekey,summary,assignee,status
columnskey,summary,assignee,status
maximumIssues20
jqlQuery"Epic Link" = CPS-1638
serverId425b2b0a-557c-3c0c-b515-579789cceedb

4
  • Jira
    serverONAP Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyCPS-1733
  • CPS-NCMP
  • Sourabh Sourabh 
  • Ericsson Team  1
  • Mid Q4 Target
Update YANG schema-set for CM handle using ModuleSetTag
  1. Update YANG schema-set for CM handle without removing and adding it
  2. Cached data is not in scope.
  3. Need to specify orphan handling of YANG modules (already built in ?)
  4. Introduce concept of ModuleSetTag to prevent unnecessary trips to nodes to get al Modules
  5. will require NCMP module loader (for upgrade of Inventory model) instead of Liquibase steps!

Jira
serverONAP Jira
columnIdsissuekey,summary,assignee,status
columnskey,summary,assignee,status
maximumIssues20
jqlQuery"Epic Link" = CPS-1733
serverId425b2b0a-557c-3c0c-b515-579789cceedb

5
  • Jira
    serverONAP Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyCPS-1812
  • CPS-NCMP
  • Priyank Maheshwari  
  • Ericsson Team  2
Merge CM data subscriptions in NCMP when forwarding it to DMIImplementing 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
serverONAP Jira
columnIdsissuekey,summary,assignee,status
columnskey,summary,assignee,status
maximumIssues20
jqlQuery"Epic Link" = CPS-1812
serverId425b2b0a-557c-3c0c-b515-579789cceedb

6
  • 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.

Request documentation


7
  • write epic
  • CPS-NMCP
  • TBC
  • TBC
Support for Async datajobs

DCM impact. Must now include: 

Create, Update, Delete and Actionsupport. I.e for passthrough only

Request documentation


87
  • Jira
    serverONAP Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyCPS-1915
  • CPS-NCMP
  • Waqas Ikram 
  • Ericsson  Team 2
  • TBD
  • TBD

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


Open Spike

Jira
serverONAP Jira
columnIdsissuekey,summary,assignee,status
columnskey,summary,assignee,status
maximumIssues20
jqlQuery"Epic Link" = CPS-1915
serverId425b2b0a-557c-3c0c-b515-579789cceedb

89
CPS/NCPM delivery process

DCM impact


910
  • Jira
    serverONAP Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyCPS-1781
  • CPS-NCMP
  • TBD
  • TBD

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 to CPS-1616


Jira
serverONAP Jira
columnIdsissuekey,summary,assignee,status
columnskey,summary,assignee,status
maximumIssues20
jqlQuery"Epic Link" = CPS-1781
serverId425b2b0a-557c-3c0c-b515-579789cceedb

10
  • write epic
  • CPS-NMCP
  • TBC
  • TBC

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

Support multiple identifiers (alternatives for CM Handle ID)

Implement FDN base CMhandle, this should be done before patternmatch cmhandle can be implemetedWe should raise a spike.

11
  • 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


12
  • TBC
  • CPS-NMCP
  • TBC
  • TBC
Event Digest

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



13

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.


Jira
serverONAP Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-1345

14
  • Jira
    serverONAP Jira
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyCPS-1632
  • CPS-CORE (& NCMP TBC)
  • Priyank Maheshwari 
  • Deutsche Telekom
    (TechMahindra)
CPS & NCMP Feature Enhancement for M Release


Jira
serverONAP Jira
columnIdsissuekey,summary,assignee,status
columnskey,summary,assignee,status
maximumIssues20
jqlQuery"Epic Link" = CPS-1632
serverId425b2b0a-557c-3c0c-b515-579789cceedb

15
  • Jira
    serverONAP Jira
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyCPS-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)
Add label of techdebt Kolawole Adebisi-Adeolokun not an immediate req for


16
  • Jira
    serverONAP Jira
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyCPS-1704
  • CPS-NMCP
  • TBC
  • TBC
Refactor legacy NCMP ASync Response Events to use Cloud Events format(M) TBC 

Jira
serverONAP Jira
columnIdsissuekey,summary,assignee,status
columnskey,summary,assignee,status
maximumIssues20
jqlQuery"Epic Link" = CPS-1704
serverId425b2b0a-557c-3c0c-b515-579789cceedb

17
Access control for topics which are created by NCMP.

Spike needs to be conducted. Dependent of TBAC implementations.


18Continue from here on nextInvoke YANG modelled sync actionInvoke 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

sync 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.

 
*Spec out before Sept'23. No implementation

 


 

can datajob cover this ?, currently no support for 'actions'. Action name at the end of resourceid. split ticket into, action with and without responses


19
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. 



20
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. 


21

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)

22TBCSupport ncmp-datastores:running for writing data (single CM handle, synchronous only)(S)  As per #18
23

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
serverONAP Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-1180

24


Retrieve single module resource/v1/ch/{cm-handle}/modules/definitions/{moduleName}
(S)moduleName}

(S)

2525Access control for public interfaces (NCMP, CPS-Core, DMI?)26
Fine-grained cache configuration

2726

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
serverONAP Jira
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-703

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

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


3029
Invoke YANG modelled RPCSpecification required. Rebbot/Reset type of actions on node. 
3130

Jira
serverONAP Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-1843

DMI Audit for DMI restarts

After restart, trustlevel loses all data. TrustLevel is not currently in use now, however this becomes an issues after TrustLevel restart. The states goes to 'NONE' after TrustLevel restart


TBC

Jira
serverONAP Jira
columnIdsissuekey,summary,assignee,status
columnskey,summary,assignee,status
maximumIssues20
jqlQuery"Epic Link" = CPS-1843
serverId425b2b0a-557c-3c0c-b515-579789cceedb

3231

Jira
serverONAP Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-1872

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


...