...
| 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.We will also make progress toward optimizing 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
- CCVPN (TBD?)
- OSAM (TBD?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.
...
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
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 (Project + Integration) | |||
|---|---|---|---|---|---|---|---|
| Usability Testing | x | ||||||
| Unit Testing | x | ||||||
| Stability Testing | x | ||||||
| Security Testing | x | ||||||
| Scalability Testing | x | ||||||
| Regression Testing | x | xx | 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 Testing | |||||
| x | Acceptance TestingUpgrade Testing (TBD) | 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 |
|---|---|---|
| Need 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
...