VNF SDK Beijing Release Planning (M1)
Overview
Project Name | VNFSDK |
|---|---|
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 |
Scope
What is this release trying to address?
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.
Epics
Stories
Longer term roadmap
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 |
|---|---|
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 |