Feature Overview (mandatory - Complete while in New status)
An elevator pitch (value statement) that describes the Feature in a clear, concise way. ie: Executive Summary of the user goal or problem that is being solved, why does this matter to the user? The “What & Why”... 
Migrate the Conversion Host component of the Red Hat OpenStack VMware Migration Toolkit from its current CentOS 10 base to Red Hat Enterprise Linux (RHEL). This shift is crucial for enhancing the security, supportability, and enterprise-readiness of the migration solution. By adopting RHEL, customers can leverage their Red Hat subscriptions for the Conversion Host, ensuring it benefits from proactive security patching, guaranteed long-term support, and official Red Hat technical assistance, providing the necessary confidence and compliance for mission-critical migration projects.

Goals (mandatory - Complete while in New status)

Deliver a RHEL-based Conversion Host to provide customers with an officially supported, secure, and reproducible component for high-performance VM data transfer during migration from VMware vCenter to Red Hat OpenStack Services on OpenShift.

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

Current State: The Conversion Host is based on CentOS 10 (CentOS Stream 10), which is a community-driven, rolling release that tracks just ahead of RHEL development. It does not include the official Red Hat security, support, and certification guarantees associated with a paid RHEL subscription.

Future State: The Conversion Host will be based on RHEL (e.g., RHEL 9 or RHEL 10 base, depending on alignment).
 
Requirements (mandatory -_ Complete while in Refinement status):

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

• A user can successfully deploy the RHEL-based Conversion Host VM using the Red Hat OpenStack VMware Migration Toolkit or manually.

• The deployed Conversion Host VM is verifiably running a supported version of Red Hat Enterprise Linux and is registered to the Red Hat subscription system (or Satellite/Insights).

• A complete Warm migration of an end-to-end workload (including multi-disk and multi-NIC configurations) from a supported VMware vCenter environment to Red Hat OpenStack Services on OpenShift completes successfully using the RHEL-based Conversion Host.

• The migration log confirms that the Conversion Host received security and other package updates via the Red Hat content delivery network (or customer's Satellite) during its lifecycle.

• All mandatory virt-v2v and Migration toolkit packages are installed and functional on the RHEL-based host.

Use Cases - i.e. User Experience & Workflow: (Initial completion while in Refinement status):
Include use case diagrams, main success scenarios, alternative flow scenarios.
<your text here>

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):

• Update Prerequisites: Clearly state that the RHEL-based Conversion Host requires an active RHEL subscription/entitlement provided by RHOSO subscription.

• Registration Steps: Document the process for providing RHSM or Satellite credentials to the Ansible collection for automated registration.

• Compatibility Matrix: Update the OS compatibility matrix for the Conversion Host to explicitly list the supported RHEL version(s).

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

• Which specific RHEL major version (e.g., RHEL 9 or RHEL 10) will be the base for the Conversion Host? This choice will dictate the underlying package versions and support timeline.

• Is there any cost implication for customers based on how the host is deployed (e.g., using existing RHEL OpenStack entitlements)?

•  What is the plan for image maintenance/patching outside of the initial deployment?

• Should the Ansible playbook support both RHSM and Satellite registration methods, or just one initially (MVP)?

Background and Strategic Fit (Initial completion while in Refinement status):
This feature aligns with Red Hat's strategy to move all critical tooling and components onto its flagship enterprise operating system, Red Hat Enterprise Linux. The use of CentOS Stream as a foundational OS for key components is being phased out in favor of RHEL to ensure a unified and fully-supported experience for enterprise customers. By standardizing on RHEL, we strengthen the end-to-end support model for the entire migration solution, mitigating the risks associated with non-commercial, community-supported distributions in a high-stakes, data-intensive operation like a mass VM migration.

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

• Subscription Usage: Customers will need to ensure they have available RHEL/RHOSO subscriptions to cover the newly deployed Conversion Host VM(s). This should be explicitly communicated.

• Network Requirements: Customers need to confirm that the RHEL-based Conversion Host has network access to Red Hat Subscription Management (RHSM) or their internal Red Hat Satellite server for successful registration and updates. This is a common enterprise network consideration that must be verified.

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

• …