...
The content of this template is expected to be fill out for M1 Release Planning Milestone.
| Info | ||
|---|---|---|
| ||
Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki. |
| Table of Contents | ||
|---|---|---|
|
Overview
...
| TSC Use Case | VNFs identified in TSC Use case |
|---|---|
| (obselete)Use Case: VoLTE (vIMS + vEPC) | N/A |
| Use Case: Residential Broadband vCPE (Approved) | vBNG, vG_MUX, vG, vAAA, vDHCP, vDNS |
| Use Case: vFW/vDNS (Approved) | vFW, vPacketGenerator, vDataSink, vDNS, vLoadBalancer, all VPP based. |
| Use Case: VoLTE(approved) | vSBC, vPCSCF, vSPGW, vPCRF, VI/SCSCF, vTAS, VHSS, vMME |
The VNF Requirements developed by this project are applicable to the VNFs identified in the TSC E2E use cases.
...
| 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 |
| SDN-C | API requirements on VNFs | M2 | M3 | |
| APPC | VNF configuration requirements | M2 | M3 | |
| VF-C | VNF life cycle management and configuration | M2 | M3 | |
| Service Design & Creation | VNF onboarding | M2 | M3 | |
| DCAE | VNF reporting requirements | M2 | M3 | |
| Authentication and authorization Framework | VNF Security Requirements | M2 | M3 | |
| Modeling | Tosca Data Modeling for VNF | N/A | ||
| Multi-VIM/ MultiCloud | network cloud infrastructure requirements | N/A |
Outgoing Dependencies
The VNF Requirements Project does not generate code APIs, however, other projects are dependent on the outputs of this project. This release is delivering the following to other projects.
| Project 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 |
| VNF SDK | VNF tooling should support the development and packaging of VNFs that are conformant to the VNF Requirements | N/A | ||
| VNF Validation program (ICE) | VNF Validation should be traceable against the VNF Requirements | N/A see the VNFRQTS <> VNF Validation project Workflow wiki page | ||
| Documentation | References to deliverables produced by this project may be included in various ONAP release documents maintained through the documentation project | N/A see the VNFRQTS <> Documentation Project Workflows wiki page | ||
Reference VNFs (now Integration Project) | Reference VNFs should be VNF Requirement compliant. The Integration Project maintaining those Reference VNFS would be dependent on the VNF Requirements for validating compliance. | N/A see the VNFRQTS <> Integration Project Workflow wiki page |
Third Party Products Dependencies
...
However, the Integration project may be integrating VNFs, and those VNFs should have documented their degree of compliance against the published VNF Requirements.
refer to the VNFRQTS <> Integration Project Workflow wiki page.
Gaps
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.
...
| Date | Project | Deliverable |
|---|---|---|
| July 21 | VNF Requirements | seed contributions in proper formats and repos |
| July 28 | VNF Requirements | documentation tool chain generating:
|
| August 1 | VNF Requirements | Sprint 1 defined |
| August 3 | VNF Requirements | M2: Test Cases Defined |
| August 24 | VNF Requirements | M3: |
| September 14 | VNF Requirements | M4: |
| September 28 | VNF Requirements | RC0 |
| October 12 | VNF Requirements | RC1 |
| October 26 | VNF Requirements | RC2 |
| November 2 | VNF Requirements | Signoff |
Documentation, Training
The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset. The VNF project generates primarily documentation assets of various forms.
Refer to the wiki page on VNFRQTS <> Documentation Project Workflows
Other Information
Vendor Neutral
...