Epic Goal:

To ensure the performance and scalability of OADP v1.5 by conducting thorough testing across various components, including RESTIC Backup, DPA, Self Service Support, Podified DataMover, Ceph Shallow Copy, and STS.

Why is this important?

The upcoming OADP v1.5 release introduces significant improvements in performance, scalability, and reliability. Thorough testing is crucial to identify potential bottlenecks, ensure a seamless user experience, and prevent any unexpected issues that might impact the stability of our platform.

Scenarios

• * High-traffic scenarios:
  + <TBD> nodes with concurrent backup operations
  + <TBD> pods with data mover operations
  + <TBD> users accessing self-service support
• Low-performance scenarios:
  + Disabled FSB (no escalated privileges) on a single node
  + Large-scale Ceph Shallow Copy operations
  + STS-related issues due to concurrent authentication requests
• Edge cases:
  + ImageStream-related performance testing
  + Kopia Maintenance and OLMV1 compatibility testing

Dependencies (internal and external)

• RESTIC Backup OADP-5158
• DPA.Velero.args OADP-3391
• OCP 4.19 requirements OADP-5031 and OADP-5105
• Ceph Shallow Copy OADP-4696
• DataUploader Speed Test OADP-1558
• STS-related RFEs OADP-4735, OADP-5096, OADP-3340, and OADP-2319

User Stories:

As a Performance Engineer, I want to thoroughly test OADP v1.5 across various scenarios to ensure its stability, performance, and scalability so that users can expect a seamless experience with minimal downtime or performance issues.

Acceptance Criteria: (Definition of Done)

• All high-traffic scenarios pass without any notable performance degradation.
• All low-performance scenarios meet their respective performance targets.
• Edge cases are handled correctly and don't cause any unexpected behavior
• STS-related issues are resolved, and concurrent authentication requests are completed successfully.
• ImageStream support is optimized for performance.
• Kopia Maintenance and OLMV1 compatibility are tested successfully.

Verify that:

• Test results are recorded and analyzed to identify any potential issues
• The team thoroughly reviews test results, identifies areas for improvement, and prioritizes fixes accordingly.
• The team provides regular updates on the testing progress and status.
• Automation covers all regression and new tests.