# | Epic | Project/Component | Description | (Suggested) Stories | Comments |
---|
1 | E2E Network Slicing Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-382 |
---|
|
| CPS/NCMP | create rest interface on northbound for GET/POST/PUT/DELETE to access yang data. Note. Currently driven by "E2E Network Slicing" Use Case mix of CPS-CORE and NCMP Interface
| - Spike API for Update and Delete Operations
Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-278 |
---|
| - 'List' support
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-360 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-362 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-361 |
---|
|
- Remove/migrate? 'hardcoded generic models used in H release"
| - interfaces for yang data are: operational, intended, pass-through (selection can be done by parameter)
check with netconf-sim if current nw slicing yang model can be imported including its imports.
|
2 | DMI-Registry Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-383 |
---|
|
| (NCMP) DMI-Registry | Create dmi-registry. Data Model Inventory Interface (DMI) 'Internal service' no public Java or REST API responsibilities are - Store & retrieve cm-handle/dmi-plugin mapping in yang modelled CPS data table.
- include additional data (key-value pars as provided by dmi-Plugin)
- Dmi manager is to select the dmi instance at runtime for cm handle for a northbound (write) request
| - Define and Agree Yang Data Model
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-352 |
---|
|
- Create Dataspace & Anchor for DMI Registry
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-353 |
---|
|
- Spike: How will DMI Plugin (De-?)Register with NCMP (DMI Registry)
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-389 |
---|
|
- Implement Plugin Registration (DMI Registry Side)
- Add CMHandle (registration) incl. 'Additional properties'
- Remove CMHandle (registration)
|
|
3 | DMI-Plugin Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-384 |
---|
|
| DMI-Plugin (ONAP impl.) | Common standard (REST and Java?) interface for extensibility create dmi plugin for onap. Its responsibility of admin to provide instance of dmi. | - Define and agree NCMP & DMI REST Interfaces (Ericsson will provide output internal study)
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-390 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-391 |
---|
|
- Implement Plugin Registration (DMI Plugin Side)
- create module dmi-onap-plugin Rest and Impl modules. Suggestion (TBC):
- sub-module dmi-notification-handler
- sub-module dmi-rest
- sub-module dmi-plugin
- create infra for separate spring boot application and docker image for dmi-plugin
| - extract dmi-plugin into separate container consensus on rest interface is needed.
|
4 | Inventory Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-385 |
---|
|
| DMI-Plugin (ONAP impl.) | - Capability to get initial Inventory
- Process Inventory updates
| - MVP: hard-coded inventory list
- Spike A&AI inventory list
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 |
---|
|
- Spike A&AI event subscription & filtering only yang modelled xnf instances's
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-393 |
---|
|
|
|
5 | Model & Data Sync Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-386 |
---|
|
| DMI-Plugin (ONAP impl.) |
| - Spike SDNC Interface for Model Retrieval
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-394 |
---|
|
|
|
6 | Pass-Thru Support Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-388 |
---|
|
| DMI-Plugin (ONAP impl.) | - dmi plugin instance (onap-dmi) have sdnc connector to access sdnc.
- call get/post/put/delete towards restconf interface (forward northbound write requests)
| - Define and agree NCMP & DMI REST Interfaces (Ericsson will provide output internal study)
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-390 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-391 |
---|
|
- Spike SDNC Interface for CRUD Operations
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CPS-395 |
---|
|
| Possibly overlaps with #1 E2E Network Slicing |