Nutanix SSP¶

Clarity Transform executes Nutanix Self-Service Portal automation as named, audited Clarity actions: launching runbooks, uploading disk images, and creating, updating and publishing blueprints through Prism Central.

Where to find it¶

Go to Discover → Integrations, then select the Nutanix SSP card. The card's category label is Automation. The integration's page has the Endpoints and History tabs, and an Operations tab; Integrations describes the page, its grid and its row actions.

Why we do this¶

Migration work is full of repeatable operations that somebody performs by hand because the automation lives somewhere else. Where a customer has already built Self-Service Portal runbooks, those runbooks are the customer's own tested way of doing the thing, and rebuilding them inside Clarity would be both wasteful and worse.

What we collect¶

This integration is primarily an execution surface rather than a discovery source. It reads what it needs to offer the operations:

Blueprints, where those operations are used
The outcome of each execution, recorded as a Clarity action

What it adds¶

All Prism Central communication is performed in PowerShell, consistent with the rest of the runbook estate, so the automation is inspectable in the same place as everything else rather than hidden behind a different mechanism.

What is deliberately not inferred¶

This integration writes, unlike the discovery integrations

The site-wide read-only principle does not apply here. Clarity launches runbooks, uploads disk images and creates, updates and publishes blueprints. Those change the customer's environment, and the credential has to be capable of them. Do not carry the read-only assumption across from the discovery pages.

Clarity does not author runbooks. The runbooks are the customer's; Clarity invokes them. Blueprints are different: Clarity can create and update them.
No guest data is read.

What we require¶

A Prism Central account able to run the Self-Service Portal operations in scope: launching runbooks, and where those operations are used, uploading images and creating, updating and publishing blueprints. This is not a read-only requirement.

Interface: the Prism Central v3 API
Connectivity: HTTPS on TCP 9440 from Clarity to Prism Central
Account: scoped to the operations actually wanted, rather than a full administrator by default

Scope it to the operations in use

Run SSP Runbook, Upload Disk Image, Create or Update Blueprint and Publish Blueprint are four separate capabilities. An engagement using only runbook launch does not need the other three, and asking for all four because the integration supports all four is how an access request gets refused.

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 account authenticates to Prism Central on 9440. The port is 9440 rather than 443. That is the detail most often missed when the firewall rule is raised.
Confirm the runbooks list. Read the runbook list as the account. An empty list usually means the Self-Service Portal has no runbooks rather than that access is missing, so check in the portal before treating it as a permission problem.
Confirm one operation runs, on something harmless. Launch a runbook that does nothing consequential. Demonstrating the write capability on something disposable is better than discovering the gap mid-migration.

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	Prism Central as `host:9440`
Credential	The stored credential for the Prism Central account
Job Schedule	A five-field cron expression. Operations themselves are invoked on demand from the Operations tab
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.

The Operations tab¶

The Operations tab lists the automation operations Clarity can run through the endpoint. The grid's columns are:

Name
Operation Key
Operation Kind
Remote Identifier
Enabled

In this build it holds four operations:

Name	Operation Key	Operation Kind
Create or Update Blueprint	`create-blueprint`	`create_or_update_blueprint`
Publish Blueprint	`publish-blueprint`	`publish_blueprint`
Run SSP Runbook	`run-runbook`	`runbook`
Upload Disk Image	`upload-disk-image`	`upload_disk_image`

The grid has the standard toolbar: the add icon, the edit icon, Remove selected, Clear selection, Reload table data, Enable spreadsheet editing, Export CSV and Import CSV. Each row has two row actions: View Details (the eye icon) and Run Now (the play icon).

The grid remembers its Search: text, column filters, sort order and page size between visits. If the grid shows fewer rows than you expect, clear the Search: box and the filter row.

The operation form¶

The add icon opens the Create new entry form and the edit icon the same fields, filled in. The fields, in order:

Name: text. Help: "Human-friendly name for the automation operation."
Operation Key: text. Help: "Stable, unique, lowercase kebab-case key (e.g. run-runbook). Referenced by runbook tasks and maps by convention to rb-pautol-{technology}-{key}.ps1."
Operation Kind: text. Help: "Technology-specific operation kind used to select a validator."
Description: a text area.
Remote Identifier: text. Help: "Operation-specific remote identifier (runbook UUID, blueprint UUID, or image target)."
Parameter Schema Json: text. Help: "JSON schema describing the editable request payload for this operation."
Defaults Json: text. Help: "JSON default parameter values applied when the request omits them."
Enabled: a checkbox.

Technology, Id and the audit fields are hidden in the form.

Removing the access¶

Delete or disable the Prism Central account, or remove the roles granting the Self-Service Portal operations. Anything already executed has taken effect in the customer's environment and is not undone by removing the access. 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
Cannot reach Prism Central	The API is on TCP 9440, not 443.
An empty runbook list	The Self-Service Portal has no runbooks, or the account cannot see them. Check in the portal first.
An operation is refused	The account lacks that capability. Runbook launch, image upload, blueprint create or update and blueprint publish are separate.
An operation succeeded but the outcome is not what was expected	Clarity invokes the customer's runbook; it does not author it. The behaviour is the runbook's.