Infrastructure Control Server · Hypervisor management

Powerful control, limited privileges

Proposed interface concept Not released. A design for discussion, drawn in HTML and CSS; not a screenshot of working software.

Connected Proxmox VE clusters with host and VM inventory, resource health, VM actions that require approval, cluster utilization and topology, and the credential scope the control server holds: a restricted API token, not root, limited to the resources Office Unbound uses. The figures shown are example data.

View full size Download image (WebP, 1600×1106) Infrastructure control

Proposed interface concept Not released · example data · subject to change

Office UnboundInfrastructure ControlRidgeline IT · ProductionSearch hosts, VMs, containers, services/2DO

Production1 of 4 environmentsOverviewHypervisorsContainersServicesMonitoringAlerts2Updates3CapacityRecoveryAudit logSettingsController ics-01Standby ics-02 ready

ProductionHypervisorsProxmox VE clustersExample data

TopologyConnect cluster

ridge-pve-a3 hosts · 18 managed VMs · 14 not in scope

Quorum 3 of 3ceph-a healthy

CPU38%
Memory77%
Storage52%

ridge-pve-b2 hosts and a quorum device · 6 managed VMs

Quorum 3 of 3 votesceph-b write latency

CPU31%
Memory37%
Storage71%

Credential scope · ridge-pve-aLeast privilege

ics@pve!office-unboundAPI token

Scope: Pool office-unbound · 18 VMs · storage ceph-a
Granted: VM.AuditVM.PowerMgmtVM.MigrateVM.Allocate pool onlyDatastore.AllocateSpace ceph-a onlySys.Audit read-only
Not granted: rootSys.ModifyPermissions.ModifyUser.Modify
Expires: in 62 days · last rotated 14 Sep · stored encrypted

Access to 14 other VMs on this cluster: none (not in scope)

RotateRevokeExample scope · Proxmox VE privilege names

Topology and failure domainsCluster → host → managed VMs

Rack 1Failure domain · own power feed

pve-a1Cluster A

mail-01db-01files-01+4

pve-a2Cluster A

mail-02docs-01id-01+3

Rack 2Failure domain · own power feed

pve-a3Cluster A

db-02search-01proxy-01+2

pve-b1Cluster B

meet-01chat-01+1

pve-b2Cluster B

calls-01backup-01+1

mail-01 and mail-02 on different hosts
db-01 and its replica db-02 in different racks
Rack 2 holds all of cluster B: one power fault stops it (as in INC-2031)

Managed VMs6 of 24 · pool office-unbound

VM	Host	State	vCPU · memory	CPU	Last backup	Actions
mail-01Mail, IMAP	pve-a1	Running	4 · 16 GB	9%	Today 01:12
mail-02Mail, SMTP relay	pve-a2	Running · service failing	4 · 16 GB	2%	Today 01:14
db-01PostgreSQL primary	pve-a1	Running	8 · 48 GB	22%	Today 01:30
search-01Search and indexing	pve-a3	Running	4 · 24 GB	41%	Today 01:41	StartRunning Shut downApproval RebootApproval Migrate to…Approval Resize…Approval SnapshotAllowed
docs-01Document engine	pve-a2	Running	6 · 16 GB	12%	Today 01:20
meet-01Meetings	pve-b1	Running	8 · 32 GB	6%	Today 00:58

Waiting for approval: migrate search-01 from pve-a3 to pve-a2 · requested by D. Okafor 01:10 · second approver S. Reyes · runs only if the target has room and the VM’s backup is less than 24 hours old.

OverviewMonitoring2AlertsCapacityMore

Clusters, hosts and VMs under a least-privilege token: what it can do, what it cannot, and the VMs it never sees.

Shape this before it is built

This screen is a proposal. MSP design partners review concepts like this one against how they actually run customers, and say what is missing.

Become an MSP design partner Register interest