Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Requirements to be submitted till: 10/16/2020 , Initial release date: 1H21

Development start: 11/2020

Start could be: 

For our project ONAP CCSDK/SDNC the derived EPICs are here: TO BE UPDATE: CCSDK Guilin Release Planning

  1. Top level, server and solution: EPIC-1 ADD JIRA 
  2. ODLUX: Top Level EPIC-2  ADD JIRA

Potential 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
  • Switch from NetConf "replace" to NetConf "merge" requests - 
    Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keySDNC-1158
  • 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 
  • Via ONAP/SDNC Project
    • ODL Alu!!!! (CCSDK)
  • Solution
    • Prio 2: Integrate/ deploy Tileserver
  • Server related
    •  Prio 1:
    Server related
    • ODL Alu!!!!
    • Move oran devicemanager to ONAP/SDNR
    • Prio 1: ES authentification
    • Server parts for User management
    • Topology server → Typescript auf Java (Spring ...)
    • Prio 2: RESTCONF 1 to N message router
  • ODLUX: 
    Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyCCSDK-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: Table enhancements: Type specific Table filter : UX-Framework Tablefilter
    • Add dashboard 
      Jira
      serverONAP JIRA
      serverId425b2b0a-557c-3c0c-b515-579789cceedb
      keyCCSDK-2566
    • BasicAuth → JSON Web token
    • Prio1: Integrate with ONAP Usermanagement 
      Jira
      serverONAP JIRA
      serverId425b2b0a-557c-3c0c-b515-579789cceedb
      keyCCSDK-2396
      • 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
          • clear → Own shiro based solution
        • BasicAuth → JSON Web token
        • → Istanbul?
      • Prio 1 Framework maintenanceTable enhancements:
        • Add refresh button
        • Add right-click context menu 
        • Update Typescript Version
        • Update material-ui Version
        • Update react version
        • Extend aria-labels
      • Prio 1 Update NetworkMap (details tba) .. prereq: User management with personal data
      • Prio 1 Update LinkCalculator (details tba)
      • Prio 2 Table enhancements:
        • Add refresh button
        • Add right-click context menu 

    Istanbul

    • Add dashboard 
      Jira
      serverONAP JIRA
      serverId425b2b0a-557c-3c0c-b515-579789cceedb
      keyCCSDK-2566
    • ConfigApp
      • 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
      • ODLUX/RESTCONF: Switch from NetConf "replace"to NetConf "merge" requests - 
        Jira
        serverONAP JIRA
        serverId425b2b0a-557c-3c0c-b515-579789cceedb
        keySDNC-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

    ...