Priority | Epic/Component/Owner/Team/Target | Description | Notes | Jira(s) |
---|
1 | Jira |
---|
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-1645 |
---|
|
- CPS-Core
|
Ahila P 1 | Data Write/Read Performance | | Jira |
---|
server | ONAP Jira |
---|
columnIds | issuekey,summary,assignee,status |
---|
columns | key,summary,assignee,status |
---|
maximumIssues | 20 |
---|
jqlQuery | "Epic Link" = CPS-1645 |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
|
2 | Jira |
---|
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-1615 |
---|
|
Jira |
---|
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-1616 |
---|
|
- CPS-NCMP
- Priyank Maheshwari
- Ericsson Team 2
|
Implementation of | - LCM Subscriptions for CM data notifications.
- Forward CM data notifications
|
forwarded Notifications- by NCMP from DMI to application
|
Implementing Data Notifications & Subscription Notifications on a US by US basis | Note. These items is now incorporated in |
columnIds | issuekey,summary,assignee,status |
---|
columns | key,summary,assignee,status |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-1812 |
---|
| (#7 below) any remaining work items have been move to that epic instead.
|
|
maximumIssues | 20 | jqlQuery | "Epic Link" = CPS-1615 |
---|
count | true |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
Subscriptions
|
columnIds | issuekey,summary,assignee,status |
---|
columns | key,summary,assignee,status |
---|
maximumIssues | 20 |
---|
jqlQuery | "Epic Link" = CPS-1616 jqlQuery | "Epic Link" = CPS-1616 |
---|
count | true |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
|
3 | Jira |
---|
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
|
3TBC | 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 |
---|
server | ONAP Jira |
---|
jqlQuery | "Epic Link" = CPS-1713 |
---|
count | true |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
|
key | CPS-1434serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-1411 |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
|
|
Jira |
---|
server | ONAP Jira | serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS- |
---|
|
|
1412 Jira |
---|
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-1413 | Batch (bulk) Operations (Get, Query) | Allow batch operations for NCMP REST and CPS-Core Java Interfaces. All new events will comply to cloudevents. Jira |
---|
server | ONAP Jira |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS- |
---|
|
|
15594columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
jqlQuery | "Epic Link" = CPS-1515 |
---|
count | true |
---|
|
|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution | serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
|
key Jira |
---|
server | ONAP Jira |
---|
columnIds | issuekey,summary,assignee,status |
---|
columns | key,summary,assignee,status |
---|
maximumIssues | 20 |
---|
jqlQuery | "Epic Link" = CPS-1515 |
---|
serverId | CPS-1515 | CPS-NCMPSourabh Sourabh Ericsson Team 1Bulk Operations (Get, Query) | Allow bulk operations for NCMP (and/or) CPS REST Interfaces | 425b2b0a-557c-3c0c-b515-579789cceedb |
|
|
5 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
|
Jira |
---|
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-1415 |
---|
|
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 |
---|
server | ONAP Jira |
---|
columnIds | issuekey,summary,assignee,status |
---|
columns | key,summary,assignee,status |
---|
maximumIssues | 20 |
---|
jqlQuery | "Epic Link" = CPS-1638 |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
|
6 |
TBCCPS-NMCPTBCTBCEvent Digest | Additional field to help clients filter CM AVC Events | 7 | | AVC Subscription, advance filter | 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) | server | ONAP Jira |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a- |
---|
|
|
8 | Jira |
---|
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb | key | CPS- |
---|
|
|
1630CORE (& TBC)Lee Anjella MacabuhayDeutsche Telekom
(TechMahindra) | Update YANG schema-set for CM handle using ModuleSetTag | - Update 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 (already built in ?)
- Introduce concept of ModuleSetTag to prevent unnecessary trips to nodes to get al Modules
- will require NCMP module loader (for upgrade of Inventory model) instead of Liquibase steps!
| Jira |
---|
server | ONAP Jira |
---|
columnIds | issuekey |
---|
|
|
Support for list as top level data node | Jira |
---|
server | ONAP Jira |
---|
columnIds | issuekey,summary,assignee,status | columns | key,summary,assignee,status |
---|
maximumIssues | 20 |
---|
jqlQuery | "Epic Link" = CPS- |
---|
|
|
1630 1733 | serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
|
9serverId | 425b2b0a-557c-3c0ccolumnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS- |
---|
|
|
1632CORE (& TBC)Lee Anjella MacabuhayDeutsche Telekom
(TechMahindra)CPS & NCMP Feature Enhancement for M Release | 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). | Jira |
---|
server | ONAP Jira |
---|
columnIds | issuekey,summary,assignee,status |
---|
columns | key,summary,assignee,status |
---|
maximumIssues | 20 |
---|
jqlQuery | "Epic Link" = CPS- |
---|
|
|
1632 1812 | serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
|
10 | 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 |
---|
server | ONAP Jira |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary, |
---|
|
|
Jira |
---|
server | ONAP Jira |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution | serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS- |
---|
|
|
134511 | | Support multiple identifiers (alternatives for CM Handle ID) | 12 | | Support for 'Instance Identifier' | Should be possible to identify a cmhandle using multiple instance identifiers | 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 |
---|
server | ONAP Jira |
---|
columnIds | issuekey,summary,assignee,status |
---|
columns | key,summary,assignee,status |
---|
maximumIssues | 20 |
---|
jqlQuery | "Epic Link" = CPS-1915 |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
|
9 | Jira |
---|
server | ONAP Jira |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-1781 |
---|
|
- CPS-
|
118015 | Update 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. | 16 | Retrieve single module resource | /v1/ch/{cm-handle}/modules/definitions/{moduleName} | 17 | Existing 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) | 18 | Access control for public interfaces (NCMP, CPS-Core, DMI?) | KMC : What level of access control is there today - both on CPS and NCMP interfaces? | 19 | Fine-grained cache configuration | 20 | Send notification for updated CM handle metadata (public CM handle properties or YANG modules) | 21 | 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
| Jira |
---|
server | ONAP Jira |
---|
13 | 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. | 14 | Enhanced query support | 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), scope=ericsson-enm-comtop:ManagedElement/ericsson-enm-gnbcucp:GNBCUCPFunction/ EndpointResource/LocalSctpEndpoint/attributes(interfaceUsed==X2)) KMC : Do we support restconf like queries or xpath only? | | 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 |
---|
server | ONAP Jira |
---|
columnIds | issuekey,summary,assignee,status |
---|
columns | key,summary,assignee,status |
---|
maximumIssues | 20 |
---|
jqlQuery | "Epic Link" = CPS-1781 |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
|
10 | | Event Digest | Additional field to help clients filter CM AVC Events (S) | |
11 | | AVC Subscription, advance filter | 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)
(S) |
|
12 | Jira |
---|
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-1630 |
---|
|
- CPS-CORE (& NCMP TBC)
- Lee Anjella Macabuhay
- Deutsche Telekom
(TechMahindra)
| Support for list as top level data node |
| Jira |
---|
server | ONAP Jira |
---|
jqlQuery | "Epic Link" = CPS-1630 |
---|
count | true |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
|
13 | Jira |
---|
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-1632 |
---|
|
- CPS-CORE (& NCMP TBC)
- Priyank Maheshwari
- Deutsche Telekom
(TechMahindra)
| CPS & NCMP Feature Enhancement for M Release | | Jira |
---|
server | ONAP Jira |
---|
columnIds | issuekey,summary,assignee,status |
---|
columns | key,summary,assignee,status |
---|
maximumIssues | 20 |
---|
jqlQuery | "Epic Link" = CPS-1632 |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
|
14 | Jira |
---|
server | ONAP Jira |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
|
|
serverId | 425b2b0a-557c-3c0c-b515- |
---|
|
|
579789cceedbkey | CPS-703 |
---|
22 | | 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. | 23 | TBC | Support ncmp-datastores:running for writing data (single CM handle, synchronous only) | 24 | TBC | Send notifications on write operation in ncmp-datastores:running for (single CM handle, synchronous only) | | Yet to agree priority | A decision was made to abandon json+problem format | Jira |
---|
server | ONAP Jira |
---|
columnIds | issuekey,summary,assignee,status |
---|
columns | key,summary,assignee,status |
---|
maximumIssues | 20 |
---|
jqlQuery | "Epic Link" = CPS-1865 |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
|
15 | Jira |
---|
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-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 |
25 | schema-set update for CM handle with cached data present | Need 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 ( | Jira |
---|
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-1704 |
---|
|
|
DMAAP1681)Possible in a generic way or it can also listen to similar events sent by SDN-R (as suggested by Ahila P | Refactor legacy NCMP ASync Response Events to use Cloud Events format | (M) | |
JIRAcolumnskeytype,created,updated,dueassignee,status | columns | key,summary,assignee, |
---|
|
|
reporter,priority,status,resolutionstatus | maximumIssues | 20 |
---|
jqlQuery | "Epic Link" = CPS-1704 |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
|
key | CPS-392 |
---|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-393 |
---|
|
27 | Automatic (optional) Data Sync | Metadata (per cmHandle) controls whether this will happen or not | 28 | Invoke YANG modelled RPC | 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.
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.