...
| Table of Contents | ||
|---|---|---|
|
Overview
| Project Name | Enter the name of the projectVNFSDK |
|---|---|
| Target Release Name | Beijing |
| Project Lifecycle State | Incubation |
| Participating Company | Huawei, Intel, AT&T, Gigaspaces, China Mobile, Wind River, Orange, Amdocs, Nokia, ZTE, IBM, VMWare, Cisco, ARM |
...
What is this release trying to address?
Describe the problem being solved by this release
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case).VNF SDK's mission is to simplify the process of developing and onboarding VNFs and expanding ONAP's VNF ecosystem. For Service Providers, VNFSDK will reduce the time and level of testing required to identify, select, and onboard a VNF. For vendors, VNFSDK will reduce integration efforts by defining a standard for VNF packaging with widespread operator acceptance. VNFSDK can be used in a validation/conformance testing program in the future.
The Beijing release will enhance existing functionality, introduce security, integrate with ONAP use-case flow and progress towards being carrier grade with high quality.
- Better integration with SDC for automatic onboarding
- Update pkgtools/marketplace to support VNF packaging model. Update VNF template to align with VNFD information model.
- add pkgtools to pypi
- Integrate VVP (ICE) tools to allow us to validate VNF packaging (not acceptance testing)
- Improve code quality & code coverage
- Improve security (S3P) (https, SOL004, possibly certificate validation)
- Align with VNF Requirements
- Experimental integration with OPNFV Dovetail test framework
- Begin work on functional testing (ONAP-lite test platform, test framework, specific tests)
Use Cases
- Integrate VVP (ICE) tools
- Standalone validation tool
- HPA
Minimum Viable Product
Describe the MVP for this release.
- Support the VNF packaging model & VNF Requirements defined in Amsterdam
- Enhance integration with SDC
- Integrate ICE tools
- 50% code coverage
- HPA
Functionalities
List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.
...
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=sanbox vnfsdk and issuetype in (epic) and fixversion="Beijing Release" serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
...
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=sanbox vnfsdk and issuetype in (story) and status not in (done) serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
...
Indicate at a high level the longer term roadmap. This is to put things into the big perspective.
- Support functional testing (requires ONAP-lite test framework)
- Support VNF conformance/validation testing
- Integrate with Dovetail test framework
- Support VNF lifecycle tests
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
| Deliverable Name | Deliverable Description | To fill out | To fill out|
|---|---|---|---|
| Compliance Tool | Executable | ||
| Model | UML info model and TOSCA model | ||
| Packaging tool | Executable | ||
| Reference Repo/Marketplace | Executable | ||
| API : Deliver API for external Project. The API will deliver such as uploading/downloading/Updating/etc functionality | |||
| Validation Tools | Executable | ||
| Lifecycle Test Framework (future) | Executable/Library | ||
| Function Test Framework (future) | Executable/Library | ||
| VES Agent | code/libraries that can be included in VNFs |
Sub-Components
List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall release.
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
Indicate where your project fit within the ONAP Archiecture diagram.
Block and sequence diagrams showing relation within the project as well as relation with external components are expected.
Anyone reading this section should have a good understanding of all the interacting modules.
| Anchor | ||||
|---|---|---|---|---|
|
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 | 0 | 0 | design-time component |
|
| Stability | 1 | 1 | design-time component |
|
| Resiliency | 1 | 1 | system run as-needed |
|
| Security | 0 | 1 | increase test coverage to 50%. Implement https and aspects of SOL-004 |
|
| Scalability | 0 | 0 | not a runtime component. VNF SDK will be run as-needed in constrained environment. |
|
| Manageability | 1 | 1 |
| |
| Usability | 1 | 1 | onap.readthedocs.io |
|
...
List the API this project is expecting from other projects.
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.
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
| 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 |
...
| none |
API Outgoing Dependencies
API this project is delivering to other projects.
| 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
|---|---|---|---|---|---|---|---|---|
| Upload API | API for vendors to upload VNF packages to marketplace | M1 | M3 | API Documentation | ||||
| Download API | API for downloading VNF Package from marketplace | M1 | M3 | API Documentation | ||||
| Query VNF information | API to query information on VNFs uploaded to the marketplace | M1 | M3 | API Documentation |
Third Party Products Dependencies
...
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.
We will enhance unit tests and CSIT tests for validation tools, packaging tools, and certification tools.
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.
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
| To fill out | To fill out | To fill out |
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...