...
- 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 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)
Release Requirements
Features Being considered for F release
...
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
...
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
...
| 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 |
...