Skip to main content

OpenSDDC Manager

Subtitle: Unified control and visibility layer.

Goal​

OpenSDDC Manager aims to bring dc(e)OS hosts, non-KVM hypervisor environments (e.g. Proxmox), vCenter/vSphere inventory, Kubernetes clusters, SLTV volumes, gIMI telemetry streams, and OpenDIMA incident context into one control plane.

Example flow​

  1. Pod latency increases.
  2. See which worker node runs the pod.
  3. Map the worker to its VM.
  4. See which KVM host runs the VM.
  5. Inspect related SLTV volumes and storage backend metrics.
  6. Trigger OpenDIMA incident and automation if needed.

Architecture approach​

OpenSDDC Manager is a control plane:

  • Adapter model — Hypervisors, vCenter, OpenShift, vanilla Kubernetes, dc(e)OS adapters.
  • Plugin system — Integrations from the community or organizations.
  • Policy engine — Placement, storage selection, automated failover.
  • Unified UI / API — Telemetry via gIMI, incidents via OpenDIMA, storage inventory via SLTV.

Roadmap​

OpenSDDC Manager matures in Phase 6, after lower layers (gIMI, SLTV, dc(e)OS, OpenDIMA) reach a baseline maturity.

Repository​

github.com/opensddc/manager