...
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=vnfrqts and issuetype in (story) serverId 425b2b0a-557c-3c0c-b515-579789cceedb
Longer term roadmap
Indicate at a high level the longer term roadmap. This is to put things into the big perspective.As an ONAP project we will Create and maintain VNF Requirements targeted to ONAP user audiences and the tasks they perform so that we can enable a viable ecosystem of VNF developers using the ONAP platform.
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
| Deliverable Name | Deliverable Description | ||
|---|---|---|---|
VNF Guidelines VNF Requirements VNF EPICs VNF Use Cases VNF Test Descriptions | Documentation Documentation Documentation Documentation Documentation | To fill out | To fill out |
Sub-Components
VNF Guidelines:
VNF Requirements:
VNF EPICs:
VNF Use Cases:
VNF Test Descriptions:List all sub-components part of this release.
Activities related to sub-component must be in sync with the overall release.
Sub-components are repositories are consolidate in a single centralized place. Edit the Release Components name for your project in the centralized page.
ONAP Dependencies
List the other Other ONAP projects your depends on.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)
Architecture
High level architecture diagram
...
Anyone reading this section should have a good understanding of all the interacting modules.
API Incoming Dependencies
Incoming Dependencies
The VNF Requirements project (as a non-code project) does not directly interface with APIs, however, it is expected that VNF Requirements may reference APIs that VNFs may be required to support. List the API this release is expecting from other releases.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.
...
| 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
API this release is delivering to other releases.
| SDN-C | API requirements on VNFs | |||
| APPC | VNF configuration requirements | |||
| VF-C | VNF life cycle management and configuration | |||
| Service Design & Creation | VNF onboarding | |||
| DCAE | VNF reporting requirements | |||
| Authentication and authorization Framework | VNF Security Requirements | |||
| Modeling | Tosca Data Modeling for VNF | |||
| Multi-VIM/ MultiCloud | network cloud infrastructure requirements |
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 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 |
| 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
...