OpenSDDC Roadmap

Follow the community roadmap here.

In Progress

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

Launch the websiteOpen community channels (GitHub, Slack, email)Publish SLTV and gIMI repositoriesContribution guide

Planning

A new storage approach versus closed stacks!

SLTV logical volume modelThin provisioning behaviourVMFS ↔ KVM-SLTV migrationThin-provisioned VM live migration

Planning

Observability from the application down to the infrastructure!

gIMI host agentHOST + GUEST eBPFCPU / memory / disk / network healthKVM/libvirt VM discovery

Future

A strong virtualization foundation!

dc(e)OS base imageKVM / QEMU / libvirt profileOVS / OVN profileSLTV host integration

Future

Bring the same storage portability to Kubernetes.

SLTV CSI driverPVC ↔ SLTV volume mappingKubernetes storage policy integrationOpenShift and vanilla Kubernetes tests

Future

One event chain from the application to the infrastructure.

gIMI Kubernetes collectorHost + VM + Kubernetes telemetry correlationPod ↔ VM ↔ Host relationshipOpenTelemetry-compatible export

Future

Not just individual tools—a broader open infrastructure ecosystem.

OpenSDDC ManagerUnified view for VM lifecycle and Kubernetes inventoryPolicy / control experiments on SLTV and gIMIPlugin / adapter model

architecture

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

feedback

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

code_off

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.