...
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 | |||
| VNF Validation program (ICE) | VNF Validation should be traceable against the VNF Requirements | |||
| Documentation | References to deliverables produced by this project may be included in various ONAP release documents maintained through the documentation project | |||
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. |
Third Party Products Dependencies
Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).
| Name | Description | Version | |||
|---|---|---|---|---|---|
| N/A | N/A | N/A | To fill out | To fill out | To fill out |
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
Testing and Integration Plans
Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.
Describe the plan to integrate and test the release deliverables within the overall ONAP system.
Confirm that resources have been allocated to perform such activities.
This VNF Requirements project does not generate code to be integrated by the Integration project.
However, the Integration project may be integrating VNFs, and those VNFs should have documented their degree of compliance against the published VNF Requirements.
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.
...
This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is erecommended recommended to provide these agreements and dates in this section.
...
| Date | Project | Deliverable |
|---|---|---|
| July 14 | VNF Requirements | VNF TOSCA Template Requirements |
| July 14 | VNF Requirements | VNF Management Requirements |
Documentation, Training
...
...
- Installation instructions
- Configuration instructions
- Developer guide
- End User guide
- Admin guide
- ...
...
| title | Note |
|---|
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.
Other Information
Vendor Neutral
...