Versions Compared

Key

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


Table of Contents

Image Removed

Image Removed

...

New Delhi (ND)

...

...

Image Removed

India Gate in New Delhi, March 20, 2016 (Credit: A. Savin, WikiCommons)

Requirements

...

ONAP Best Practices (Global Requirements) and similar

...

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-439

...


Table of Contents





Image Added

Image Added

New Delhi (N)

Image Added

India Gate in New Delhi, March 20, 2016 (Credit: A. Savin, WikiCommons)


Requirements

Priority legend
PreliminaryPriority AgreedIn ProgressPaused/BlockedCompletedDe-scoped

ONAP Best Practices (Global Requirements) and similar

CPS-
ONAP RequirementNotesCPS- Jira(s)

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
key

REQ-439




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

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCPS-1324

CPS-CORE / CPS-NCMP Requirements

17

PriorityEpic/Component/Owner/Team/TargetDescriptionNotesJira(s)
1
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    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 Legacy
serverSystem Jira
columnIdsissuekey,summary,assignee,status
columnskey,summary,assignee,status
maximumIssues20
jqlQuery"Epic Link" = CPS-1645
counttrue
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

2
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    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 Legacy
serverSystem Jira
columnIdsissuekey,summary,assignee,status
columnskey,summary,assignee,status
maximumIssues10
jqlQuery"Epic Link" = CPS-1713
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176


3
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-1638
  • CPS-NMCP
  • Halil Cakal 
  • Ericsson Team 1
  • Early Q1 24' Target
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.

Done:

Jira Legacy
serverSystem Jira
jqlQuery"Epic Link" = CPS-1638
counttrue
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

4
  • Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-1733
  • CPS-NCMP
  • Sourabh Sourabh 
    Toine Siebelink  Missed Impacts
  • Ericsson Team  1
  • End Q1 24'
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 Legacy
serverSystem Jira
columnIdsissuekey,summary,assignee,status
columnskey,summary,assignee,status
maximumIssues20
jqlQuery"Epic Link" = CPS-1733
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

5
  • Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-1812
  • CPS-NCMP
  • Priyank Maheshwari  
  • Ericsson Team  2
  • Mid Q1 Q 24' Target
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).


Delivery of this epic is dependent on -

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCPS-2166

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,assignee,status
columnskey,summary,assignee,status
maximumIssues20
jqlQuery"Epic Link" = CPS-1812
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

6
  • Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-1963
  • CPS-NCMP
  • Levente Csanyi 
  • Ericsson Team 1
  • IDUN-100301
  • Q2 24'

Support Alternate ID (3GPP) for CM Handle ID
Implement FDN base CMhandle, this should be done before patternmatch cmhandle can be implemented

NCMP's CmHandle registration endpoint shall be changed to accept a new String parameter which proposed name is alternateId.
NCMP Inventory CPS-NCMP-I-01 should be able to support alternate id update

Done:

Jira Legacy
serverSystem Jira
jqlQuery"Epic Link" = CPS-1963
counttrue
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

7
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-1632
  • CPS-CORE (& NCMP TBC)
  • Priyank Maheshwari 
  • Deutsche Telekom
    (TechMahindra)
CPS & NCMP Feature Enhancement for M Release: Delta Feature

Moved up on  Previously Priority 19

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,assignee,status
columnskey,summary,assignee,status
maximumIssues20
jqlQuery"Epic Link" = CPS-1632
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

8
  • Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-2007
  • CPS-NCMP
  • Jeff van Dam 
  • Ericsson Team 1
  • TBC
  • Q2 Q1 24'

Update NCMP LCM events to include  alternate id

* NCMP LCM event should send notification events with FDN identifier in the alternateid (deprecation period: correlationid=md5-hash, alternateId=FDN)
* NCMP LCM event should send notification events with FDN identifier in the correlationid (after deprecation period: correlationid=md5-hash (existing) or uri-FDN (new ones), alternateId=FDN)

Done:

Jira Legacy
serverSystem Jira
jqlQuery"Epic Link" = CPS-2007
counttrue
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

9
  • Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-2125
  • CPS-NCMP
  • Daniel Hanrahan 
  • Ericsson Team 1 & 2
  • Immediately

Audit Logging. NCMP to support audit logging

  • NCMP to use Header and log Request
  • Propagate the Authorization Header as received
  • Disable Basic Authentication


*NEWLY ADDED → Customer installation was impacted

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,assignee,status
columnskey,summary,assignee,status
maximumIssues20
jqlQuery"Epic Link" = CPS-2125
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

10
  • Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-1964
  • CPS-NCMP
  • Gerard Nugent  
  • Ericsson Team 1 & 2
  • IDUN-100303
  • Q2 Q3 24'

Support for Async datajobs

Not just for reading specific fdn, but rather QUERY Group of FDN , it's just a broadcast to every DMI plugin. The response should mimic sending a broadcast to 2 or more CM Handles 

CPS Team wil only do java interface. REST Interface is done in DCM

NEW interface aligning with 3GPP i.e FDN instead of CM-HandleIds

(Read use case can re-use existing dataOperationz impl. after mapping FDNs to CMHandleIds for input and back for output!)

Read, Create, Update, Delete and Action support. I.e for passthrough only
Note: Q(uery) is  SUBNETWORK-wide read and should be done separately using a different endpoint for clarity and separation!

* NCMP to introduce a qualifier to be used along with the DMI plugin so NCMP can break the request with multiple cmhandle into batches based on the DMI plugin and the Qualifier (where qualifier should be EMS name / id).
* NCMP shall create one or multiple EMS job ids depending on FDNs requested
* NCMP shall provide an interface to get status of an EMS job id (forward request)
* NCMP shall provide an interface to get results of an EMS job id
* NCMP shall send the results to Kafka topic

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,assignee,status
columnskey,summary,assignee,status
maximumIssues20
jqlQuery"Epic Link" = CPS-1964
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

11
  • Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-1966
  • CPS-NCMP
  • Daniel Hanrahan 
  • Ericsson Team 2
  • Q3 24'
CPS/NCMP delivery process

Moved up on Not discussed for long time but need new attention so these problems don't continue while building DCM
Alignment
of CPS/NCMP build artifact versions with EIC 

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCPS-1933

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,assignee,status
columnskey,summary,assignee,status
maximumIssues20
jqlQuery"Epic Link" = CPS-1966
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

12
  • Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-1135
  • CPS-NCMP
  • Halil Cakal 
  • Ericsson Team 1
  • Q1 24'
Retrieve single module resource
No Epic, Single User Story
/v1/ch/{cm-handle}/modules/definitions/{moduleName}

Done:

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCPS-1135

13

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCPS-2166

Forwarding CM Data Notifications based on Subscription


  • Topic used for forwarding notification should be based on the client-id which can be extracted from the subscription-id - Yet to be clarified  
  • Client application shall ONLY receive notification they subscribed on
  • Client application shall not see notification they did not subscribed on

Interdependent on -

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCPS-1812

--newly added--

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,assignee,status
columnskey,summary,assignee,status
maximumIssues20
jqlQuery"Epic Link" = CPS-2166
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

14

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCPS-2170

Adding limit to legacy batch (bulk) interface

proposed hardcoded limit of 50 cm handles

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCPS-2170

15

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCPS-2172

Enable Open Telemetry tracing

Configuration impacts only. Ericsson has delivered the required configuration files

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCPS-2172

16

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCPS-

2008

989

  • CPS-NCMP
TBC

Update existing single sync cmhandle APIs to support alternative id (containing FDNs)

Replace RestTemplate with WebClient


Merging

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCPS-

1992

989

CPS-NMCP

with

TBC

Jira Legacy

  • TBC
  • IDUN-46098
  • Q2 24'
  • NCMP to support the 3GPP ProvMnS CRUD interfaces. NCMP to Support new 3GPP sync single FDN request

    Implement new NCMP CRUDAQ sync interface aligned with 3GPP API (Read and write use cases) - Wrapper on existing/legacy API

    18
    Jira Legacy
    serverSystem Jira
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-

    2009
  • CPS-NCMP
  • CPS-NMCP
  • TBC
  • Q4 24'
  • Update remaining existing/legacy NCMP APIs to support alternateId (FDN)

    Update existing/legacy NCMP APIs to support FDN / alternateId

    Depends on Jira LegacyserverSystem Jira

    2148

    Prometheus metrics http_client_requests_* metrics are not available for every endpoints in CPS NCMP


    Add state tags to cps.ncmp.lcm.events.publish metrics


    Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,assignee,status
    columnskey,summary,assignee,status
    maximumIssues20
    jqlQuery"Epic Link" = CPS-2166
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

    key
    17CPS-1704 (which now has a lower priority)Now includes  Jira Legacyserver
    • Jira Legacy
      serverSystem Jira
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyCPS-2009
    • CPS-NCMP
    • CPS-
    205819
    • NMCP
    • TBC
    • Q3 24'
    Update remaining existing/legacy NCMP APIs to support alternateId (FDN)

    Update existing/legacy NCMP APIs to support FDN / alternateId

    Depends on

    Jira Legacy
    serverSystem Jira

    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee

    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-1704
    (which now has a lower priority)

    Now includes 

    Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-

    2010
  • CPS-NCMP
  • CPS-NMCP
  • TBC
  • Q4 24'
  • NCMP to support

    2058


    Agreed with stakeholders on   These open issues are not a blocker, we would leave LCM event as Legacy event and proceed with  

    Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-2009

    Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,assignee,status
    columnskey,summary,assignee,status
    maximumIssues20
    jqlQuery"Epic Link" = CPS-2009
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

    18
    • Jira Legacy
      serverSystem Jira
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyCPS-2189
    • CPS-NCMP
    • TBC
    • Q 24'



    19
    • Jira Legacy
      serverSystem Jira
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyCPS-2008
    • CPS-NCMP
    • TBC
    • Q2 24'

    Update existing single sync cmhandle APIs to support alternative id (containing FDNs)



    20
    • Jira Legacy
      serverSystem Jira
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyCPS-1992
    • CPS-NMCP
    • TBC
    • TBC
    • IDUN-46098
    • Q2 24'

    NCMP to support the 3GPP ProvMnS CRUD interfaces. NCMP to Support new 3GPP sync single FDN request

    Implement new NCMP CRUDAQ sync interface aligned with 3GPP API (Read and write use cases) - Wrapper on existing/legacy API


    21
    • Jira Legacy
      serverSystem Jira
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyCPS-2010
    • CPS-NCMP
    • CPS-NMCP
    • TBC
    • Q4 24'
    NCMP to support datajob results in S3

    NCMP to introduce a qualifier to be used along with the DMI plugin so NCMP can break the request with multiple cmhandle into batches based on the DMI plugin and the Qualifier (where qualifier should be EMS name / id).
    * NCMP shall create one or multiple EMS job ids depending on FDNs requested
    * NCMP shall provide an interface to get status of an EMS job id (forward request)
    * NCMP shall provide an interface to get results of an EMS job id
    * NCMP shall send the results to S3


    2022
    • Jira Legacy
      serverSystem Jira
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyCPS-1915
    • CPS-NCMP
    • Waqas Ikram (Unlicensed) 
    • 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.

    Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,assignee,status
    columnskey,summary,assignee,status
    maximumIssues20
    jqlQuery"Epic Link" = CPS-1915
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

    2123
    • Jira Legacy
      serverSystem Jira
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      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 LegacyserverSystem JiracolumnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolutioncolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

    Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,assignee,status
    columnskey,summary,assignee,status
    maximumIssues20
    jqlQuery"Epic Link" = CPS-1781
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

    22

    Epic Link" = CPS-1781
    serverId4733707d-2057-3a0f

    -ae5e-4fd8aff50176keyCPS-1965
  • 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)

    23
    • TBC
    • CPS-NMCP
    • TBC
    • TBC
    Event Digest

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

    24

    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 Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-1345

    25
    • Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      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

    26
    • Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyCPS-1704
    • CPS-NMCP
    • TBC
    • TBC
    Refactor legacy NCMP ASync Response Events to use Cloud Events format(M) TBC 

    -ae5e-4fd8aff50176

    24
    • Jira Legacy
      serverSystem Jira
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyCPS-1965
    • 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)


    25
    • TBC
    • CPS-NMCP
    • TBC
    • TBC
    Event Digest

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



    26

    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 Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,assignee,status
    maximumIssues20
    jqlQuery"Epic Link" = CPS-1704 due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-1345

    27

     

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

    29Enhanced 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. 
    30Enhanced 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. 31

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

    Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-1180

    34Fine-grained cache configuration35

    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 Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-703

    36TBCSend notifications on write operation in ncmp-datastores:running for (single CM handle, synchronous only)37schema-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. 
    38Invoke YANG modelled RPCSpecification required. Rebbot/Reset type of actions on node. 39
    Jira LegacyserverSystem JiracolumnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolutioncolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    • Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    27Access control for topics which are created by NCMP.

    Spike needs to be conducted. Dependent of TBAC implementations.

    28Invoke YANG modelled sync action

    Invoke YANG modelled action

    Invoke YANG modelled RPC, Specification required. Rebbot/Reset type of actions on node. Include to the sync one

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


    28
    • Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyCPS-1704
    • CPS-NMCP
    • TBC
    • TBC
    Refactor legacy NCMP ASync Response Events to use Cloud Events format(M) TBC 

    Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,assignee,status
    columnskey,summary,assignee,status
    maximumIssues20
    jqlQuery"Epic Link" = CPS-1704
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

    29
    Access control for topics which are created by NCMP.

    Spike needs to be conducted. Dependent of TBAC implementations.


    30Invoke YANG modelled sync action

    Invoke YANG modelled action

    Invoke YANG modelled RPC, Specification required. Rebbot/Reset type of actions on node. Include to the sync one

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


     

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


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



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


    33

    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)
    34TBCSupport ncmp-datastores:running for writing data (single CM handle, synchronous only)(S)  As per #18
    35

    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 Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-1180

    36
    Fine-grained cache configuration

    37

    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 Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    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 Legacy
    serverSystem Jira
    columnIdsissuekey,summary,assignee,status
    columnskey,summary,assignee,status
    maximumIssues20
    jqlQuery"Epic Link" = CPS-1843
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

    40

    703

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

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


    40
    Invoke YANG modelled RPCSpecification required. Rebbot/Reset type of actions on node. 
    41

    Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-1872

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

    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 Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution,status
    maximumIssues20
    jqlQuery"Epic Link" = CPS-1843
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-2148

    Prometheus metrics http_client_requests_* metrics are not available for every endpoints in CPS NCMP

    Add state tags to cps.ncmp.lcm.events.publish metrics

    *NCMP to cost and reprioritise

    42

    Jira Legacy
    issuekey,summary,assignee,status
    serverSystem Jira
    columnIdscolumnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status
    maximumIssues20
    jqlQuery"Epic Link" = CPS-2148
    ,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

    42

    keyCPS-1872

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


    43

    Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-2169

    CM-handle search that returns 200k Nodes Cells 



    Spin-off user stories, yet to be prioritized

    ...

    Other Information

    Platform Maturity

    See the centralized wiki page: London Release Platform Maturity Tony Hansen 's Best Practices Badging Status Dashboard

    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.

    ...