...
More detailed information under SDN-R Release/SDN-R Release Frankfurt
A further goal is the the enable SDN-R to be used and extended by O-RAN-SC.
- model-driven DMaaP Agent
- Extend SDN-R for O-RAN specific YANG-Specs and devicemanagers.
SDN-R Disaggregation means
- 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
- SDNR WEB service is entry point for WEB Browser/Client
...
- 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.
- Elasticsearch Version 6.4.3
- (docker run -d --name sdnrdb -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.
- See SDNC-848
- Selection depends on capabilites provided by hello-answer
- Provide Notifications via DMaaP
| Drawio | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
More detailed information: Disaggregated Architecture
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...