...
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project="vnf requirements" and issuetype in (story) and fixversion = "Beijing Release" serverId 425b2b0a-557c-3c0c-b515-579789cceedb
Longer term roadmap
Amsterdam- deliver overview VNF Guidelines & prototype RFP text requirements.
Beijing - Update Amsterdam deliverable for new ONAP features, Test Descriptions for VNF Package Testing, VNF Scaling Use case, tooling improvements
Casablanca - Extend tracability of VNF testing ( VNF Requirments Database),additional VNF provider use cases, Update Bejing deliverable for new ONAP features
Dublin - Design time VNF testing description, additional VNF provider use cases, Update Casablancadeliverable for new ONAP features
El Alto - Run time VNF testing description, update Dublin deliverable for new ONAP features
Frankfurt - Update El Alto deliverable for new ONAP featuresIndicate at a high level the longer term roadmap. This is to put things into the big perspective.
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
...
Sub-components are repositories are consolidate in a single centralized place. Edit the Release Components name for your project in the centralized page.
Architecture
High level architecture diagram
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.
Platform Maturity
Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.
Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
|---|---|---|---|---|
| Performance | NA | VNFRQTS is primarily a documentation project and does not deliver ONAP platform code |
| |
| Stability | NA | VNFRQTS is primarily a documentation project and does not deliver ONAP platform code |
| |
| Resiliency | NA | VNFRQTS is primarily a documentation project and does not deliver ONAP platform code |
| |
| Security | NA | VNFRQTS is primarily a documentation project and does not deliver ONAP platform code |
| |
| Scalability | NA | VNFRQTS is primarily a documentation project and does not deliver ONAP platform code |
| |
| Manageability | NA | VNFRQTS is primarily a documentation project and does not deliver ONAP platform code |
| |
| Usability | 1 | VNF Guidelines VNF Requirments | http://docs.onap.org/en/latest/guides/onap-user/vnfprovider.html |
|
API Incoming Dependencies
Other ONAP projects 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
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.
...
The VNF Requirments does not produce code interfaciong with platform APIs. The VNF Requirments do consoliate requirements from ONAP platform compontents that impact the design and development of VNFs. These ONAP platform components in the table below generate APIs that impact VNFs and so these are generally reflected in the VNF Requirements.
...