You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 39 Next »

The Overall release planning is here: Release Planning#El-AltoRelease . According to this plan there is no feature change planned for El Alto.

Frankfurt

Goal for this version is disaggregation of SDN-R into three major parts.

  1. UXWeb - Web service
  2. Devicemanager - Device controlling
  3. WTDB - Database

Improvements by Disaggregation

  • Better split regarding performance from the three originations: 1. devices southbound 2. Web users northbound 3. database processing.
  • Have one entrypoint for Web User access to different web services of SDN-R: UX Web Service, REST, RESTCONF, Netconf device related
  • Use ONAP database components
  • SDNC/CCSDK/SDNR Devicemanager cluster/Netconf
    • Provide function to support NETCONF/devicehandling by devicemanagers for one OpenDaylight mountpoint in a cluster.
    • Provider to consuming microservices to publish mountpoint state changes and capabilites of NETCONF/device.  (Used by O-RAN-SC OAM) (model-driven DMaaP Agent)
  • Solution integration test covers O-RAN-SC OAM (Operations and Maintenance) Scenarios.
  • RPC/bundle for devicemanager configuration service

Further changes

  • WEB Client data table access via extended odlux db api. See ODLUX DB API

API-Gateway is entry point for SDNR WEB service.

api_gw_architecture

Architecture

  • Three node types for wt service: Web service cluster, Devicemanager cluster, DB cluster
  • Features are provided by CCSDK/features/sdnr. 
  • One SDN-C/SDN-R image. Node types are configured:
    • by configuration parameter: WTSDNR-WEB, WTSDNR-DEVICEMANAGER, WTSDNR-DB
    • El Alto configuration "WTSDNR" not supported anymore
  • Server platform (Bold new in Frankfurt):
    • WEB: SDNC/ODL/Karaf: apigateway, odlux, helpserver, dataprovider
    • DEVICEMANAGER SDNC/ODL/Karaf: devicemodel, devicemanager, websocketmanager2 (Discussion: dataprovider as devicemanager DB client service)
    • DB: Alpine + Elasticsearch (ODL/Karaf not nessecary) .. Existing ONAP ES Image if possible.

Open points

  • Configuration
    • Which configuration for which cluster 
    • How many configuraton files
    • Run-time reconfiguration only via RPC
    • Internal cluster synchronization to be specified.
    • Initial configuration via file
    • Using MDSAL
  • WEB Cluster-DevicemanagerCluster - DB Cluster setup for dev environment and kubernetes
    • Kubernetes services?
    • relationship (1:1 or n to m) . WEB-Cluster-Node-N to Devicemanager-Cluster-Node-M. 
    • Access via DNS Name?
    • entry via virtual-IP/load-balancer ... Kubernetes service

References


  • No labels