Orchestrator Requirements Overview
After completing the common prerequisites, you need to provide orchestrator-specific access and configuration details. Each orchestrator has its own credentials, connectivity, and setup checkpoints.
Select Your Orchestrator​
| Orchestrator | Credentials Required | Special Requirements |
|---|---|---|
| Apache CloudStack | DomainAdmin user | Templates, services enablement, KVM snapshots |
| VMware vSphere | Read-only + API user | vCenter folder structure, 31 specific permissions, ESXi console ports |
| OpenStack | Horizon admin | API service endpoints, project/domain IDs |
| Proxmox VE | Root-level admin | OS templates as per Proxmox template requirements |
| CEPH | Admin user | S3 endpoint, zone configuration |
| PowerDNS | API key | v4.8.3+, API + DNSSEC enabled |
| Keycloak SSO | Admin credentials or client credentials | Realm setup, redirect URIs |
info
CEPH and PowerDNS are standalone integrations — they are not tied to any specific compute orchestrator and can be added alongside any of the above.
How This Works​
flowchart TD
A("✅ Common Prerequisites\nVM specs, DNS, SSL, SMTP") --> B("🔌 Orchestrator Requirements\nCredentials & connectivity")
B --> C("🛠StackConsole installs CMP\nServer setup & configuration")
C --> D("✔ Checkpoints verified\nTemplates, networks, VMs, console")
D --> E("🚀 CMP goes live")
style A fill:#4A90D9,color:#fff,stroke:#2c6fad
style B fill:#4A90D9,color:#fff,stroke:#2c6fad
style C fill:#f39c12,color:#fff,stroke:#c07d0a
style D fill:#f39c12,color:#fff,stroke:#c07d0a
style E fill:#27ae60,color:#fff,stroke:#1e8449