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.