Feature Overview (mandatory - Complete while in New status)

Migrate the base operating system for the Red Hat OpenStack VMware Migration Toolkit's Ansible Execution Environment (AEE) from CentOS Stream 10 to Red Hat Enterprise Linux (RHEL). This transition is essential to improve security, stability, and reproducibility by leveraging the RHEL ecosystem. By using a RHEL-based AEE, customers using Ansible Automation Platform (AAP) gain assurance that the core orchestration engine is built on a fully supported, compliant, and enterprise-grade base, thereby enhancing the reliability and maintainability of large-scale migration workflows.

Goals (mandatory - Complete while in New status)

Deliver a RHEL-based Ansible Execution Environment for the Red Hat OpenStack VMware Migration Toolkit to ensure the orchestration layer (Ansible) is secure, stable, and fully supported, maximizing the reliability and compliance of automated migration at scale using Ansible Automation Platform.

What is the difference between today’s current state and a world with this Feature?

Current State: The Ansible Execution Environment (AEE) is built on CentOS Stream 10, a community-driven, continuously delivered distribution that tracks ahead of RHEL. It lacks the official, enterprise-level security assurance, bug fix SLAs, and long-term support provided by a RHEL subscription.

Future State: The AEE will be built on a RHEL base image. This ensures official Red Hat support and security patches are available for the operating system components of the execution environment, aligning the entire migration solution with enterprise support and security policies.

Requirements (mandatory -_ Complete while in Refinement status):
A list of specific needs, capabilities, or objectives that a Feature must deliver to satisfy the Feature. Some requirements will be flagged as MVP. If an MVP gets shifted, the Feature shifts. If a non MVP requirement slips, it does not shift the feature.

Done - Acceptance Criteria (mandatory - Complete while in Refinement status):

• A Red Hat engineer or building process can successfully build the new Ansible Execution Environment using a published RHEL base image.

• The final AEE image passes an inspection check verifying that the base OS is RHEL (e.g., checks against OS-release files).

• The RHEL-based AEE is imported into a customer's Ansible Automation Platform (AAP) instance.

• A full end-to-end warm migration playbook run—executed as an AAP job using the new RHEL-based AEE—completes successfully, performing discovery, mapping, and VM conversion/provisioning.

• All required Python and OS dependencies within the RHEL-based AEE are verified to be the supported and certified versions needed for the Ansible collection.

Use Cases - i.e. User Experience & Workflow: (Initial completion while in Refinement status):
Include use case diagrams, main success scenarios, alternative flow scenarios.
1. The Migration Administrator logs into Ansible Automation Platform (AAP).

2. The Administrator selects the Migration Toolkit job template, which is configured to use the new RHEL-based Execution Environment.

3. The job launches, and the playbooks execute within the RHEL environment.

4. The migration completes, benefiting from the known stability and security of the RHEL base, reducing concerns about environment-related issues.

Out of Scope __(Initial completion while in Refinement status):
High-level list of items or persona’s that are out of scope.
<your text here>

Documentation Considerations __(Initial completion while in Refinement status):

• Execution Environment Specification: Update the documentation to clearly state that the AEE is now based on RHEL, listing the specific base image URL to use during the import of the AEE into AAP.

Questions to Answer __(Initial completion while in Refinement status):

• Which specific RHEL base image (e.g., RHEL 8 or RHEL 9 runner) will be used to build the AEE, and is this image officially certified for the current supported version of Ansible Automation Platform?

• Are all required Ansible Collections and their Python dependencies available and supported on the chosen RHEL major version?

• What is the source of the RHEL base image for the automated build pipeline (e.g., private registry, Red Hat registry), and does the build environment have the necessary authentication/entitlements to access it?

Background and Strategic Fit (Initial completion while in Refinement status):

This feature is a direct strategic fit with Red Hat’s mandate to move core product components away from community-supported upstream projects (like CentOS Stream) toward the fully supported, secure, and commercially viable RHEL platform. This aligns the core orchestration layer of a critical migration tool with enterprise standards, ensuring a uniform support experience across all layers of the Red Hat solution stack—from the AEE orchestrating the move to the Conversion Host executing the transfer and finally to Red Hat OpenStack Services on OpenShift.

Customer Considerations __(Initial completion while in Refinement status):
Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.
<your text here>

Team Sign Off (Completion while in Planning status)

• All required Epics (known at the time) are linked to the this Feature
• All required Stories, Tasks (known at the time) for the most immediate Epics have been created and estimated
• Add - Reviewers name, Team Name
• Acceptance == Feature as “Ready” - well understood and scope is clear - Acceptance Criteria (scope) is elaborated, well defined, and understood
• Note: Only set FixVersion/s: on a Feature if the delivery team agrees they have the capacity and have committed that capability for that milestone

• …