When organizations commit to open-source infrastructure, they are making more than a technical decision. They are making a long-term architectural commitment.
That was the case for Monash University.
As the university expanded its online learning programs and supported new research initiatives, it needed to deliver virtual desktops to faculty and students. Rather than deploying a traditional, full-stack VDI solution, Monash chose to build on its existing OpenStack cloud.
The challenge was not infrastructure. It was control.
The OpenStack VDI Gap
OpenStack is powerful. It manages compute, networking, and storage across a cloud environment. It supports multi-tenancy, quotas, and flexible provisioning models.
But OpenStack does not assign desktops to users. It does not enforce desktop access policies. It does not decide when to provision new instances or power down idle ones.
To turn OpenStack into a practical VDI platform, Monash needed a centralized connection and policy layer.
Without that layer, OpenStack remains infrastructure. With it, OpenStack becomes a scalable desktop delivery system.
Building a Policy-Driven Desktop Model
Monash implemented Leostream as the control plane above its OpenStack environment.
In this architecture:
- OpenStack manages compute and networking resources.
- Leostream manages user authentication, desktop assignments, provisioning, and session lifecycle.
This separation allowed Monash to maintain its open-source infrastructure strategy while adding the controls required for VDI at scale.
Using golden images stored in OpenStack, the university could provision desktops dynamically as demand increased. When desktops were no longer needed, resources could be released back into the pool.
This prevented unnecessary CPU consumption and improved overall efficiency.
Matching Resources to Real User Needs
Not all users require the same desktop configuration. A one-size-fits-all approach wastes resources and increases cost.
With policy-based assignments, Monash could allocate different machine profiles based on user roles. For example, bioinformatics users were provisioned systems with significantly higher memory allocations, while educators received smaller configurations aligned to their workloads.
This level of granular control ensured that:
- High-demand research workloads received appropriate capacity
- Faculty desktops were right-sized
- Infrastructure was not overprovisioned
Instead of building to the highest common denominator, Monash built to policy.
Secure, Flexible Access
Another critical requirement was secure access for a diverse user base.
Through the Leostream Gateway, Monash provided browser-based access to OpenStack desktops. This eliminated the need for client installs on incompatible devices and supported a wide range of student and faculty endpoints.
The result was secure, centralized access management layered onto an open infrastructure foundation.
Avoiding Legacy VDI Lock-In
Traditional VDI vendors did not offer a comprehensive OpenStack-based solution. Deploying a proprietary VDI stack would have required significant licensing investment and architectural compromise.
By combining OpenStack with Leostream’s centralized access management, Monash avoided:
- Hypervisor licensing fees
- Full-stack vendor dependency
- Infrastructure redesign
- Costly platform migrations
Instead of introducing a proprietary VDI stack into their environment, Monash aligned desktop delivery with their existing open-source cloud strategy. By combining OpenStack with centralized connection management, they preserved architectural flexibility while gaining the policy controls required for production-scale VDI.
This approach reflects a broader shift discussed in our recent post where infrastructure remains open and the access layer remains independent. The result is a model that supports growth without increasing dependency.
The Broader Lesson
Monash University’s approach highlights an important principle:
OpenStack can support VDI at scale, but only when paired with centralized connection and policy management.
When infrastructure and access are separated:
- OpenStack remains flexible and open
- Desktop delivery becomes operationally manageable
- Resources can scale up and down based on demand
- Costs align with actual usage
This model allows organizations to maintain control over their architecture while still delivering enterprise-grade desktop experiences.
Conclusion
Scaling OpenStack VDI is not about replacing infrastructure. It is about enabling it.
By layering policy-driven access management on top of OpenStack, Monash transformed its research cloud into a production-ready desktop platform.
For organizations committed to open-source infrastructure, the path forward is not another proprietary stack. It is a control plane that unlocks the full potential of OpenStack.