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
RECOMMENDEDorPENDINGstate - 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
- Dashboard
- CLI
Execute
Click Execute. The plan state transitions to
ONGOING.Action statuses update in real time:| Status | Meaning |
|---|---|
PENDING | Action queued |
ONGOING | Migration in progress |
SUCCEEDED | Action completed |
FAILED | Action failed — execution halts |
CANCELLED | Execution cancelled before this action ran |
Verify Post-Execution Placement
After execution, verify that instances have been redistributed as expected.- Dashboard
- CLI
Navigate to Admin → Compute → Hypervisors 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:- Dashboard
- CLI
On the action plan detail page, click Cancel. The in-progress migration
completes; all pending actions are marked
CANCELLED.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.