Introduction

This testing plan outlines the strategy for ensuring the quality of UDN features within OpenShift Virtualization. Our focus is on UDN's integration within CNV. specifically on the integration aspects and new capabilities specific to the virtualization context, avoiding duplication of efforts with the OpenShift SDN team's testing.

Scope

• Testing of UDN functionality within CNV.
• Integration with existing virtualization features.
• Coordination with the performance team for performance and scalability testing.
• Coordination with the OpenShift SDN team to ensure comprehensive coverage

Test Objectives

• Verify UDN functionality for VMs in OpenShift.
• Ensure compatibility with existing CNV features.
• Validate new UDN capabilities specific to virtualized environments
• Coordinate with the performance team to assess performance and scalability aspects.
• Coordinate with the OpenShift SDN team to identify and address any testing gaps.

Test Strategy

Integration & Functional Testing

• VM creation and connection to UDNs (for example, East-Wast traffic, Ingress Egress, IPAM for primary NIC only)
• Interaction between UDNs and CNV.
• Compatibility with existing VM networking features
• Specific UDN features added for virtualization scenarios
• Any virtualization-specific network isolation or security enhancements

Performance and Scalability Testing

In coordination with the Performance Team

• Support the performance team in defining test scenarios for:
  • Network throughput for VMs on UDNs.
  • Scalability testing (number of VMs per UDN, number of UDNs per cluster).

Coordination with OpenShift SDN Team

• Regular communication to align on testing coverage
• Identification of potential gaps in testing between teams
• Collaboration on test cases that span both domains

Test Environment

• most work can begin with a virtualized environment (like PSI or AWS).
• must be validated on multi-node BM clusters and SNO.
• Various VM configurations and workloads.

Test Automation

• Extend cnv-tests to cover UDN scenarios.

Risks and Mitigations

• Complexity of networking in virtualized environments
• Potential performance impact on VMs
• Integration challenges with existing features
• Significant delays due to the discovery of critical bugs.
  • Mitigation: Align with the development team on expectations and maintain continuous testing and automation with clear integration plans.

Timeline

• 4.17.0 Aim for tech. preview
  • Week 1-2: Test plan refinement and initial test case development
  • Week 3-6: Core functional testing and initial automation development
  • Week 7-8: Integration testing and Tech Preview readiness assessment
• 4.18.0 Aim for GA
  • Week 9-12: Extended functional testing and automation expansion
  • Week 13-14: Comprehensive integration testing
  • Week 15-16: Final testing, bug fixes, and GA readiness assessment

Note: 3 engineers with 60% capacity allocated throughout the entire effort.

Team Responsibilities

• Test design, execution, and automation
• Bug verification and regression testing
• Collaboration with development for issue resolution
• Regular progress updates and SoS meeting participation
• Coordination with the OpenShift SDN team and performance team

Coordination with OpenShift SDN Team

• Schedule regular sync meetings with the OpenShift SDN team
• Share test plans and results to identify any gaps in coverage
• Collaborate on test cases that span both virtualization and core SDN functionality
• Maintain open communication channels for quick resolution of cross-team issues