...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Frankfurt Release |
| Project Lifecycle State | Either Incubation, Core, Mature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
| Participating Company (Alphabetical order) | AT&T, Amdocs, Bell Canada, CMCC, DT, Fujitsu, Huawei, Intel, Nokia, Orange, Samsung, Tech Mahindra |
...
- Integrate the AAF and upgrade the APIs to Https - ATT
- ETSI alignment improvements - Ericcson, Huawei, Verizon
- SOL005 adaptation
- SOL003 adaptation
- PNF orchestration Enhancements - Ericcson, Huawei, Nokia
- PNF sotware upgrade
- PNF PNP enhancement
- CCVPN Enhancement
- MDONS support - Fujitsu
- Eline support - Bell, Huawei, CMCC
- 5G Slicing - ATT, Amdocs, CMCC, Huawei, Wipro
- CDS integration enhancement - ATT, Bell, Tech Mahindra
- (SO Multi Cloud plugin improvements - Intel)
- HPA - Intel (Testing effort)
- Component Upgrades to new Policy Lifecycle API : Resource commitment is being checked (ATT??)
Release Requirements
Features Being considered for F releaserelease (As per the resource availability):
| SOL005 Adapter supports communication security |
| SOL005 Adapter supports NS/VNF Package Management and NS LCM |
| Multi-domain Optical Network Service Orchestration Support in SO |
| SOL002 Adapter - supports EM-triggered VNF/VNFC Management |
| SO Catalog Management Support |
| Frankfurt release planning milestone |
| Initiate/ Terminate slice service; Activate/deactivate Slice service |
| SO support of Network Slicing Demo in Frankfurt |
| ETSI Alignment Support - SOL003 Adapter Enhancement for Frankfurt |
| AAI update for VNF improvements |
| SO Multicloud plugin to Multicloud improvements |
| SO to CDS Enhancement for Generic Implementation |
...
| S3P |
...
- Document current upgrade component strategy
- SECCOM Perform Software Composition Analysis - Vulnerability tables
- SECCOM Password removal from OOM HELM charts
- SECCOM HTTPS communication vs. HTTP
In addition, looking at the stories, it is unclear if you have committed to
...
| improvement Requirements |
| Upgrade the APIs to Policy |
Minimum Viable Product
Same as was defined for E-alto, but is going to add AAF integration with external APIs updated to https.
...
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
List the API this project is expecting from other projects.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
...
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
| To fill out | To fill out | To fill out |
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...