Versions Compared

Key

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

Detailed planned for this version

High level planning page: SDN-R GuilinGuilin Release Requirements

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

  1. Top level, server and solution: 
    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keySDNC-1290
  2. ODLUX: 
    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCCSDK-2556

Topic list

  • Integration with ONAP / external services
    • (XM1) Integration TransportPCE as microservice 
      Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keySDNC-848
      • southbound restconf interface instead of netconf
      • restconf according to RFC8040 (Precondition SDN-R provides related interface)
      • Integration test of SDN-R together with TransportPCE image.
    • (XM1) Elasticsearch 7.x support
      • Client/Common: 
        Jira Legacy
        serverSystem Jira
        serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
        keySDNC-1112
      • Integration:  SECCOM requires version 7.6.1 for Guilin
    • Interfacing with o-ran-sc (https://jira.o-ran-sc.org/browse/OAM-132)
      • O-RAN-SC project uses ONAP Guilin sdnc-image to
        • Add RAN specific devicemanagers
        • And provides it back as nonrtric-o1 image
        • startable by ONAP oom Kubernets/Helm setup
    • Integration test
      • ES basic auth: 
        Jira Legacy
        serverSystem Jira
        serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
        keyOOM-2537
      • Secure SDNC/SDN-R user/password initializing.
      • IP V4/V6: 
        Jira Legacy
        serverSystem Jira
        serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
        keySDNC-895
  • CCSDK, ODL related, non functional
  • Devicemanagement
    • New devicemanagers: Specific devicemanager start condition and features 
    • Handled via 
      Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyCCSDK-2553
      • (XA) Add ONF 1.4 devicemanager (
        Jira Legacy
        serverSystem Jira
        serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
        keySDNC-658
        )
      • (XR) Add TR-069 devicemanager (required with Service NetConf CM Notification) → moved to o-ran-sc
      • (XS) Integration of OpenROADM 
        • Devicemanager. Devicemanager specific OpenROADM 6.1.0
        • Mediator for optical performance measurement device
        • Use extended melacon/ntsim
        • Provide data-provider-v2 with optical (
          Jira Legacy
          serverSystem Jira
          serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
          keyCCSDK-2582
          )
      • (XH) O-RAN-SC Add Healthcheck to devicemanager-oran: 
        Jira Legacy
        serverSystem Jira
        serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
        keySDNC-1055
    • (XH) issue155 devicemanager states
  • Services
    • ODLUX UI Improvements (
      Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyCCSDK-2556
      )
      • (XM2) Change authorization to BasicAuth
      • (XM2) Switch from Biermann-RestConf to RFC8040 interface 
        Jira Legacy
        serverSystem Jira
        serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
        keyCCSDK-2565
      • Update Inventory App 
        Jira Legacy
        serverSystem Jira
        serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
        keySDNC-1119
         
      • (XA) Add NetworkMap (
        Jira Legacy
        serverSystem Jira
        serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
        keyCCSDK-2559
        )
      • Add Link Calculator App
    • (XR) NetConf CM Notification Handling  (NetConf CM Notification Handling) and 
      Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keySDNC-1188
      • affecting "mountpoint-registrar" bundle
    • Servicability: Add function to collect information for service-issues.
  • ONAP Non functional

Honolulu

  • Netconf CallHome (https://tools.ietf.org/html/rfc8071)
  • CCSDK, ODL Related
    • Decoupling ODL/Restconf <↔> Devicemanager (Impacts → More after Guilin, open disussion)
  • Add dashboard 
    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCCSDK-2566
  • BasicAuth → JSON Web token
  • Integrate with ONAP Usermanagement 
    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCCSDK-2396
  • SDN-R interfacing with Configuration & Persistency Service
  • Switch from NetConf "replace" to NetConf "merge" requests - 
    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keySDNC-1158
  • ConfigApp: Consider yang statements 'when' and 'must'

Details for

Child pages (Children Display)

Guilin related Jiras (not closed)

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues40
jqlQueryproject=SDNC & "labels"=highstreet & fixVersion in ("Guilin Release") & "status"!="closed"
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176