Versions Compared

Old Version 92

changes.mady.by.user Kolawole Adebisi-Adeolokun

Saved on

compared with

New Version 93

changes.mady.by.user Kolawole Adebisi-Adeolokun

Saved on

Key

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

Table of Contents



Montreal Release (M)

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



Requirements

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

ONAP Best Practices (Global Requirements) and similar

ONAP RequirementNotesCPS- Jira(s)

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

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

- Code Generation (contract first, stubs)

15
  • CPS-NMCP
  • TBC
  • TBC

    • Currently only custom upgrade is supported. (upon request)

    Requirement: It shall be possible to upgrade NCMP-CPS from release N-1 to N (without requiring manual intervention/workarounds). N is defined as any release requested by ESH

    • Note. Need to agree version strategy: use current ONAP x.y.z. numbering. Ericsson to communicate when a version is to be 'delivered' and 'y' increased

    Technical Debt to be addressed: Liquibase is used in CPS to manage data(upgrades) in CPS

    Study: Resolve technical debt (mixed data). NCMP Data upgrade. CPS Core need to support model upgrade so that NCMP can use it,
    (XL) - Scope needs to be defined. Risk is scope not identified, efforts might increase.

    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. 

    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. 
    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)TBC
    Should be possible to identify a cmhandle using multiple instance identifiers.
    (M) - Not sure. Scope not known yet. 
    /v1/ch/{cm-handle}/modules/definitions/{moduleName}
    (S)KMC : What level of access control is there today - both on CPS and NCMP interfaces?
    Send notifications on write operation in ncmp-datastores:running for Need to address case with incompatible model changes.
    Scope: Upgrade of model that is cached?  Lee Anjella to confirm. 
    3334
    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 1

    		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
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

    2
    • Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyCPS-1615

      Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyCPS-1616
    • CPS-NCMP
    • Priyank Maheshwari
    • Ericsson  Team 2
    • Q3 Target
    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 Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-1812
    (#7 below) any remaining work items have been move to that epic instead.

    Notifications

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

    Subscriptions

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

    3
    • 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
    jqlQuery"Epic Link" = CPS-1713
    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-1515
    • CPS-NCMP
    • Sourabh Sourabh 
    • Ericsson  Team 1
    • Q2 Target
    		Batch (bulk) Operations (Get, Query)

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

    All new events will comply to cloudevents.

    Jira 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-1717
     

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

    5
    • Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyCPS-1638
    • CPS-NMCP
    • Halil Cakal 
    • Ericsson Team 2
    		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 Legacy
    serverSystem Jira
    columnIdsissuekey,summary,assignee,status
    columnskey,summary,assignee,status
    maximumIssues20
    jqlQuery"Epic Link" = CPS-1638
    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-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 Legacy
    serverSystem Jira
    columnIdsissuekey,summary,assignee,status
    columnskey,summary,assignee,status
    maximumIssues20
    jqlQuery"Epic Link" = CPS-1733
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

    7
    • 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
    		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 Legacy
    serverSystem Jira
    columnIdsissuekey,summary,assignee,status
    columnskey,summary,assignee,status
    maximumIssues20
    jqlQuery"Epic Link" = CPS-1812
    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-1915
    • CPS-NCMP
    • Waqas Ikram (Unlicensed) 
    • Ericsson  Team 2

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


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

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

    (S)
    12
    • Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyCPS-1630
    • CPS-CORE (& NCMP TBC)
    • Lee Anjella Macabuhay
    • Deutsche Telekom
      (TechMahindra)
    		Support for list as top level data node

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

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


    Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,assignee,status
    columnskey,summary,assignee,status
    maximumIssues20
    jqlQuery"Epic Link" = CPS-1632
    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-1796
    • CPS-CORE & NCMP
    • 1865
    • TBC
    • TBC

    Spike for documenting Kafka interfaces using AsyncAPI

    		Yet to agree priorityA decision was made to abandon json+problem format

    Jira Legacy
    serverSystem Jira

    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-1704
    Refactor legacy NCMP ASync Response Events to use Cloud Events format(M)

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

    		16

    TBC

    		Support NCMP-CPS upgrade
    15
    • 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)


    16
    • 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)

    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,assignee,status
    maximumIssues20
    jqlQuery"Epic Link" = CPS-1704
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-1345

    17

    TBC

    		Support multiple identifiers (alternatives for CM Handle ID)

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

    		18Access control for topics which are created by NCMP .Spike needs to be conducted. 19Invoke YANG modelled action20Enhanced query support (fields)21Enhanced 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)NCMP-CPS upgrade

    Currently only custom upgrade is supported. (upon request)

    Requirement: It shall be possible to upgrade NCMP-CPS from release N-1 to N (without requiring manual intervention/workarounds). N is defined as any release requested by ESH

    • Note. Need to agree version strategy: use current ONAP x.y.z. numbering. Ericsson to communicate when a version is to be 'delivered' and 'y' increased

    Technical Debt to be addressed: Liquibase is used in CPS to manage data(upgrades) in CPS

    Study: Resolve technical debt (mixed data). NCMP Data upgrade. CPS Core need to support model upgrade so that NCMP can use it,

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

    Jira 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

    18

    TBC

    		Support multiple identifiers (alternatives for CM Handle ID)

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


    19
    		Access control for topics which are created by NCMP .Spike needs to be conducted. 
    20
    		Invoke YANG modelled action

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

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

    (S) - for passthrough. 

    *Spec out before Sept'23. No implementation. 

    		22

    TBC

    		Support ncmp-datastores:running for reading data (single CM handle, synchronous only)23TBCSupport ncmp-datastores:running for writing data (single CM handle, synchronous only)(S)  As per #18
    24Support relationships for 'Instance Identifier'

    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

    		25Retrieve single module resource26Access control for public interfaces (NCMP, CPS-Core, DMI?)27Fine-grained cache configuration28

    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

    		29TBC21
    		Enhanced query support (fields)

    Currently the passthrough has an 'fields' parameter to do a scoped query.  Propose to support this in non-passthrough so it is promoted to a fully supported option, e.g. {ncmp-root}/ncmp/v1/ch/335ff/data/ds/ncmp-datastore:passthrough-operational?
                  resourceIdentifier=/&options=(fields=ericsson-enm-comtop:ManagedElement/ericsson-enm-
                  gnbcucp:GNBCUCPFunction    /EndpointResource/LocalSctpEndpoint/attributes(sctpEndpointRef),
             

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

    (L) .

    *Spec out before Sept'23. No implementation. 


    22
    		Enhanced query support (scope)

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

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

    (L)

    *Spec out before Sept'23. No implementation. 


    23

    TBC

    		Support ncmp-datastores:running for reading data (single CM handle, synchronous only)See CPS-391 page for details about supported operations and combinations. Note: There can be some overlap between work items for #5, #6, #11 and #12.

    Read from operations.

    (S) - Forward only.  No validation or data enhancements (add prefixis)
    24TBCSupport ncmp-datastores:running for writing data (single CM handle, synchronous only)30schema-set update for CM handle with cached data present31Invoke YANG modelled RPCSpecification required. Rebbot/Reset type of actions on node. 32(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 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-1843

    		DMI Audit for DMI restarts

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

    1180

    26


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

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


    28
    		Fine-grained cache configuration

    29

    Support for HTTPS and authentication

    • Use Service-Mesh? Both ONAP and Ericsson (applied ISTIO using Envoy Proxy side-car) are working towards this. Check with Gareth Roper 
    		Validation required whether this is still needed. 

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

    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-703

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

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

    		DMI Audit for DMI restarts

    Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,assignee,status
    columnskey,summary,assignee,status
    maximumIssues20
    jqlQuery"Epic Link" = CPS-

    1865
  • TBC
    • TBC

    1843
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

    34

    Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,status
    maximumIssues20
    jqlQuery"Epic Link" = CPS-1865
    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.


    Spin-off user stories, yet to be prioritized

     JiraComponent(s)Related Work ItemDescriptionNotes

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

    		CPS-NCMP


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

    		CPS-NCMP


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

    		CPS-NCMP


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

    		CPS-NCMP


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

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

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

    		CPS


    Functionalities

    User Stories

    Expand
    titleOpen User Stories for 'Montreal Release'

    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
    maximumIssues20
    jqlQueryproject = CPS AND type = Story AND fixVersion = "Montreal Release" AND status = Open ORDER BY fixVersion ASC, priority DESC
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176


    Expand
    titleImprovements & Technical Debt (any release)

    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
    maximumIssues20
    jqlQueryfilter=12620
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176


    Expand
    titleClosed Stories

    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
    maximumIssues20
    jqlQueryproject = CPS AND type = Story AND fixVersion = "Montreal Release" AND status in (Closed, Done) ORDER BY updated DESC
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176


    Other Information

    Platform Maturity

    See the centralized wiki page: London Release Platform Maturity

    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.