London Requirement Jira | Component(s) | Epic/Component/Owner/Team/Target | Description | Notes |
---|
Team & Work-Item Owner | Jira(s) |
---|
1 | Jira |
---|
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key |
---|
|
|
REQ-1405 | NCMP | Data Write/Read Performance |
NCMP (read) Requirements
It shall be possible get all cmhandles (anchors)
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)
with a given public property at a rate of 500/second (assuming 20k cmhandles are registered) Depensds on serverId | 425b2b0a-557c-3c0c-b515-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- |
---|
|
|
1348kieran 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
| Jira |
---|
server | ONAP Jira | serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS- |
---|
|
|
1171 Jira |
---|
server | ONAP Jira |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
| - LCM Subscriptions for CM data notifications.
- Forward CM data notifications by NCMP from DMI to application
| Note. These items is now incorporated in |
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution Jira |
---|
server | | serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS- |
---|
|
|
1326 (#7 below) any remaining work items have been move to that epic instead. |
|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
jqlQuery | "Epic Link" = CPS-1615 |
---|
count | true |
---|
|
|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution | serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
|
key | CPS-1344columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
jqlQuery | "Epic Link" = CPS-1616 |
---|
count | true |
---|
|
|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution | serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
|
key | CPS-14433 | Jira |
---|
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS- |
---|
|
|
1445 Jira |
---|
| 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) | |
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
jqlQuery | "Epic Link" = CPS-1713 |
---|
count | true |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
|
keyCPS-1475 | 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- |
---|
|
|
1509 Jira |
---|
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-1516 |
---|
|
Jira |
---|
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-1494 |
---|
|
Jira |
---|
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-1519 |
---|
|
| Batch (bulk) Operations (Get, Query) | Allow batch operations for NCMP REST and CPS-Core Java Interfaces. All new events will comply to cloudevents. |
serverId | 425b2b0a-557c-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- |
---|
|
|
1525 | Jira |
---|
server | ONAP Jira |
---|
jqlQuery | "Epic Link" = CPS-1515 |
---|
count | true |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
|
keyCPS-1536 | 2 | Jira |
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key |
---|
|
|
REQ1405NCMPImplementation of CM data notifications forwarded by NCMP from DMI to application | Implementing Data Notifications & Subscription Notifications on a US by US basis | | Jira |
---|
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-1385 |
---|
|
| 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 |
---|
server | ONAP Jira |
---|
columnIds | issuekey,summary, |
---|
|
|
issuetype,created,updated,duedate Jira |
---|
server | ONAP Jira |
---|
assignee,status | columns | key,summary,assignee, |
---|
|
|
reporter,priority,status,resolutioncolumns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-1386 |
---|
Subscriptions
status | maximumIssues | 20 |
---|
jqlQuery | "Epic Link" = CPS-1638 |
---|
|
|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
|
key | CPS-14316 | 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- |
---|
|
|
1392 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-1393 |
---|
|
| 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,summary,assignee,status |
---|
columns | key,summary,assignee,status |
---|
maximumIssues | 20 |
---|
jqlQuery | "Epic Link" = CPS-1733 |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
|
7 | 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- |
---|
|
|
1394 Jira |
---|
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-1492 | 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). | |
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-1496 |
---|
columnIds | issuekey,summary,assignee,status |
---|
columns | key,summary,assignee,status |
---|
maximumIssues | 20 |
---|
jqlQuery | "Epic Link" = CPS-1812 |
---|
|
|
Jira |
---|
server | ONAP Jira | serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
|
key | CPS-14978 | 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- |
---|
|
|
1561 | 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 |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-1573 |
---|
|
Jira |
---|
server | ONAP Jira | columnIds | issuekey,summary |
---|
|
|
,issuetype,created,updatedduedate,reporter,priority,,resolutiontype,created,updated,due,reporter,priority,status,resolutionserverId | 425b2b0a-557c-status | maximumIssues | 20 |
---|
jqlQuery | "Epic Link" = CPS-1915 |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
|
keyCPS-1599 | 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- |
---|
|
|
1565 | 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. |
3serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | REQ-1316 |
---|
columnIds | issuekey,summary,assignee,status |
---|
columns | key,summary,assignee,status |
---|
maximumIssues | 20 |
---|
jqlQuery | "Epic Link" = CPS-1781 |
---|
|
|
Jira |
---|
server | ONAP Jira | serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
|
keyREQ-1405NCMPSupport 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) | | | 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-1434 |
---|
|
Jira |
---|
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-1411 | Jira |
---|
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS- |
---|
|
|
1412 | Support for list as top level data node |
| Jira |
---|
server | ONAP Jira |
---|
jqlQuery | "Epic Link" = CPS-1630 |
---|
count | true |
---|
serverId | 425b2b0a |
---|
|
|
Jira |
---|
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|
|
key | CPS-1413columnIds | 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-1559 |
---|
4 | CPS-NCMP | Bulk Operations (Get, Query) | Allow bulk operations for NCMP (and/or) CPS REST Interfaces | | 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-579789cceedb |
---|
key | CPS- |
---|
|
|
1515 | Yet to agree priority | A decision was made to abandon json+problem format | |
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-1550 |
---|
columnIds | issuekey,summary,assignee,status |
---|
columns | key,summary,assignee,status |
---|
maximumIssues | 20 |
---|
jqlQuery | "Epic Link" = CPS-1865 |
---|
|
|
Jira |
---|
server | ONAP Jira | serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
|
key | CPS-155315 | Jira |
---|
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS- |
---|
|
|
1555 | 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 |
---|
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-1556 | Jira |
---|
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS- |
---|
|
|
1557jiraserverONAP Jira | serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-1558 |
---|
| Refactor legacy NCMP ASync Response Events to use Cloud Events format | (M) | |
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-1560 |
---|
Jira |
---|
server | ONAP Jira |
---|
columnIds | columnIds | issuekey,summary,assignee,status |
---|
|
|
issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution,type,createdupdated,due,reporter,priority,status,resolutionstatus | maximumIssues | 20 |
---|
jqlQuery | "Epic Link" = CPS-1704 |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
|
key | CPS-1583 |
---|
17 | | 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,
(XL) - Scope needs to be defined. Risk is scope not identified, efforts might increase. | Jira |
---|
server | ONAP Jira |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate |
---|
|
|
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-1614 |
---|
5 | CPS-NCMP | 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 |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
|
|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS- |
---|
|
|
14156 Jira |
---|
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-1128 |
---|
|
Deutsche Telekom (TechMahindra) | CPS-Core / CPS-NCMP | Support for list as top level data node | | Jira |
---|
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-491 |
---|
|
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-765 |
---|
|
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-766 |
---|
|
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-767 |
---|
|
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-1586 |
---|
|
| 7 | Jira |
---|
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-1128 |
---|
|
Deutsche Telekom (TechMahindra) | CPS-Core / CPS-NCMP | Support for multiple top-elements from different modules in one CM handle/anchor | | Jira |
---|
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-1051 |
---|
|
Jira |
---|
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-341 |
---|
|
| 8 | Jira |
---|
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | REQ-1405 |
---|
|
| NCMP-CPS | 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,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-1345 |
---|
|
| 9 | Jira |
---|
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | REQ-1405 |
---|
|
| CPS-Core NCMP-CPS | Support multiple identifiers (alternatives for CM Handle ID) | 10 | Jira |
---|
server | ONAP Jira |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | REQ-1316 |
---|
|
| Support for 'Instance Identifier' | Should be possible to identify a cmhandle using multiple instance identifiers | 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-1180 |
---|
|
| 11 | CPS-NCMP | 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. | 12 | CPS-NCMP | 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? | 13 | Move above 8 | CPS_Core / CPS-NCMP | 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. | 14 | CPS-NCMP | Retrieve single module resource | /v1/ch/{cm-handle}/modules/definitions/{moduleName} | 15 | CPS-Core / CPS-NCMP | 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) | 16 | CPS-Core / CPS-NCMP | Access control for public interfaces (NCMP, CPS-Core, DMI?) | KMC : What level of access control is there today - both on CPS and NCMP interfaces? | 17 | CPS-NCMP | Fine-grained cache configuration | 18 | CPS-NCMP | Send notification for updated CM handle metadata (public CM handle properties or YANG modules) | 19 | CPS-Core / CPS-NCMP | 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 |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-703 |
---|
|
| 20 | | CPS-NCMP | 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. | 21 | TBC | CPS-Core / CPS-NCMP | Support ncmp-datastores:running for writing data (single CM handle, synchronous only) | 22 | TBC | CPS-Core | Send notifications on write operation in ncmp-datastores:running for (single CM handle, synchronous only) | 23 | CPS-Core / CPS-NCMP | schema-set update for CM handle with cached data present | Need to address case with incompatible model changes. | 24 | (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 | DMAAP-1681 |
---|
| )Possible in a generic way or it can also listen to similar events sent by SDN-R (as suggested by Ahila P) | Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-392 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-393 |
---|
|
| 25 | CPS-NCMP | Automatic (optional) Data Sync | Metadata (per cmHandle) controls whether this will happen or not | 26 | CPS-NCMP | 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.