Detailed planned for this version
High level planning page: SDN-R Guilin, Guilin Release Requirements
For our project ONAP CCSDK/SDNC the derived EPICs are here: CCSDK Guilin Release Planning
- Top level, server and solution:
- ODLUX:
Topic list
- Integration with ONAP / external services
- (XM1) Integration TransportPCE as microservice
- southbound restconf interface instead of netconf
- restconf according to RFC8040 (Precondition SDN-R provides related interface)
- Integration test of SDN-R together with TransportPCE image.
- (XM1) Elasticsearch 7.x support
- Client/Common:
- Integration: SECCOM requires version 7.6.1 for Guilin
- Interfacing with o-ran-sc (https://jira.o-ran-sc.org/browse/OAM-132)
- O-RAN-SC project uses ONAP Guilin sdnc-image to
- Add RAN specific devicemanagers
- And provides it back as nonrtric-o1 image
- startable by ONAP oom Kubernets/Helm setup
- Integration test
- ES basic auth:
- Secure SDNC/SDN-R user/password initializing.
- IP V4/V6:
- CCSDK, ODL related, non functional
- Devicemanagement
- New devicemanagers: Specific devicemanager start condition and features
- Handled via
- (XA) Add ONF 1.4 devicemanager ()
- (XR) Add TR-069 devicemanager (required with Service NetConf CM Notification) → moved to o-ran-sc
- (XS) Integration of OpenROADM
- (XH) O-RAN-SC Add Healthcheck to devicemanager-oran:
- (XH) issue155 devicemanager states
- Services
- ODLUX UI Improvements ()
- (XM2) Change authorization to BasicAuth
- (XM2) Switch from Biermann-RestConf to RFC8040 interface
- Update Inventory App
- (XA) Add NetworkMap ()
- Add Link Calculator App
- (XR) NetConf CM Notification Handling (NetConf CM Notification Handling) and
- affecting "mountpoint-registrar" bundle
- Servicability: Add function to collect information for service-issues.
- ONAP Non functional
Details for
Guilin related Jiras (not closed)