The requirement is for a self-service solution allowing users to migrate their own workloads using
VMware vMotion within a VMware Cloud Foundation (VCF) 5.2 environment. vMotion is a vSphere
feature that enables live migration of virtual machines (VMs) between ESXi hosts with no downtime,
typically managed by administrators via vCenter. A self-service solution implies empowering end
users (e.g., application owners) to initiate this process through a user-friendly interface or
automation tool. Let’s evaluate each component:
Option A: Aria Suite Lifecycle Manager
Aria Suite Lifecycle Manager (LCM) is responsible for deploying, upgrading, and managing the
lifecycle of VMware Aria Suite components (e.g., Aria Automation, Aria Operations). It does not
provide self-service capabilities or direct interaction with vMotion. The VMware Aria Suite Lifecycle
Administration Guide confirms its role is administrative, not end-user-facing, making it unsuitable for
this requirement.
Option B: Aria Automation Orchestrator
Aria Automation Orchestrator (formerly vRealize Orchestrator) is a workflow automation engine
integrated with Aria Automation in VCF 5.2. It allows the creation of custom workflows, including
vMotion operations, which can be exposed to users via the Aria Automation self-service portal. The
VMware Aria Automation Orchestrator Administration Guide details how workflows can call vSphere
APIs (e.g., RelocateVM_Task) to initiate vMotion, enabling users to trigger migrations without direct
vCenter access. In VCF, this integrates with SDDC Manager and vCenter, satisfying the self-service
requirement by providing a customizable, user-accessible automation layer.
Option C: Aria Operations
Aria Operations (formerly vRealize Operations) is a monitoring and analytics tool for performance,
capacity, and health of VCF components. It provides dashboards and insights but has no capability to
execute vMotion or offer self-service workload management. The VMware Aria Operations
Administration Guide confirms its focus is observability, not automation or user interaction, ruling it
out.
Option D: Aria Automation Config
Aria Automation Config (formerly SaltStack Config) is a configuration management tool for
automating infrastructure and application states (e.g., patching, compliance). It lacks native vMotion
integration or a self-service portal for workload migration. The VMware Aria Automation Config User
Guide focuses on configuration tasks, not VM migration, making it irrelevant here.
Conclusion:
Aria Automation Orchestrator (B) is the best fit. It enables the architect to design workflows for
vMotion, integrated with Aria Automation’s self-service portal, meeting the requirement for user-
driven workload migration in VCF 5.2.
Reference:
VMware Cloud Foundation 5.2 Architectural Guide (docs.vmware.com): Section on Aria Suite
Integration and Automation.
VMware Aria Automation Orchestrator Administration Guide (docs.vmware.com): Workflow Creation
for vSphere Actions (vMotion).
VMware Aria Suite Lifecycle Administration Guide (docs.vmware.com): LCM Capabilities.
VMware Aria Operations Administration Guide (docs.vmware.com): Monitoring Scope.
