The content of this template is expected to be fill out for M1 Release Planning Milestone.
...
| Deliverable Name | Deliverable Description | |
|---|---|---|
| To fill out | To fill outCSAR Validation upates | Support PM dictionary. |
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.
Please see the INFO.yaml files associated with each repo as the authoritative sources of information. https://gerrit.onap.org/r/admin/repos/q/filter:vnfsdk
Architecture
High level architecture diagram
...
Please fill out the centralized wiki page: Frankfurt Honolulu Release Platform Maturity
API Incoming Dependencies
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) |
|---|---|---|---|---|
| Upload API | API for vendors to upload VNF packages to marketplace | Defined in Amsterdam | Delivered in Amsterdam | API Documentation |
| Download API | API fro downloading VNF Package from Marketplace | Defined in Amsterdam | Delivered in Amsterdam | API Documentation |
| Query VNF information | API to query information on VNFs uploaded to the marketplace | Defined in Amsterdam | Delivered in Amsterdam | API Documentation |
| List Testsuite | List available test suties in a given scenario | Defined in Dublin | Delivered in Dublin | VTP REST API v1 |
| List Testcases | List available test cases | Defined in Dublin | Delivered in Dublin | VTP REST API v1 |
| Execute Testcases | execute the test cases | Defined in Dublin | Delivered in Dublin | VTP REST API v1 |
| List status | List the status in a given testcases | Defined in Dublin | Delivered in Dublin | VTP REST API v1 |
...
Testing and Integration Plans
Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.
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.
Verify the PM dictionary validation and Make sure the CSAR validation satifies the SOL requirments .
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.
| Gaps identified | Impact |
|---|---|
| To fill out | To fill out |
Known Defects and Issues
...
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 (bug) AND fixversion = "Honolulu Release" serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
Risks
List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).
Please update any risk on the centralized wiki page - Frankfurt Risks
- Release Deliverables
NO
Resources
Fill out the Resources Committed to the Release centralized page.Please see the INFO.yaml files associated with each repo as the authoritative sources of information. https://gerrit.onap.org/r/admin/repos/q/filter:vnfsdk
Release Milestone
The milestones are defined at the Release Level and Planning: Honolulu and all the supporting project agreed to comply with these dates.
...
Please update the following centralized wiki: Frankfurt Honolulu Documentation
That includes
- Team contributions to the specific document related to he project (Config guide, installation guide...).
- Team contributions to the overall Release Documentation and training asset
- High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
- Documentation includes items such as:
- Installation instructions
- Configuration instructions
- Developer guide
- End User guide
- Admin guide
- ...
...