...
Project Name | Enter the name of the project |
---|---|
Target Release Name | Guilin |
Project Lifecycle State | Incubation |
Participating Company (in alphabetical order) | AT&T, Fujitsu, Huawei, Orange, Wipro |
Scope
What is this release trying to address?
...
Functional Requirements
- MDONS use case
Resources from FujitsuJira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key REQ-325 - Extend the existing route optimization in OOF to support the MDONS use case. (MDONS use case)
- 5G Network Slicing
Resources from Wipro, HuaweiJira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key REQ-342 - Support 5G slice instantiation workflows, by providing selection decisions (5G - Network Slicing)
- SON Optimization
Resources from WiproJira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key REQ-345 - Evolve the PCI optimizer to use ML/AI techniques
- CCVPN Transport Slicing (Stretch goal) (
(Basic TN NSSI Selection to be covered under 5G - Network Slicing use case)Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key REQ-347
Non - Functional Requirements:
Resources from Wipro (Huawei, Fujitsu to support where needed)
- Containers must have no more than one main process (REQ-365)
- ONAP projects must use only approved and verified base images for their containers (REQ-379)
Each ONAP project shall define code coverage improvements and achieve at least 55% code coverage (REQ-349)
- Containers must crash properly when a failure occurs (REQ-366)
- Each project will update the vulnerable direct dependencies in their codebase (REQ-323)
- No root access to the database from application container (REQ-358)
- OOF to use cert initializers for certificates(REQ-361)
- Apply common Swagger style and documentation generation tools(REQ-386)
Stretch goals
- Functional requirements
- CCVPN Transport Slicing - Impacts related to TN NSSI not covered under 5G - Network Slicing use case.
- Non Functional requirements
- Python 3.6 to 3.8 migration (REQ-373)
- Improve documentation. Document as you code. New features must have mandatory documentation along with code.
CII Silver badge; internal communication encrypted
- Move Helm Chart (OOM) at project level
- Unit test coverage beyond 55%
- Improve OOM deployment time for OOF helm charts.
...
- Approved New use cases:
- MDONS - Route optimization
- CCVPN - Transport Slicing
- Hardening/Test Only
- HPA - Hardening, Testing and Automation of vFW, vDNS, vCPE, VoLTE
- Traffic Distribution
- Change Management Frankfurt Extensions (low priority)
- Extensions of existing use cases
- 5G E2E Network Slicing
- 5G OOF-SON
...
High level architecture diagram
Platform Maturity
Please fill out the centralized wiki page: Frankfurt Guilin Release Platform Maturity
API Incoming Dependencies
...
API this project is delivering to other projects.
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | Status |
---|---|---|---|---|---|
HAS API | API to submit homing requests, and retrieve homing solutions (SO, VFC) | El Alto Release | Completed | ||
Extensions to |
APIs to support network slicing workflows (NST, NSI and NSSI selection) | Guilin Release | TBD | In progress | In progress |
SON API | API to perform SON optimization |
Frankfurt Release | Completed | ||
Route API | API to perform Route optimization (used by CCVPN use case) |
Frankfurt Release | Completed | ||||
API enhancements for Route Selection for MDONS use case | Guilin Release | TBD | In progress | In progress | |
CMSO API | API invoked by CM use case for schedule optimization | El Alto Release | Completed |
Third Party Products Dependencies
...
Known Defects and Issues
Please refer to Frankfurt Guilin Defect Status.
Risks
...
- Meeting the non-functional requirement for CMSO project. There are no active contributers for the project right now. Requests have been sent for supporting to meet the non-functional requirements.
Please update any risk on the centralized wiki page -Frankfurt Guilin Risks.
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.
...
Please update the following centralized wiki:Frankfurt Guilin Documentation.
That includes
- Team contributions to the specific document related to he project (Config guide, installation guide...).
- Team contributions to the overall Release Documentation and training asset
- High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
- Documentation includes items such as:
- Installation instructions
- Configuration instructions
- Developer guide
- End User guide
- Admin guide
- ...
...