Feature Request Overview (mandatory - Complete while in New status){_}

Customers using Red Hat OpenStack versions that are End-of-Life (EOL) or in Extended Life-cycle Support (ELS) need a reliable, supported solution to migrate their workloads to the latest platform, Red Hat OpenStack Services on OpenShift. This feature aims to provide a tool that automates and orchestrates this migration.

Business justification (mandatory - Complete while in New status)

This feature provides a fully supported, productised solution for parallel cloud migrations. By leveraging the os-migrate tool, customers can perform parallel migrations, significantly reducing downtime and risk.

This ensures continued access to new features, security patches, and official Red Hat support, which is critical for maintaining a stable and secure infrastructure. It also reduces the operational burden on customers by automating complex migration tasks.

Functional requirements (mandatory - Complete while in New status){_}

The tool must support parallel migration of OpenStack resources.

These are the foundational services and their data that must be migrated for any OpenStack workload.

• Compute (Nova):
  • Instances (VMs)
  • Flavors
  • Instance Metadata
• Networking (Neutron):
  • Networks and Subnets
  • Routers
  • Security Groups
  • Ports including ports with binding:vnic_type set to direct
• Block Storage (Cinder):
  • Volumes
  • Snapshots
• Image Service (Glance):
  • VM Images
• Identity (Keystone):
  • Users
  • Roles
  • Projects (Tenants)

The tool must be able to migrate from Red Hat OpenStack 13 and 16.2 to the latest version of Red Hat OpenStack Services on OpenShift.

The tool should include pre-migration validation checks to ensure source and destination environments are compatible.

The solution must be fully documented and supported by Red Hat.

Describe the customer impact

IMPORTANT: Do not include customer names.

• Provide links to the account project
• Provide links to any related support tickets (open or closed)

For details on connecting Jira issues to an account, see Connecting Jira Issues to Accounts.

(Optional) Point of contact

• Provide any additional points of contact for this feature request, such as an account executive, SA, or TAM:

(Optional) Additional links

Click More > Link to add any links to issues, such as an outcome, that are related to this feature request.

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”... 
<your text here>

Goals (mandatory - Complete while in New status)
Provide high-level goal statement, providing user context and expected user outcome(s) for this Feature

• Who benefits from this Feature, and how? 
• What is the difference between today’s current state and a world with this Feature?
  <your text here>

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):
Acceptance Criteria articulates and defines the value proposition - what is required to meet the goal and intent of this Feature. The Acceptance Criteria provides a detailed definition of scope and the expected outcomes - from a users point of view
…
<your text here>
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):
Provide information that needs to be considered and planned so that documentation will meet customer needs. If the feature extends existing functionality, provide a link to its current documentation..
<your text here>
 
Questions to Answer _ _(Initial completion while in Refinement status):
Include a list of refinement / architectural questions that may need to be answered before coding can begin.
<your text here>
Background and Strategic Fit (Initial completion while in Refinement status):
Provide any additional context is needed to frame the feature.
<your text here>
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

  Reviewed By	Team Name	Accepted	Notes