Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject="INT" and issuetype in (epic) and status != done
serverId425b2b0a-557c-3c0c-b515-579789cceedb

...

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject=sanbox "int" and issuetype in (story) and status != done
serverId425b2b0a-557c-3c0c-b515-579789cceedb

...

Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.

...

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, ...).

NameDescriptionVersion
RobotTesting framework
JenkinsCI/CD tool
OpenstackCloud OS

Docker

Container platform
JMeterPerformance Testing tool
Chaos MonkeyResilience Testing tool

In case there are specific dependencies  (Centos 7 vs Ubuntu 16. Etc.) list them as well.

...

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 Testingx


Unit Testingx


Stability Testing


x
Security Testing


x
Scalability Testing


x
Regression Testingxxxx
Recovering Testing

xx
Performance Testing


x
Integration/Pair-Wise Testing
x

Install/Uninstall Testingx


Feature/Functional Testingx


End-to-End Testing

x
Application Testingx


Acceptance Testing
xx

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 identifiedMitigation PlanContingency Plan
To fill outTo fill outTo fill out

Resources

Fill out the Resources Committed to the Release centralized page.

Release Milestone

...