Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.xloud.tech/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

After reviewing and approving an action plan, you execute it to trigger the live migrations. Actions execute sequentially in priority order — each migration must complete before the next begins. Live migrations are non-disruptive for running instances: the workload continues serving requests while its memory state is transferred to the destination host. Plan execution can be cancelled at any time — in-progress migrations complete, pending actions are halted.
Prerequisites
  • An action plan in RECOMMENDED or PENDING state
  • All compute hosts with sufficient capacity to accept migrating instances
  • Shared storage (Xloud Distributed Storage) for all instances in the plan

​
Execute an Action Plan

Open the action plan

Navigate to Optimization → Action Plans and click the plan name.

Start the action plan

If the plan state is RECOMMENDED, click Start first.

Execute

Click Start. The plan state transitions to ONGOING.Action statuses update in real time:
StatusMeaning
PENDINGAction queued
ONGOINGMigration in progress
SUCCEEDEDAction completed
FAILEDAction failed — execution halts
CANCELLEDExecution cancelled before this action ran

Monitor completion

Watch the action list update as each migration completes. The plan state changes to SUCCEEDED when all actions finish.
Plan state is SUCCEEDED and all actions show SUCCEEDED.

​
Verify Post-Execution Placement

After execution, verify that instances have been redistributed as expected.
Navigate to Compute > Hypervisors (admin view) to view the updated host utilization. Compare the host instance counts and resource utilization before and after execution.
Previously underutilized hosts now show reduced instance counts.

​
Cancel Execution Mid-Plan

If a plan needs to be stopped after execution has started:
On the action plan detail page, click Cancel. The in-progress migration completes; all pending actions are marked CANCELLED.
After cancellation, run a new audit to generate an updated action plan that reflects the current (partially optimized) cluster state.

​
Next Steps

Audit History

Review the completed audit and its execution results over time.

Action Plans

Review the action plan detail and individual action outcomes.

Troubleshooting

Resolve failed actions and migration errors.

Run an Audit

Run another audit to continue optimization after the current plan completes.