...
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:
| 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.
- 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 thsi this project to implement VNF testing for validation purposes.
...
| Date | Project | Deliverable |
|---|---|---|
| July 1421 | VNF Requirements | seed contributions in proper formats and repos |
| July 28 | VNF TOSCA Template Requirements | |
| July 14 | VNF Requirements | VNF Management Requirements |
| Requirements | documentation tool chain generating:
| |
| August 1 | VNF Requirements | Sprint 1 defined |
| August 3 | M2: Test Cases Defined | |
| August 24 | M3: | |
| September 14 | M4: | |
| September 28 | RC0 | |
| October 12 | RC1 | |
| October 26 | RC2 | |
| November 2 | 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.
...
FOSS activities are critical to the delivery of the whole ONAP initiative. The information may not be fully available at Release Planning, however to avoid late refactoring, it is critical to accomplish this task as early as possible.
List all third party Free and Open Source Software used within the release and provide License type (BSD, MIT, Apache, GNU GPL,... ).
In the case non Apache License are found inform immediately the TSC and the Release Manager and document your reasoning on why you believe we can use a non Apache version 2 license. Each project must edit its project table available at Project FOSS.
The VNF Requirements Project generates documentation, not code. As such it does not directly include any code directly. It may incorporate references to APIs etc generated by other ONAP projects. Any Open Source dependencies within those APIs should be documented by those projects.
Charter Compliance
The project team comply with the ONAP Charter.