El Alto
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.
- UXWeb - Web service
- Devicemanager - Device controlling
- WTDB - Database
SDN-R 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
- API-Gateway is entry point for all SDNR WEB service.
Gliffy Diagram |
---|
size | 300 |
---|
name | api_gw_architecture |
---|
pageid | 48534134 |
---|
|
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.
- 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)
draw.io Diagram |
---|
border | true |
---|
viewerToolbar | true |
---|
| |
---|
fitWindow | false |
---|
diagramName | sdnr-post-dublin |
---|
simpleViewer | false |
---|
width | 600 |
---|
diagramWidth | 937 |
---|
revision | 16 |
---|
|
WEB Cluster-DevicemanagerCluster - DB Cluster setup for dev environment and kubernetes
- Each cluster is providing a Kubernetes services
- Service access via DNS Name
draw.io Diagram |
---|
border | true |
---|
viewerToolbar | true |
---|
| |
---|
fitWindow | false |
---|
diagramName | sdnr-deploy-frankfurt |
---|
simpleViewer | false |
---|
width | 400 |
---|
diagramWidth | 551 |
---|
revision | 3 |
---|
|
Open points
- Cluster internal notification handling
- 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
References