...
| draw.io Diagram | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Tasks
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
- Epic 1 SDN-R disaggregation
- Story 1 Define disaggregated architecture
- Story 2 Dataprovider
- Task1 Provide own bundle and specify northbound interface.
- Task2 Provide test-solution for ODLUX Development
- Task3 Integrate with WT-Common
- Story 3 Extend other components to new architecture
- Story 4 DBaaS awareness
- Story 5 WS Notification Handling through webServices
- Story 6 multi-technology support for devicemanager
- Story 7 Support CoreModel 1.4
- Story 8 OOM solution of clustered disaggregated SDN-R
- Story 9 Adjustment of UX clients to new dataprovider
- Story 10 Solution Integration
- Story 11 Security considerations, Vulnerability report
- Story 12 Create WT-Common bundle for Configuration
- Epic 2 Network technology evolution and Integration
- Story 1 support IPV6
- Story 2 TLS/https everywhere
- Story 3 ONAP Portal integration
- Story 4 ONAP authentication/authorization
- Epic 3 Model-driven DMaap agent
- Story 1 Define architecture/API
- Story 2 enhance device manager
- Epic 4 UX Evolution
- Story 1 ODLUX AAI App
- Story 2 Complete Configuration app (Prio 1)
- Story 3 User/Group management App
...
- 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
- Change to to new RESTCONF (Frankfuert/ G...?)
References
- OOF-PCI Use Case - Dublin Release - ONAP based SON for PCI and ANR
- Logging Enhancements Project Proposal
- OOM Story:
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key OOM-1598 - Integration: SDNC-848
...