live wire
▸PLATFORM · Clang 23 bytecode interpreter cuts allocations and expands constant-expression supportRed Hat Developer▸PLATFORM · RHEL becomes first-party on OCI; OpenShift subscriptions reach Oracle MarketplaceRed Hat▸AI · vLLM-Omni merges native MOSS-Image serving with parallelism and offloadvLLM▸AI · vLLM adds System One endpoint for Decision 3.0 multimodal routing models (Oct. 15)vLLM▸SECURITY · Red Hat rates OpenShift AI 3.4.5 update Critical; advisory lists hundreds of CVEsRed Hat Product Security▸SECURITY · Red Hat’s first Security Signals report shifts focus from CVE counts to risk paths (Oct. 15)Red Hat▸PLATFORM · IBM adds non-destructive FlexVolume-to-CSI migration tool for OpenShift object storageIBM Cloud▸vLLM tests agent-built Kimi K3 decode path at up to 1.9× speedup; PR remains openvLLM▸AI · LeaderWorkerSet 1.0 changes rollout defaults for disaggregated AI workloadsKubernetes SIGs▸SECURITY · Red Hat flags active exploitation of kernel flaw affecting OpenShift CoreOS; no fix listedRed Hat Product Security▸AI · Red Hat sets Dec. 9 showcase for AI 3.6 agent governance and model servicesRed Hat▸vLLM 0.32.0 drops Python 3.10, restricts CORS defaults and adds security fixesvLLM▸SECURITY · Red Hat tracks Moderate Hono auth bypass across OpenShift AI, Dev Spaces and AnsibleRed Hat Product Security▸SECURITY · Red Hat Hardened Images fixes Moderate libpng denial-of-service flawRed Hat▸PLATFORM · Clang 23 bytecode interpreter cuts allocations and expands constant-expression supportRed Hat Developer▸PLATFORM · RHEL becomes first-party on OCI; OpenShift subscriptions reach Oracle MarketplaceRed Hat▸AI · vLLM-Omni merges native MOSS-Image serving with parallelism and offloadvLLM▸AI · vLLM adds System One endpoint for Decision 3.0 multimodal routing models (Oct. 15)vLLM▸SECURITY · Red Hat rates OpenShift AI 3.4.5 update Critical; advisory lists hundreds of CVEsRed Hat Product Security▸SECURITY · Red Hat’s first Security Signals report shifts focus from CVE counts to risk paths (Oct. 15)Red Hat▸PLATFORM · IBM adds non-destructive FlexVolume-to-CSI migration tool for OpenShift object storageIBM Cloud▸vLLM tests agent-built Kimi K3 decode path at up to 1.9× speedup; PR remains openvLLM▸AI · LeaderWorkerSet 1.0 changes rollout defaults for disaggregated AI workloadsKubernetes SIGs▸SECURITY · Red Hat flags active exploitation of kernel flaw affecting OpenShift CoreOS; no fix listedRed Hat Product Security▸AI · Red Hat sets Dec. 9 showcase for AI 3.6 agent governance and model servicesRed Hat▸vLLM 0.32.0 drops Python 3.10, restricts CORS defaults and adds security fixesvLLM▸SECURITY · Red Hat tracks Moderate Hono auth bypass across OpenShift AI, Dev Spaces and AnsibleRed Hat Product Security▸SECURITY · Red Hat Hardened Images fixes Moderate libpng denial-of-service flawRed Hat
upstreambeat.ai
analysisPLATFORM

Red Hat maps two live-migration paths into OpenStack Services on OpenShift

A first-party migration toolkit uses Ansible and changed-block tracking, while certified partner Hystax targets agentless moves at larger scale.

Two migration paths into OpenShift: Ansible toolkit and agentless Hystax replication.
Side by side: what changed
By The News Desk· Oct 1, 2026the quick take — two AI hosts go live when you do

Red Hat has set out two routes for moving virtual machines into Red Hat OpenStack Services on OpenShift: its own Ansible-based migration toolkit and a certified partner path from Hystax aimed at large, agentless migrations.

The distinction matters for platform teams planning exits from VMware or older OpenStack estates. Red Hat’s September 30 overview positions the native toolkit as a repeatable migration workflow for live VMs, while Hystax Acura fills what Red Hat describes as an agentless, incremental-replication gap for high-volume projects.

What the Red Hat toolkit automates

The first-party toolkit is delivered as an Ansible collection. Red Hat’s technical deep dive says it discovers VM, network and storage metadata from VMware vCenter; maps networks and hardware profiles to OpenStack; supports multiple disks and network interfaces; and can perform warm migrations with VMware snapshots and changed-block tracking.

Its workflow deploys a RHEL-based conversion host in the target cloud, provisions and attaches a Cinder volume, then transfers disk data directly from VMware through that conversion host. Before cutover, the toolkit checks for changed blocks and synchronizes only the delta. Nova, Cinder and Neutron then provide compute, storage and networking for the recreated VM.

That architecture keeps bulk data away from the host running the Ansible playbook. Teams can run the collection from a standalone migrator or through Red Hat Ansible Automation Platform for centralized orchestration, validation and post-migration workflows.

Where Hystax fits

For migrations that require agentless replication or very large daily waves, Red Hat points users to Hystax Acura. The September post says the partner product performs incremental replication in the background while source systems remain live, reducing the final maintenance window. It also adds continuous replication, disaster-recovery functions and ransomware detection.

Red Hat cites three deployment examples: a payroll company moving 9,000 Windows and Linux VMs, a cybersecurity provider moving more than 10,000 VMs in daily waves, and a telecommunications operator using the same platform for migration, backup and disaster recovery. The post does not name those customers or provide independent case-study links, so readers should treat the scale figures as vendor-supplied claims rather than audited benchmarks.

The decision for platform teams

The native collection offers a transparent Ansible workflow and direct integration with OpenStack APIs. Hystax adds an external replication layer when agentless operation and continuous protection are requirements. Before choosing, teams should validate guest support, network and flavor mappings, snapshot capacity, recovery objectives and the operational ownership of the conversion or replication infrastructure.

The practical takeaway is not a one-click migration promise. Red Hat now documents a concrete warm-migration mechanism and a partner option for larger estates, giving platform teams two architectures to test against their downtime and automation constraints.

sources

Filed by The News Desk. Corrections: desk@upstreambeat.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.

    more from the desk