Summary

This document outlines the testing strategy for Advanced Cluster Management (ACM) Quality Engineering (QE) regarding live migration capabilities in the CNV integration tech preview for ACM 2.15. Based on coordination with Installer QE (msmigiel) and ACM Addon team (Nathaniel Graham), this strategy focuses specifically on end-to-end live migration functionality and ACM console integration.

Primary Objective: Validate cross-cluster VM live migration between managed clusters via ACM console, ensuring reliable migration workflows and proper integration with ACM's multi-cluster management capabilities.

1. Testing Scope and Responsibilities

Based on coordination with Installer QE (msmigiel) and ACM Addon team (Nathaniel Graham), responsibilities are clearly delineated:

ACM QE Live Migration Testing Responsibilities

Primary Focus: End-to-end live migration functionality and ACM console integration

1. Addon Lifecycle and Template Validation (ACM Perspective)

• Simple validation of MTV addon functionality within ACM pages
• Integration testing of MTV addon with ACM console workflows
• Cross-cluster template application verification for migration scenarios

2. End-to-End Live Migration Functionality (ACM-13311)

• Primary Responsibility: Full user workflow testing for VM live migration between clusters
• Source to Destination: Migration from hub to RHOV spoke clusters via ACM console
• Workflow Validation: Complete process from UI action to successful migration completion
• MTV Orchestra Integration: Verify that Migration Toolkit for Virtualization successfully orchestrates migrations
• Cross-Cluster Action Dispatching: Ensure requests from ACM console are correctly dispatched to MTV

Installer QE Responsibilities (Covered by Matthew Smigielski's team)

• MTV Addon Installation/Uninstallation: Standard addon lifecycle testing
• Operator Health Validation: MTV operator CSV status and health checks
• Upgrade Scenarios: Future upgrade testing for MTV addon
• Template Deployment: Basic template application to managed clusters
• Standard Install Testing: All foundational installation and deployment aspects

CNV QE Collaboration

• Scope: Virtualization-specific migration testing on individual clusters
• UI Testing: CNV team handles virtualization UI testing (separate from ACM console)
• Coordination: Joint validation of end-to-end migration flows
• Tracking: Epic CNV-66464

2. Live Migration Testing Strategy

2.1 Migration Toolkit for Virtualization (MTV) Integration

JIRA: ACM-22348 - "Onboard CNV addon and MTV-integrations into ACM Installer"
Scope Clarification: Based on coordination with Installer QE (msmigiel), ACM QE focuses on functional testing while Installer QE handles installation/deployment

ACM QE Scope: MTV Functional Integration Testing

• Objective: Validate MTV integration with ACM console and migration functionality
• Test Areas:
  • Simple MTV Addon Validation: Basic functionality verification within ACM pages
  • Migration Plan Creation: Test creating VM migration plans through ACM interface
  • Cross-Cluster Migration Execution: Validate migration orchestration via ACM console
  • Migration Status Monitoring: Real-time progress tracking through ACM UI
  • Post-Migration Validation: VM functionality verification after migration completion

End-to-End Live Migration Workflow (ACM-13311)

• Primary ACM QE Responsibility: Complete user workflow from ACM console to successful migration
• Test Areas:
  • UI to MTV Integration: Verify ACM console actions correctly trigger MTV operations
  • Cross-Cluster Action Dispatching: Ensure migration requests route correctly to target clusters
  • MTV Orchestration Validation: Confirm MTV successfully completes cluster-to-cluster migrations
  • Migration Error Handling: Test failure scenarios and error reporting through ACM console
  • Source to RHOV Spoke: Specific testing of hub-to-spoke migration scenarios

Note: Installer QE (msmigiel's team) handles MTV addon installation, uninstallation, operator health, and upgrade scenarios as part of standard install testing.

2.2 VNC Console During Migration

JIRA: ACM-14983 - "Transition users of Virtual Machine list to CNV with multicluster support"

Migration Console Access

• Test Areas:
  • Verify VNC console access during live migration process
  • Test console connectivity maintenance during cluster transition
  • Validate console session handling post-migration
  • Test console access failure scenarios during migration

3. Migration Testing Environment

Environment Configuration

The live migration testing environment consists of:

• Hub Cluster: ACM hub managing multiple clusters with MTV integration
• Source Clusters: Clusters hosting VMs for migration
• Target Clusters: RHOV spoke clusters as destination for migration scenarios
• Network Configuration: Cross-cluster connectivity for migration traffic

Migration-Specific Prerequisites

• Network Connectivity: Dedicated migration network paths between clusters
• Storage Compatibility: Shared or compatible storage classes for VM migration
• Resource Capacity: Adequate compute and storage on target clusters
• MTV Operator: Deployed for migration orchestration (handled by Installer QE)
• CNV Operator: Installed on all participating clusters

4. Live Migration Test Scenarios

4.1 Basic Migration Scenarios

• Single VM Migration: Migrate individual VMs between clusters via ACM console
• VM State Preservation: Ensure running state maintenance during migration
• Network Connectivity: Validate network access post-migration
• Storage Migration: Test persistent volume migration with VMs

4.2 Advanced Migration Scenarios

• Bulk Migration: Migrate multiple VMs simultaneously through ACM
• Hub to RHOV Spoke: Specific migration testing to RHOV spoke clusters
• Resource Constraint Migration: Migration with limited target resources
• Failed Migration Recovery: Rollback and retry scenarios via ACM console

5. Success Criteria for Live Migration

Functional Success

• All VM migration operations complete successfully via ACM console
• Post-migration VMs retain full functionality and network connectivity
• Migration status accurately reflects real-time progress through ACM UI
• Failed migrations can be properly rolled back via ACM console

Integration Success

• ACM console provides comprehensive migration management
• Cross-cluster migration actions route correctly to MTV
• VNC console access maintains connectivity during migration
• Migration workflows integrate properly with ACM RBAC