...
- This project will deliver a unified set of VNF Guidelines and VNF Requirements.
- The VNF Guidelines and VNF Requirements must be versioned to enable evolution based on operational experience
- The VNF Guidelines and VNF Requirements will support the ONAP Architecture Principles.
- Update the VNF Requirements as prototype RFP text for the ONAP/Beijing release
- Update the VNF Guidelines as for the ONAP/Beijing release
- Identify a list of features and functionality will be developed.
- The VNF Guidelines and Requirements will support the Release 1 Use Cases.
- Use cases focused on VNF Requirements may be developed in this project, and they will need to be aligned with the ETE Platform use cases.
- Document the VNF Provider Guidelines for VNF Scaleout Use Case for the ONAP/Beijing release
- VNF Guidelines and Requirements are to be refined beyond prototype text (e.g. through EPIC statements, use cases) to deliver test cases and test procedures for us in VNF onboarding & validation. VNF Requirement level use cases to be aligned with ETE platform use cases
- Document the VNF Test Case Descriptions for VNF Package testing for the ONAP/Beijing release
- Identify what is in or out of scope. During the development phase, it helps reduce discussion.
- VNF Guidelines may be forward looking, or include best practices in VNF design and VNF lifecycle processes.
- VNF Requirements from ONAP APIs should be linked to the ONAP Release
- VNF Requirements may include:
- expected operational characteristics ( e.g. security, resilience, upgradeability)
- conditional requirements (e.g. When configured for deployment on High Availability Network Cloud Infrastructure, the VNF Shall …)
- Tool chain improvements
- Develop requirements structure/ metadata to support better linkage / tracking with other ONAP projects
- Develop templates for VNFs to demonstrate VNF Requirements conformance
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case).
The TSC identified the following Use cases for Release A:
| Release first proposed | TSC Use Case | VNFs identified in TSC Use case |
|---|---|---|
| (obselete)Use Case: VoLTE (vIMS + vEPC) | N/A | |
| 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 | |
| Beijing | Centralised Parser Distribution |
The VNF Requirements developed by this project are applicable to the VNFs identified in the TSC E2E use cases.
- a VNF Provider (developer) using VNF Requirements in designing, testing, and certifying a VNF for use on ONAP
- a Service Provider using VNF Requirements as prototype text for RFPs to acquire VNFs to run in an ONAP context see VNFRQTS-16
- VNF Validation Project uses VNF Test Descriptions developed by this project to implement VNF testing for validation purposes.
Minimum Viable Product
- A VNF Guidelines document summarizing VNF provider oriented deliverables and providing informative, forward lookiging guidance.
- A set of Integrated VNF Requirements for use as prototype RFP text.
- VNF Test Descriptions for use by VNF Validation project, traceable from the VNF Requirments
- VNF Use Case - VNF Provider Guidelines for VNF Scale Out Use Case
Functionalities
List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.
...
High level architecture diagram
At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.
Block and sequence diagrams showing relation within the project as well as relation with external components are expected.
The VNF Requirements Project is not delivering ONAP platform code, rather it delivers documentation targeted to VNF providers to enable thme to develop VNFS which can be more easily onboarded and operated by an Operator using an ONAP platform.
Anyone reading this section should have a good understanding of all the interacting modules.
API Incoming Dependencies
...
This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
List identified release gaps (if any), and its impact.
| Gaps identified | Impact | ||
|---|---|---|---|
| VNF Requirments linkage to testing | VNF Requirments are current provided for FPS purposes, but the linkage to testing and validation of those requirments is not yet in place. | To fill out | To fill out |
Known Defects and Issues
Provide a link toward the list of all known project bugs.
...