Versions Compared

Key

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

Table of Contents


Milestones


Image AddedImage Added

Montreal Release (M)

Image RemovedImage Removed

Image Modified

Credit:  Arild Vågen.  Licensed under Creative CommonsAttribution-Share Alike 4.0 International license.

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?

  1. TBC

Minimum Viable Product

N/A

Requirements

Priority legend
PreliminaryPlanned for current ONAP ReleaseIn ProgressPaused/BlockedCompletedDe-scoped

ONAP Best Practices (Global Requirements) and similar

ONAP RequirementNotesCPS- Jira(s)

Jira
serverONAP Jira
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyREQ-439




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

Jira
serverONAP Jira
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-1324

CPS-CORE / CPS-NCMP Requirements

PriorityEpic/Component/Owner/Team

Requirement JiraComponent(s)
/TargetDescriptionNotesJira(s)
1

TBC

Daniel Hanrahan 

  • Jira
    serverONAP Jira
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    key
Team 1
  • CPS-
NCMP
Data Write/Read Performance

NCMP (read) Requirements

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

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

  • It shall be possible get all cmhandles (anchors) (question) for a given module name at a rate of 1000 cmhandles / second (assuming 20k cmhandles are registered)
  • It shall be possible to get all cmhandles (anchors) (question) with a given public property at a rate of 500/second  (assuming 20k cmhandles are registered) Depensds on  JiraserverONAP Jira

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

    kieran mccarthy For this step we can focus on just returning just the cmhandlesIds.  Anything further can be covered by another step.

    Note. This now overlaps with work be done with Wipro/Fujitsu, see CPS Performance Testing

    • 1615

      Jira
      serverONAP Jira
    • serverId425b2b0a-557c-3c0c-b515-579789cceedb
      keyCPS-
    1171
    • 1616
    JiraserverONAP JiracolumnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    1. LCM Subscriptions for CM data notifications.
    2. Forward CM data notifications by NCMP from DMI to application

    Note. These items is now incorporated in

    Jira
    serverONAP Jira

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

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

    1326

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

    Notifications

    Jira
    serverONAP Jira

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

    jqlQuery"Epic Link" = CPS-1615
    counttrue
    serverId425b2b0a-557c-3c0c-b515-579789cceedb

    Subscriptions

    Jira
    serverONAP Jira
    jqlQuery"Epic Link" = CPS-1616
    counttrue

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

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

    keyCPS-1344
    3
    • Jira
      serverONAP Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolutioncolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionserverId425b2b0a-557c-3c0c-b515-579789cceedbkeyCPS-1443 JiraserverONAP 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

    key


    4
    CPS-1445
    • 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-
    1475
    • 1515
    JiraserverONAP Jira
    Batch (bulk) Operations (Get, Query)

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

    All new events will comply to cloudevents.

    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-

    1509

    1717
     

    Jira
    serverONAP Jira
    jqlQuery"Epic Link" = CPS-1515
    counttrue
    serverId425b2b0a-557c-3c0c-b515-579789cceedb

    keyCPS-1516
    5
    • Jira
      serverONAP Jira
      serverId425b2b0a-557c-3c0c-b515-579789cceedb
      keyCPS-
    1494
    • 1638
    Jira
    serverONAP Jira
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyCPS-1519
    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.

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

    Jira
    serverONAP Jira

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

    columnIdsissuekey,summary,assignee,status
    columnskey,summary,assignee,status
    maximumIssues20
    jqlQuery"Epic Link" = CPS-1638

    JiraserverONAP Jira

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

    key
    6
    CPS-1615
    • Jira
      serverONAP Jira
    serverId425b2b0a-557c-3c0c-b515-579789cceedbkeyCPS-1616

    Priyank Maheshwari

    Team 2

    CPS-NCMPImplementation of CM data notifications forwarded by NCMP from DMI to applicationImplementing Data Notifications & Subscription Notifications on a US by US basis

    Notifications

    Jira
    serverONAP Jira
    jqlQuery"Epic Link" = CPS-1615
    counttrue
    serverId425b2b0a-557c-3c0c-b515-579789cceedb

    Subscriptions

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

    1616

    1733

    counttrue

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

    3 Jira
    7

    TBC

    Priyank Maheshwari
    External Team ???

    CPS-NCMPSupport update of cached data through a message driven solution.
    Respond to  VES Events from Devices in ONAPReceive VES Event and transform it into a 'standard DMI→NCMP events (schema owned by NCMP)
    • Jira
    JiraserverONAP Jira
    • serverONAP Jira
    serverId425b2b0a-557c-3c0c-b515-579789cceedbkeyCPS-1434
    • 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-
    1411
    • 1812
    JiraserverONAP JiraserverId425b2b0a-557c-3c0c-b515-579789cceedbkeyCPS-1412
    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

    serverId425b2b0a-557c

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

    key
    8
    CPS-1413
    • 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-
    1559
    • 1915
    4

    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
    serverONAP Jira
    columnIdsissuekey,summary,assignee,status

    JiraserverONAP JiracolumnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution

    columnskey,summary

    ,type

    ,

    created,updated,due,

    assignee

    ,reporter

    ,

    priority,

    status

    ,resolution

    maximumIssues

    serverId425b2b0a

    20
    jqlQuery"Epic Link" = CPS-1915
    serverId425b2b0a-557c-3c0c-b515-579789cceedb

    keyCPS-1515

    Sourabh Sourabh 

    Team 1

    CPS-NCMPBulk Operations (Get, Query)Allow bulk operations for NCMP (and/or) CPS REST Interfaces
    9
    • Jira
      serverONAP Jira
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,
    assignee,statusmaximumIssues20jqlQuery"Epic Link" = CPS-1515
    • type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId425b2b0a-557c-3c0c-b515-579789cceedb
    5
    • keyCPS-
    NCMPCM 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

    Jira
    serverONAP Jira
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyCPS-1415

    • 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
    serverONAP Jira
    columnIdsissuekey,summary,assignee,status
    columnskey,summary,assignee,status
    maximumIssues20

    6CPS-NCMPEvent DigestAdditional field to help clients filter CM AVC Events JiraserverONAP Jira

    jqlQuery"Epic Link" = CPS-

    1515 counttrue

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

    10
    7
    • TBC
    • CPS-
    NCMPAVC Subscription, advance filterFilter on 'Type' instead of 8

    TBC

    Lee Anjella Macabuhay
    Deutsche Telekom
    • NMCP
    • TBC
    • TBC
    Event DigestAdditional field to help clients filter CM AVC Events
    (S)


    11
    • TBC
    • CPS-NMCP
    • TBC
    • 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)


    (
    TechMahindra
    S)
    CPS-Core /
    CPS-NCMPSupport for list as top level data node

    12
    • Jira
      serverONAP Jira
      serverId425b2b0a-557c-3c0c-b515-579789cceedb
      keyCPS-
    491
    Support for list as top level data node

    Jira
    serverONAP Jira
    jqlQuery"Epic Link" = CPS-1630
    counttrue
    serverId425b2b0a-557c-3c0c-b515-579789cceedb

    13
    • Jira
      serverONAP Jira
    JiraserverONAP JiracolumnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolutioncolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    • serverId425b2b0a-557c-3c0c-b515-579789cceedb
      keyCPS-
    765
    CPS & NCMP Feature Enhancement for M Release


    Jira
    serverONAP Jira
    columnIdsissuekey,summary,

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

    assignee,status
    columnskey,summary,assignee,status
    maximumIssues20
    jqlQuery"Epic Link" = CPS-1632

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

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

    key
    14
    CPS-766
    • 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-
    767
    • 1865
    • TBC
    • TBC
    Yet to agree priorityA decision was made to abandon json+problem format

    Jira
    serverONAP Jira
    columnIdsissuekey,summary,

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

    assignee,status
    columnskey,summary

    ,type

    ,

    created,updated,due,

    assignee,

    reporter,priority,status,resolution

    status
    maximumIssues20
    jqlQuery"Epic Link" = CPS-1865
    serverId425b2b0a-557c-3c0c-b515-579789cceedb

    key
    15
    CPS-1586
    • Jira
    9
    • server

    TBC

    Lee Anjella Macabuhay

    Deutsche Telekom
    (TechMahindra)

    CPS-Core /
    CPS-NCMPSupport for multiple top-elements from different modules in one CM handle/anchor
    • ONAP Jira
      serverId425b2b0a-557c-
    JiraserverONAP JiraserverId425b2b0a-557c-
    • 3c0c-b515-579789cceedb
      keyCPS-
    1051
    • 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
      serverONAP Jira
      serverId425b2b0a-557c-3c0c-b515-579789cceedb
    JiraserverONAP JiraserverId425b2b0a-557c-3c0c-b515-579789cceedb
    • keyCPS-
    341
    • 1704
    10
    • CPS-NMCP
    • TBC
    NCMP-CPSSupport NCMP-CPS upgradeCurrently
    • TBC
    Refactor legacy NCMP ASync Response Events to use Cloud Events format(M)

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

    17

    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,

    Jira


    (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

    11
    18

    TBC

    CPS-Core
    NCMP-CPS
    Support multiple identifiers (alternatives for CM Handle ID)
    12

    TBC

    Support for 'Instance Identifier'Should be possible to identify a cmhandle using multiple instance identifiers

    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

    13CPS-NCMPInvoke YANG modelled action

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

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

    (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

    14CPS-NCMPEnhanced query supportCurrently 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=

      
                  scope=ericsson-enm-comtop:ManagedElement/ericsson-enm-gnbcucp:GNBCUCPFunction/
                 

    gnbcucp:GNBCUCPFunction/EndpointResource/LocalSctpEndpoint/attributes(sctpEndpointRef),
                  scope=ericsson-enm-comtop:ManagedElement/ericsson-enm-gnbcucp:GNBCUCPFunction/
                   EndpointResource/LocalSctpEndpoint18CPS-Core /
    CPS-NCMPAccess control for public interfaces (NCMP, CPS-Core, DMI?)KMC : What level of access control is there today - both on CPS and NCMP interfaces?19CPS-NCMPFine-grained cache configuration20CPS-NCMPSend notification for updated CM handle metadata (public CM handle properties or YANG modules)21CPS-Core /
    CPS-NCMP

     EndpointResource/LocalSctpEndpoint/attributes(interfaceUsed==X2))

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

    15CPS_Core / CPS-NCMPUpdate YANG schema-set for CM handle without removing and adding it

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

    Needed for node upgrade scenario.

    16CPS-NCMPRetrieve single module resource/v1/ch/{cm-handle}/modules/definitions/{moduleName}17CPS-Core / CPS-NCMPExisting CPS-path based queries across all CM handles for cached data

    Look to define the interface specification for this only.

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

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

    24TBCSupport 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
    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

    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 
    Jiraserver
    Validation required whether this is still needed. 

    Jira
    serverONAP Jira
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyCPS-703

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

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

    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. 


    32
    Invoke YANG modelled RPCSpecification required. Rebbot/Reset type of actions on node. 
    33

    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

    Jira
    serverONAP Jira
    columnIdsissuekey,summary,assignee,status
    columnskey,summary,assignee,status
    maximumIssues20
    jqlQuery"Epic Link" = CPS-1843

    23TBCCPS-Core /
    CPS-NCMPSupport ncmp-datastores:running for writing data (single CM handle, synchronous only)24TBCCPS-CoreSend notifications on write operation in ncmp-datastores:running for (single CM handle, synchronous only)25CPS-Core /
    CPS-NCMPschema-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 JiraserverONAP JIRA

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

    keyDMAAP-1681)

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

    34

    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-

    392
    Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyCPS-393
    27CPS-NCMPAutomatic (optional) Data Sync Metadata (per cmHandle) controls whether this will happen or not28CPS-NCMPInvoke YANG modelled RPC

    1872

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


    Spin-Spin-off user stories, yet to be prioritized

     JiraComponent(s)Related Work ItemDescriptionNotes

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

    CPS-NCMP


    Jira
    serverONAP Jira
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyCPS-1127

    CPS-NCMP


    Jira
    serverONAP Jira
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyCPS-1174

    CPS-NCMP


    Jira
    serverONAP Jira
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyCPS-11831139

    CPS-NCMPInvestigation on the use of Liquibase to install NCMP artifacts

    Jira
    serverONAP Jira
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyCPS-1139




    Jira
    server

    CPS-NCMP

    Jira
    serverONAP Jira
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyCPS-1301

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

    Jira
    serverONAP Jira
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyCPS-1348

    CPS


    Functionalities

    User Stories

    Expand
    titleOpen User Stories REQ-1410 (CPS Enhancements)for 'Montreal Release'

    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
    maximumIssues20
    jqlQuery"Epic Link" in (CPS-1410) AND status = Open ORDER BY fixVersion ASC, priority DESC
    serverId425b2b0a-557c-3c0c-b515-579789cceedb

    Expand
    titleImprovements & Technical Debt (any release)

    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
    maximumIssues20
    jqlQueryfilter=12620
    serverId425b2b0a-557c-3c0c-b515-579789cceedb

    Expand
    titleClosed Stories

    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
    maximumIssues20
    jqlQueryproject = CPS AND type = Story AND fixVersion = "London Release" AND status in (Closed, Done) ORDER BY updated DESC
    serverId425b2b0a-557c-3c0c-b515-579789cceedb

    Longer term roadmap

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

    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)

    20
    jqlQueryproject = CPS AND type = Story AND fixVersion = "Montreal Release" AND status = Open ORDER BY fixVersion ASC, priority DESC
    serverId425b2b0a-557c-3c0c-b515-579789cceedb


    Expand
    titleImprovements & Technical Debt (any release)

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

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

    No gaps Identified

    • Known Defects and Issues

    See dynamic Jira filter:

    JiraserverONAP Jira

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

    project = CPS and type = bug and status = open

    filter=12620
    serverId425b2b0a-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
    titleClosed Stories

    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
    maximumIssues20
    jqlQueryproject = CPS AND type = Story AND fixVersion = "Montreal Release" AND status in (Closed, Done) ORDER BY updated DESC
    serverId425b2b0a-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.