...
- 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
...
- -Gateway is entry point for all SDNR WEB service.
| Gliffy | ||||||
|---|---|---|---|---|---|---|
|
WEB Client
- Data table access via extended odlux db api. See ODLUX DB API
- configApp support Core model 1.4
- connectApp accept IPV6 and DNS names
- NEW aai App
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.
- (docker run -d --name elasticsearch -p 9200:9200 -p 9300:9300 -e "discovery.type=single-node" --network yaml_default docker.elastic.co/elasticsearch/elasticsearch:6.4.3)
- APIGateway: Add RestConf Forwarding
- DB as a Service
- WS notification forwarding to WEB Service and Client
- Devicemanager disaggregation for multi-technolgy support. (Used for CoreModel 1.4)
- Goal: Different devicemanager bundles, managing netconf devices. E.g. devicemanager1.2, devicemanager1.4, DevicemanagerPM.
- Selection depends on capabilites provided by hello-answer
...