...
What is this release trying to address?
Based on the vFW / vDNS, vCPE and VoLTE use cases, this project will provide cross-project system integration, CI/CD, and all related end-to-end release use cases testing with VNFs necessary for the successful delivery and industry adaption of the ONAP project as a whole. The same Amsterdam use cases with be tested with more automation and , with additional emphasis on platform stability and performance, and the three new functionalities (CM, Auto scaling, HPA). In addition, ensure the platform is stable as installed and deployed via OOM, if viable.
...
No new use cases. Instead the same use cases as Amsterdam will be tested using more automation and with additional emphasis on platform stability and performance. Test that the same use cases still work when ONAP is deployed via OOM.
- vFW
- vDNS
- vCPE
- VoLTE
Minimum Viable Product
- CI/CD
- Automatic unit testing, CSIT testing, and end-to-end testing
- Guidelines, frameworks, or best practice recommendations on S3P testing for ONAP project teams.
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 "INT" and issuetype in (epic) and status != done 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 "int" and issuetype in (story) and status != done serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
...
- Cross-project Continuous System Integration Testing (CSIT)
- End-to-End (ETE) release use cases testing with VNFs with repeatability
- Service design for end-to-end release use cases
- Continuous Distribution (CD) to ONAP community integration labs
- Reference VNFs that can be used to show how the ONAP platform handles
- VNF installation and
- VNF life cycle management
- VNF Requirement compliance
Release Deliverables
...
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
| Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
|---|---|---|---|---|
| Performance | N/A |
| ||
| Stability | N/A |
| ||
| Resiliency | N/A |
| ||
| Security | N/A |
| ||
| Scalability | N/A |
| ||
| Manageability | N/A |
| ||
| Usability | N/A |
|
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) |
|---|---|---|---|---|
| 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 |
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 |
Third Party Products Dependencies
Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).
| Name | Description | Version | To fill out | To fill out | To fill out|
|---|---|---|---|---|---|
| Robot | Testing framework | ||||
| Jenkins | CI/CD tool | ||||
| Openstack | Cloud OS | ||||
Docker | Container platform | ||||
| JMeter | Performance Testing tool | ||||
| Chaos Monkey | Resilience Testing tool |
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
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.
The goal is to automate all the unit testing, CSIT testing, and end-to-end testing in release Amsterdam. The detailed test roles and responsibilities are listed below.
Types of Testing | Dev. Team | CSIT Team | E2E Team | S3P Team |
|---|---|---|---|---|
| Usability Testing | x | |||
| Unit Testing | x | |||
| Stability Testing | x | |||
| Security Testing | x | |||
| Scalability Testing | x | |||
| Regression Testing | x | x | x | x |
| Recovering Testing | x | x | ||
| Performance Testing | x | |||
| Integration/Pair-Wise Testing | x | |||
| Install/Uninstall Testing | x | |||
| Feature/Functional Testing | x | |||
| End-to-End Testing | x | |||
| Application Testing | x | |||
| Acceptance Testing | x | x |
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
Provide a link toward the list of all known project bugs.
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
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).
| 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
The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.
Team Internal Milestone
This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is erecommended to provide these agreements and dates in this section.
...
| Date | Project | Deliverable |
|---|---|---|
| To fill out | To fill out | To fill out |
Documentation, Training
- Highlight the team contributions to the specific document related to he project (Config guide, installation guide...).
- Highlight the 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
- ...
...