...
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 Company (Alphabetical order) | AT&T, Amdocs, Bell Canada, CMCC, DT, Fujitsu, Huawei, Intel, Nokia, Orange, Samsung, Tech Mahindra |
Scope
What is this release trying to address?
- 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
- ODM 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 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.
...
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | Interface Type | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
SDC | APIs for distribute service models | Defined in Amsterdam | Delivered in Amsterdam | Incoming and Out going | |||||||||
A&AI | APIs for inventory data | Defined in Amsterdam | Delivered in Amsterdam | Out Going | |||||||||
SDN-C | APIs for network controller | Defined in Amsterdam | Delivered in Amsterdam | Out going | |||||||||
APP-C | APIs for application controller | Defined in Amsterdam | Delivered in Amsterdam | Out Going | |||||||||
VF-C | APIs for Network Service | Defined in Amsterdam | Delivered in Amsterdam | Out Going | |||||||||
Multi-VIM | APIs for Multi-VIM | Defined in Casablanca | Delivered in Casablanca and enhancements expected in F release. | Out Going | |||||||||
OOF | APIs for placement and homing | Defined in Beijing | Delivered in Beijing | Out Going | |||||||||
DCAE | For PNF instantiation message from DCAE over DMaap | Defined in Casablanca | Delivered in Casablanca | Incoming | |||||||||
SOL003 | ETS SOL003 interafces between SO and VNFM | Defined in D release | Delivered in D release | Out Going | |||||||||
CDS | gRPC APIs between SO and CDS | Defined in D release | Delivered in D release | Out Going | |||||||||
SOl005 | ETSI SOL005 interface between SO and NFVO (VFC / external) | Defined in F release | Delivered in F release |
| Out Going |
Third Party Products Dependencies
...
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
...