...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Casablanca |
| Project Lifecycle State | Incubation |
| Participating Company | Huawei, AT&T, China Mobile, China TelcomTelecom, Orange, VMware, Wind River, Amdocs, ZTE, TechMahindra |
...
What is this release trying to address?
Based on the vFW / vDNS, vCPE and VoLTE use cases, this This project will provide cross-project system integration, CI/CD, and all related end-to-end release use cases testing with VNFs (approved by TSC) integration with VNFs, PNFs, SDN Controllers, s-VNFMs, etc. end to end maturity testing, necessary for the successful delivery and industry adaption of the ONAP project as a whole. The The same Amsterdam Beijing use cases with will be tested with more automation, 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.new use cases for Casablanca.
Optimizing the docker image build and deployment processes, the new sub-project approved by TSC:
- Docker images
- Docker image size optimization
- Docker best practice
- Docker architecture agnostic deployment to committed projects
- Leveraging cached docker image layers
Offline Deployment
CD / Clover integration
Use Cases
- vFW
- vDNS
- vCPE
- VoLTE
- CCVPN5G
- OSAM (Still need to talk to OSAM owner)
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.
...
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 2050 jqlQuery project="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 2050 jqlQuery project="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.
...
Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level, the targeted level for the current release and the evidences on how you plan to achieve the targeted level.
Since Integration project does not deliver code, the following will refer to the overall ONAP platform maturity level as measured by the Integration team S3P testing activities during the prior release.
| Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
|---|---|---|---|---|
| Performance |
| Not Measured |
| ||
| Stability |
| 2 | Integration team will perform platform-level testing similar to: |
| ||
| Resiliency |
| 2 | Integration team will perform platform-level testing similar to: |
| ||
| Security |
| Not Measured |
| ||
| Scalability |
| Not Measured |
| ||
| Manageability |
| Not Measured |
| ||
| Usability |
| Not Measured |
|
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.
...
The goal is to automate all the unit testing, CSIT testing, and end-to-end testing in release AmsterdamCasablanca. The detailed test roles and responsibilities are listed below.
Types of Testing | Dev. (Project Team) | CSIT (Project Team) | E2E (Integration Team) | S3P Team (Project + Integration) | |||
|---|---|---|---|---|---|---|---|
| Usability Testing | x | ||||||
| Unit Testing | x | ||||||
| Stability Testing | x | ||||||
| Security Testing | x | ||||||
| Scalability Testing | x | ||||||
| Regression Testing | xx | x | x | Recovering Testingx | x | ||
| Performance Testing | x | ||||||
| Integration/Pair-Wise Testing | x | ||||||
| Install/Uninstall Testing | x | ||||||
| Feature/Functional Testing | x | ||||||
| End-to-End Testing | x | ||||||
| Application Upgrade Testing (TBD) | 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.
...
| Risk identified | Mitigation Plan | Contingency Plan | ||
|---|---|---|---|---|
| To fill out | To fill out | To fill outNeed additional lab resources (RAM, disk, network bandwidth, etc.) | N/A | N/A |
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...