| Table of Contents | ||
|---|---|---|
|
Overview
| Project Name | VNFSDK |
|---|---|
| Target Release Name | Dublin |
| Project Lifecycle State | Incubation |
| Participating Company | Huawei, Intel, AT&T, Gigaspaces, China Mobile, Wind River, Orange, Amdocs, Nokia, ZTE, IBM, VMWare, Cisco, ARM |
Scope
...
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.
Minimum Viable Product
TBA
...
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project = vnfsdk and issuetype in (epic) and fixversion=VNFSDK AND issuetype = Epic AND resolution = Unresolved AND fixVersion in ("Casablanca Release", "Dublin 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=vnfsdk and issuetype in (story) and status not in (done) and fixversion="Casablanca Dublin Release" 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 VNF Function tests
- Support VNF lifecycle Performance 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 | Executable |
| 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.
...
| 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 | 1 | 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 environment1 | VTP will support scalability as default. |
|
| 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.
...
| 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
...