Skip to content
Roadmap
7 phases

Follow the community roadmap here. The OpenSDDC roadmap advances through inventory, storage portability, datacenter host OS, Kubernetes integration, observability correlation, and upper management layers.

Community00SLTV01gIMI02dc(e)OS03CSI04OpenDIMA05Manager06phase →↑ we are here
FIG. 3.1Every phase adds one layer to the open stack
00
Phase 0In progresswe are here

Community, communication channels, and roadmap

GoalWhat are our communication and contribution channels? Where is the roadmap?

Scope
  • Launch the website
  • Open community channels (GitHub, Slack, email)
  • Publish SLTV and gIMI repositories
  • Contribution guide
Deliverables
  • opensddc.io launch
  • GitHub org and communication channels
  • SLTV and gIMI repository releases
  • CONTRIBUTING.md / contribution guide
  • ROADMAP.md
01
Phase 1Planning

Thin-provisioned SAN usage with SLTV

GoalA new storage approach versus closed stacks!

Scope
  • SLTV logical volume model
  • Thin provisioning behaviour
  • VMFS ↔ KVM-SLTV migration
  • Thin-provisioned VM live migration
  • Migration scenarios
  • Portable disk lifecycle on QEMU/KVM
Deliverables
  • SLTV technical design document
  • Proof of concept
  • Lab environment
  • Baseline CLI
  • Failure scenario tests
02
Phase 2Planning

Coherent app + infra observability with gIMI

GoalObservability from the application down to the infrastructure!

Scope
  • gIMI host agent
  • HOST + GUEST eBPF
  • CPU / memory / disk / network health
  • KVM/libvirt VM discovery
  • Kubernetes cluster discovery
  • Node / VM / host relationship mapping
  • Basic telemetry export
Deliverables
  • gIMI agent MVP
  • gRPC API definition
  • Host inventory endpoints
  • Sample collector
  • OpenTelemetry export experiment
03
Phase 3Future

dc(e)OS + SLTV

GoalA strong virtualization foundation!

Scope
  • dc(e)OS base image
  • KVM / QEMU / libvirt profile
  • OVS / OVN profile
  • SLTV host integration
  • gIMI host agent integration
  • Immutable OS approach
Deliverables
  • First bootable dc(e)OS image
  • Host bootstrap flow
  • Node registration model for OpenSDDC Manager
04
Phase 4Future

Shared volume model from SLTV to Kubernetes

GoalBring the same storage portability to Kubernetes.

Scope
  • SLTV CSI driver
  • PVC ↔ SLTV volume mapping
  • Kubernetes storage policy integration
  • OpenShift and vanilla Kubernetes tests
  • Shared volume lifecycle for VMs and containers
Deliverables
  • SLTV CSI driver MVP
  • Kubernetes demo manifests
  • OpenShift test notes
  • PVC lifecycle documentation
05
Phase 5Future

gIMI observability and incident context with OpenDIMA

GoalOne event chain from the application to the infrastructure.

Scope
  • gIMI Kubernetes collector
  • Host + VM + Kubernetes telemetry correlation
  • Pod ↔ VM ↔ Host relationship
  • OpenTelemetry-compatible export
  • OpenDIMA incident timeline and service map
  • Telemetry and incident context inputs for OpenDIMA
Deliverables
  • Topology graph
  • Incident context API
  • OpenDIMA integration experiment
  • Sample latency troubleshooting scenario
06
Phase 6Future

OpenSDDC upper layers

GoalNot just individual tools—a broader open infrastructure ecosystem.

Scope
  • OpenSDDC Manager
  • Unified view for VM lifecycle and Kubernetes inventory
  • Policy / control experiments on SLTV and gIMI
  • Plugin / adapter model
  • Proxmox integration
  • Education, support, and community contributions
Deliverables
  • OpenSDDC Manager MVP
  • Proxmox adapter experiment
  • Plugin development guide
  • Community contribution model
01

Architectural integrity

As the roadmap progresses, OpenSDDC stays aligned with design principles: open interfaces, portability, and operational simplicity.

02

Feedback-driven

Community feedback, lab experience, and real-world scenarios update the roadmap.

03

Vendor agnostic

Our stack is not tied to a single hardware vendor or closed management plane.

Join the roadmap discussion!

Every phase is open to community discussion and contribution. Open issues on GitHub, join design discussions, or share your use case.