...
Release first proposed | TSC Use Case | VNFs identified in TSC Use case |
|---|---|---|
Release first proposed | TSC Use Case | VNFs identified in TSC Use case |
| Amsterdam | Use Case: Residential Broadband vCPE (Approved) | vBNG, vG_MUX, vG, vAAA, vDHCP, vDNS |
| Amsterdam | Use Case: vFW/vDNS (Approved) | vFW, vPacketGenerator, vDataSink, vDNS, vLoadBalancer, all VPP based. |
| Amsterdam | Use Case: VoLTE(approved) | vSBC, vPCSCF, vSPGW, vPCRF, VI/SCSCF, vTAS, VHSS, vMME |
| Beijing | 5G- RAN deployment, Slicing, SON | |
| Beijing | Enterprise vCPE --potential R1 use cases’ extension | vCPE, vAAA, vDHCP |
| Beijing | ONAP Change Management | |
| Beijing | SD-WAN | vBG |
| Beijing | Scale Out | VOLTE, vDNS |
| Beijing | Centralised Parser Distribution |
...
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
| Deliverable | repo | Files Structure of repo |
| VNF Guidelines: | vnfrqts/guidelines | File per chapter |
| VNF Requirements: | vnfrqts/requirements | File per chapter |
| VNF Use Cases: | vnfrqts/usecases | File per Use Case |
| VNF Test Descriptions: | vnfrqts/testcases | File Per Test Case Dscription |
| VNF EPICs: | vnfrqts/epics | not used in Casablanca Release |
Architecture
High level architecture diagram
...
Anyone reading this section should have a good understanding of all the interacting modules.
Platform Maturity
...
| Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
|---|---|---|---|---|
| Performance | NA | documentation |
| |
| Stability | NA | documentation |
| |
| Resiliency | NA | documentation |
| |
| Security | NA | documentation |
| |
| Scalability | NA | documentation |
| |
| Manageability | NA | documentation |
| |
| Usability | 1 | 1 Establish Linkage to VNF Testing (improved testability) Establish categorization and linkage to VNF Badging ( improved Usability) Toolchain improvements (improved consistency) | VNF Guidelines VNF Requirements VNF Use Cases VNF Test Case Descriptions |
|
...
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
Other ONAP projects that this VNF Requirements project depends on:
- SDN-C (for API requirements on VNFs)
- APPC (for VNF configuration requirements)
- VF-C (for VNF life cycle managment and configuration)
- Service Design & Creation (for VNF onboarding)
- DCAE (for VNF reporting requirements)
- Authentication and authorization Framework (for VNF Security Requirements)
- Modeling (for Tosca Data Modeling for VNF)
- Multi-VIM/ MultiCloud (for network cloud infrastructure requirements)
The VNF Requirments does not produce code interfaciong with platform APIs. The VNF Requirments do consoliate requirements from ONAP platform compontents that impact the design and development of VNFs. These ONAP platform components in the table below generate APIs that impact VNFs and so these are generally reflected in the VNF Requirements.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| To fill out | High level description of the API | Date for which the API is reviewed and agreed | To fill out | Link toward the detailed API description |
API Outgoing Dependencies
| APPC | VNF configuration requirements | M2 | M3 | APPC Documentation |
| Authentication and authorization Framework | VNF Security Requirements | M2 | M3 | |
| DCAE | VNF reporting requirements | M2 | M3 | DCAE APIs documentation |
| Modeling | Tosca Data Modeling for VNF | N/A | ONAP Modelling Specifications | |
| Multi-VIM/ MultiCloud | network cloud infrastructure requirements | N/A | MultiCloud Documentation | |
| SDN-C | API requirements on VNFs | M2 | M3 | SDNC APIs documentation |
| Service Design & Creation | VNF onboarding | M2 | M3 | SDC documentation |
| VF-C | VNF life cycle management and configuration | M2 | M3 | VF-C APIs documentation |
API Outgoing Dependencies
The VNF Requirements do not provide code with APIs, but the VNF Requirements are used as inputs by a number of other ONAP projects.API this project is delivering to other projects.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| To fill out | High level description of the API | Date for which the API is reviewed and agreed | To fill out | Link toward the detailed API description |
...