Status 2020-08-26: drafty draft (Herbert Eiselt)
Detailed planned for this version
High level planning page: Honolulu Release Requirements
Requirements to be submitted till: 10/16/2020 , Initial release date: 1H21
Possible development start: 11/2020
Start could be:
The root EPICs for For our project ONAP CCSDK/SDNC the derived EPICs are here: TO BE UPDATE: CCSDK Guilin Release Planning
- Top level, server and solution: ADD JIRA
- ODLUX: ADD JIRA
Topic list
Honolulu
...
- Decoupling ODL/Restconf <↔> Devicemanager (Impacts → More after Guilin, open discussion)
...
-
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key SDNC-1379 - ODLUX:
...
-
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key CCSDK-2882
Topic list
- (TOP Leve request?) Initial data for devices: SDN-R interfacing with Configuration & Persistency Service
- Via ONAP/SDNC Project
- Prio1: ODL Aluminium (CCSDK) Prio2: ODL Magnesium
- MVP Solution
- Prio 2: Integrate/ deploy Tile-server
- Server related
- Prio 1: Move oran devicemanager to ONAP/SDNR
- Prio 1: Move oran devicemanager to ONAP/SDNR
- Request by an Operator for https://alpinelinux.org/posts/Alpine-3.12.0-released.html for ONAP SDN-R dockers → Alignment with CCDSK and others
- ODL Alu!!!!
- ODLUX:
- ConfigApp: group root objects and lists per yang module
- ConfigApp: Consider yang statements 'when' and 'must'
- ConfigApp: Show key values of list members using appropriate RestConf filters
- Add dashboard
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key CCSDK-2566 - BasicAuth → JSON Web token Integrate with ONAP Usermanagement
SDNC-1378 - Prio 1: Elasticsearch authentication
- Server parts for User management
- Topology Server→ Typescript to Java 11 (Spring MVC)
- Prio 2: RESTCONF 1 to N message router
- ODLUX:
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key CCSDK-2882 - Prio 1 MVP User management (User management)
- Integrate container with openIdentity interface and Usermanagement
- As close as possible to ONAP
- openIdentity interface
- ONAP Usermanagement feature status not really clear → Own shiro based solution
- Combine
- Create a User management ODLUX app which combines
- AAF needs and ODL shiro
- with own service
- Not: ODL MD-SAL based authentication
- BasicAuth → openIdentity token
- Prio 1 Framework maintenance
- Update Typescript Version
- Update material-ui Version
- Update react version
- Extend aria-labels
- Table enhancements:
- Prio 1 Type specific Table filter : UX-Framework Tablefilter
- Prio 2 Add refresh
- button
- Prio 2 Add right-click context
- Update Typescript Version
- menu
- Prio 1 Update Update NetworkMap (details tba) .. prereq: User management with personal data
- Prio 1 Update LinkCalculator (details tba)
- ConfigApp
- ConfigApp: group root objects and lists per yang module
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key CCSDK-3023
- ConfigApp: group root objects and lists per yang module
- Prio 1 MVP User management (User management)
Istanbul
- Add dashboard
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key CCSDK-2566 - ConfigApp
- ConfigApp: Consider yang statements 'when' and 'must'
- ConfigApp: Show key values of list members using appropriate RestConf filters
- ODLUX/RESTCONF: Switch from NetConf "replace"to NetConf "merge" requests -
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key SDNC-1158
(Attribute changes in root objects without handling the whole tree)
- Decoupling ODL/Restconf <↔> Devicemanager (Impacts → More after Guilin, open discussion)
- Netconf CallHome (https://tools.ietf.org/html/rfc8071) Integrate Operational Mountpoints.
Details for
Children Display |
---|
...