...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Amsterdam |
| 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?
...
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery key in (VNFSDK-18,VNFSDK-17,VNFSDK-10,VNFSDK-9,VNFSDK-8,VNFSDK-7,VNFSDK-6,VNFSDK-5,VNFSDK-4)project=vnfsdk and issuetype in (epic) and resolution = Unresolved serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
...
| Deliverable Name | Deliverable Description |
|---|---|
| Compliance Tool | Executable |
| Model | UML data 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 | Executable/Library |
| Function Test Framework | Executable/Library |
...
Sub-components are repositories are consolidate in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
- VNF Validation Program: responsible for developing a validation program to provide assurance of VNF interoperability with ONAP. It will document governance and processes.
- VNF Requriement : responsible for documenting VNF guidelines and requirements. It will produce requirements documents
- Modeling: align information model and TOSCA model
- Microservices Bus: register microservices
- SDC: handoff for VNF onboarding
Architecture
High level architecture diagram
...
Anyone reading this section should have a good understanding of all the interacting modules.
API Incoming Dependencies
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.
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) | |
|---|---|---|---|---|---|
| Microservice bus API | API for registration of the microservices | Date for which the API is reviewed and agreed | To fill out | Link toward the detailed API description | |
| SDC API | API for uploading to SDC catalognone |
API Outgoing 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 provide 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.
...
| 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
...
Each project must edit its project table available at FOSS VNF SDK.
Charter Compliance
The project team comply with the ONAP Charter.