Skip to main content

Orchestrator Requirements Overview

After completing the common prerequisites, provide orchestrator-specific access and configuration. Each orchestrator has its own credentials, connectivity, and setup checkpoints.

Shared install topics (VM sizing, DNS, SSL, SMTP, logos) live under prerequisites and domain/DNS — each orchestrator page links to those pages.

Select your orchestrator

OrchestratorCredentials requiredSpecial requirements
Apache CloudStackDomainAdmin userTemplates (Featured + Public), services, CloudStack quotas
VMware vSphereRead-only + API uservSphere 8.0.1.0+; custom role; ESXi console ports
OpenStackHorizon adminAPI endpoints, project/domain IDs, AZ consistency
Proxmox VEAPI user + permissions in ConnectingTemplates, public/private networks
CEPHAdmin userPublic S3 endpoint, ≥1 zone
Impossible CloudPartner API key (Bearer token)Beta + V1 API URLs, S3 region mapping, Object Storage only
Veeam (VSPC)Company Administrator/Portal Administrator + REST API keyVSPC 9.1; role, API URL, web UI URL, API key shared with StackConsole
PowerDNSAPI endpoint + API key + port, and NS list (ns1, ns2, …)v4.8.3+; prepare API/DNSSEC yourself — only those values are shared with StackConsole
Keycloak SSOAdmin or client credentialsRealm, redirect URIs
DIGIO KYCDIGIO client credentialsIndia only; sandbox + workflows
info

CEPH, Impossible Cloud, Veeam (VSPC), and PowerDNS are standalone integrations — they are not tied to a specific compute orchestrator and can be added alongside any of the above.

How this works