...
| 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 upgradeupgrade
- PNF PNP enhancementenhancement
- 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.
onap/so/api-handler-infra
onap/so/bpmn-infra
onap/so/catalog-db-adapter
onap/so/openstack-adapter
onap/so/request-db-adapter
onap/so/sdc-controller
onap/so/sdnc-adapter
onap/so/so-monitoring
onap/so/vfc-adapter
onap/so/vnfm-adapter
Architecture
High level architecture diagram
...
Anyone reading this section should have a good understanding of all the interacting modules.
...
...
- change pom files for ODL Neon SR1 upgrade
- increase version number in pom
...
- add scripts for startup springbook framework
- increase version number in pom
...
- add new LCM actions
- increase version number in pom
...
- move from oom Repo
Platform Maturity
Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.
...
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.
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 |
Currently Available
Currently Available
API Outgoing Dependencies
API this project is delivering to other projects.
| 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 | Detailed doc in SO
| 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
Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).
Name
...
OpenDaylight controller platform
...
FOSS used for Service Orchestrator
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized materialised (contingency).
| 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
...