...
| TOPIC | DESCRIPTION | WIKI PAGE | ||||||||||
| Requirements Proposal | This is a link to the requirements proposal made on the Requirements Sub-committee | 5G_OOF_SON_usecase_vF2F_rqmts_subcommittee.pptx | ||||||||||
| Architecture S/C info | Information on the Architecture sub-committee presentation |
ONAP_OOF_SON_R8_ArchCom_v1.0.pptx Wiki page ONAP-based SON for 5G networks: Honolulu Architecture Review | ||||||||||
| Prior Project "Base" Wiki | Link to the Frankfurt release page for this use case | |||||||||||
| Requirements Jira (REQ-###) Ticket | Link to the REQ Jira ticket for this use case |
| ||||||||||
| Key Use Case Leads & Contacts | USE CASE LEAD: @N N.K. ShankarShankaranarayanan , Swaminathan Seetharaman USE KEY CONTACTS: | |||||||||||
| Meetings Register & Recordings | Link to Use Case Team meetings. |
|
BUSINESS DRIVER
Executive Summary
...
| PROJECT | PTL | User Story / Epic | Requirement | ||||||||||
| A&AI | No impact | ||||||||||||
| AAF | No impact | ||||||||||||
| APPC | No impact | ||||||||||||
| CLAMP | No impact | ||||||||||||
| CC-SDK |
| Incorporate new Yang model, new VES message, and possibly interface to new CPS | |||||||||||
| DCAE |
| Minor enhancements in SON-Handler MS | |||||||||||
| DMaaP | No impact | ||||||||||||
| External API | No impact | ||||||||||||
| HOLMES | No impact | ||||||||||||
| MODELING | No impact, CPS related modeling aspects will be covered by CPS project | ||||||||||||
Multi-VIM / Cloud | No impact | ||||||||||||
| OOF | No impact, enhancements deferred to I-release | ||||||||||||
| OOM | No impact | ||||||||||||
| POLICY | No impact | ||||||||||||
| PORTAL | No impact | ||||||||||||
| SDN-C | No impact | ||||||||||||
| SDC | No impact | ||||||||||||
| SO | No impact | ||||||||||||
| VID | No impact | ||||||||||||
| VF-C | No impact | ||||||||||||
| VNFRQTS | No impact | ||||||||||||
| VNF-SDK | No impact | ||||||||||||
| CDS | No impact | ||||||||||||
| CPS |
| Models, and interface to store/retrieve OOF SON use case related data |
List of PTLs:Approved Projects
*Each Requirement should be tracked by its own User Story in JIRA
...
| 1 | There should be a test case for each item in the sequence diagram | NOT YET TESTED |
| 2 | create additional requirements as needed for each discreet step | COMPLETE |
| 3 | Test cases should cover entire Use Case | PARTIALLY COMPLETE |
Supporting Files
| Date | Description | File |
|---|---|---|
| Feb 04, 2021 | Presentation and Guilin demo given at LFN DDF | |
| Dec 08, 2020 | Presentation given to ArchCom | |
| Oct 15, 2020 | Presentation given at LFN vF2F on Honolulu requirements & Roadmap (in detail) Recording: See here. |