...
Requirements to be submitted till: 10/16/2020 , Initial release date: 1H21
Possible development start: 11/2020
Start could be:
For our The root EPICs for project ONAP CCSDK/SDNC the derived EPICs are here: TO BE UPDATE: CCSDK Guilin Release Planning
- Top level, server and solution: ADD JIRA
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key SDNC-1379 - ODLUX: ADD JIRA
Potential topic list
-
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key CCSDK-2882
Topic list
- Netconf CallHome (https://tools.ietf.org/html/rfc8071)
- CCSDK, ODL Related
- Decoupling ODL/Restconf <↔> Devicemanager (Impacts → More after Guilin, open discussion)
- (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 relatedSwitch from NetConf "replace" to NetConf "merge" requests -
- Prio 1: Move oran devicemanager to ONAP/SDNR
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key SDNC-
- 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
- Solution
- Start with Tileserver
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
- ODL Alu!!!!
- Move oran devicemanager to ONAP/SDNR
- ODLUX:
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key CCSDK-2882 - 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
- 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 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 menu
- Prio 1 Update NetworkMap (details tba) .. prereq: User management with personal data
- Prio 1 Update LinkCalculator (details tba)
- ConfigAppAdd dashboard
- ConfigApp: group root objects and lists per yang module
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key CCSDK-
- BasicAuth → JSON Web token Integrate with ONAP Usermanagement
3023
Istanbul
- Add dashboard
2396Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key CCSDK- - Create a User management ODLUX app which combines AAF needs and ODL shiro and/or ODL MD-SAL based authentication
- → openIdentity interface
- → ONAP status qua not really clear
- → Istanbul?
- Table enhancements:
- Add refresh button
- Add right-click context menu
- Update Typescript Version
- Update material-ui Version
- Update react version
- Extend aria-labels
- Update NetworkMap (details tba)
- Update LinkCalculator (details tba)
Istanbul
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.Point 1
Details for
Children Display |
---|
...