-
Epic
-
Resolution: Done
-
Medium
-
None
-
SDN-R Guilin
-
To Do
Details: https://wiki.onap.org/display/DW/Guilin
Integration with ONAP / external services
- Interfacing with o-ran-sc project. https://jira.o-ran-sc.org/browse/OAM-132
- ONAP oom starts extended SDNC as nonrtric-o1
- Move RAN devicemanagement capabilities for TR069, O-RAN (open fronthaule), 3GPP (o1) [https://wiki.onap.org/display/DW/Specific+devicemanager+start+condition+and+features]
- Rename devicemanager-oran to "devicemanager-adapter-manager" and keep NTSIM related parts.
- Devicemanager related changes: https://jira.onap.org/browse/CCSDK-2553
- Integration ODL TransportPCE as microservice
SDNC-848 - Elasticsearch 7.x support
SDNC-1112and seccom requirements - ODL Sodium, RFC8040 https://jira.onap.org/browse/CCSDK-2396
- Add ONF 1.4 and openROADM devicemanager
- ODLUX extensions:
CCSDK-2556https://jira.onap.org/browse/CCSDK-2556
Integration test steps
- Solution definition depicted here: https://wiki.onap.org/display/DW/ONAP+SDN-R+Guilin+Kubernetes+Pods+and+Options
- Startup solution
- Mount and connect
- all types of devices by using O-RAN/NTSSIM
- Mount and connect 100 devices.
- Test described in network map EPIC
- Success if
- Containers are running
- All simulated devices are connected
- Simulated notifications and alarms are visible in the WEB App
- Equipment app shows equipment.
- relates to
-
CCSDK-2553 Add Sodium SR3 compatibility to SDN-R features
- Closed
-
CCSDK-2556 SDN-R ODLUX improvements
- Closed
- mentioned in
-
Page Loading...