Overview

Nutanix runs your clients’ virtual machines on AHV or ESXi clusters that Prism Central manages, and Nutanix SP Central lets a service provider give each client its own tenant. Connect your Prism Central to Neo once, at the MSP level, with its address and an API key for a Neo service account.

​

What Neo can do with Nutanix

With the access you choose, Neo can also manage images and templates, clusters and hosts, storage, networking, network security policies, data protection, upgrades and licensing, and SP Central tenants. Some changes always ask a technician first, under every access profile, such as deleting a VM or a disk, or changing users and roles: the full list.

​

Your clients in Nutanix

Prism Central has no client object of its own. You keep a client’s VMs in an SP Central tenant, a project, a category such as Customer: Acme, a cluster of their own, or under a naming prefix. Neo finds a client’s VMs the way you already group them, and says how it found them. There is no Organization Mapping tab for Nutanix.

​

What Neo never does

• Read or create a VM console token, an API key’s secret, an object store key, a claim token’s secret, a VPN device’s configuration or the cluster’s encryption key backup.
• Destroy a cluster, unregister Prism Central from what it manages, or restore Prism Central from a backup.
• Send a batch of API calls in one, because Neo checks each call’s permissions on its own.

Neo also removes the fields Nutanix keeps credentials in (passwords, secrets, private keys, tokens, API keys, SNMP keys, a guest’s Sysprep or cloud-init script, and the user name and password in a URL) from every answer before an agent sees it. When an agent sends a whole entity back, Neo puts the stored values back where it removed them, so a change never overwrites a password.

​

Next steps