Nutanix Move¶
Clarity Transform drives Nutanix Move to migrate workloads onto the Nutanix platform: reading providers, plans and readiness, and creating, starting and cancelling migration plans from Execute → Migration Operations → Migration Jobs.
Where to find it¶
Go to Discover → Integrations, then select the Nutanix Move card. The card's category label is Migration. The integration's page has the Endpoints and History tabs; Integrations describes the page, its grid and its row actions.
Why we do this¶
Planning and execution drift apart when they live in different tools. A wave plan in one system and migration plans built by hand in another means the two are reconciled by somebody reading both, and on a large migration that reconciliation is where mistakes happen.
Driving Move from Clarity means the plan that was agreed is the plan that runs, and the record of what happened sits alongside the record of what was intended.
What we collect¶
- Move providers, and their clusters, containers and networks
- Migration plans and the workloads in them
- Plan readiness and appliance information
- Workload-to-appliance mapping
What it adds¶
Reading it alongside the others is the point: each covers a blind spot in the rest.
Execution state against the plan: where the migration has actually got to, per workload, with the same identifiers the plan uses.
Readiness is the useful part before anything moves.
What is deliberately not inferred¶
This integration writes, unlike the discovery integrations
The site-wide read-only principle does not apply here. Clarity creates, starts, cancels and deletes migration plans on the Move appliance. Those are real actions with real consequences, and the credential has to be capable of them. Do not carry the read-only assumption across from the discovery pages.
- No guest data is read. Move moves the workload; Clarity does not open it.
- Clarity does not perform the migration. Move does the work; Clarity instructs it and reports on it.
What we require¶
A Nutanix Move appliance account with permission to create and run migration plans. This is not a read-only requirement, and it should not be requested as one.
- Interface: the Move appliance API, authenticating at
/move/v2/users/loginand using a bearer token thereafter - Connectivity: HTTPS on TCP 443 from Clarity to the Move appliance
- Account: capable of the plan lifecycle operations listed above
Provision this one deliberately
Because it writes, it deserves a different conversation from the discovery integrations: who is allowed to initiate a cutover from Clarity. Worth settling before the credential is created rather than afterwards.
Verification before handover¶
Run these as the system owner before handing the credential over, so a failed discovery run is never the first time anyone finds out.
- Confirm the login returns a token. Authenticate against the Move appliance as the account. Move issues a bearer token, so a successful login returning no token is a different failure from a rejected credential.
- Confirm providers and plans list. Read the providers and migration plans. An empty provider list usually means the Move appliance has no source or target configured yet rather than that the account lacks access.
Configuring the endpoint¶
On the integration's Endpoints tab, select the add icon (Create New Integration Endpoints). The Create new entry form opens with these fields, in this order:
| Field | Value |
|---|---|
| Name | A name for the endpoint |
| End Point | The Move appliance hostname or IP |
| Credential | The stored credential for the Move account |
| Job Schedule | A five-field cron expression. Migration Jobs also has Refresh Workloads |
| Enabled | Ticked. The box is unticked when the form opens |
The help texts: End Point "FQDN or IP Address of management system for technology e.g. vCenter, Nutanix Prism"; Credential "Credentials can be configured under Settings/Identity and Access Management/Credentials."; Job Schedule "Cron schedule – Use five fields: 〈mm〉 〈hh〉 〈day-of-month〉 〈month〉 〈weekday〉".
The Credential list offers the credentials stored under Settings → Identity & Access Management → Credentials, so create the credential there first.
No field is marked as required. Technology is set by the card and is hidden in the form. Select Save to create the endpoint, or Cancel to close the form. The edit icon opens the same fields as Edit entry.
Removing the access¶
Delete or disable the account on the Move appliance. Any migration plans Clarity created remain on the appliance and are managed there, so remove or complete them deliberately rather than assuming deleting the account tidies up. Then, in Clarity, remove the endpoint (select its row on the Endpoints tab, then Remove selected) or clear its Enabled box, and remove the credential under Settings → Identity & Access Management → Credentials.
Troubleshooting¶
| Symptom | Cause |
|---|---|
| Login succeeds but returns no token | A different failure from a rejected credential. Check the appliance version exposes /move/v2/users/login. |
| An empty provider list | The Move appliance has no source or target provider configured. This is an appliance state rather than a permission. |
| A plan action is refused | The account is not capable of the plan lifecycle. This integration writes; a read-only Move account is not sufficient. |
| A plan exists in Move but not in Clarity | It was created directly on the appliance. To pick it up, refresh the plans from the menu on Migration Jobs (refresh all plans, or the selected ones). |