This blog is part of the "Making VDI Work" blog series. If you'd like to learn more about how to make VDI work for your organization, check out our previous installments How to Design the Ideal VDI or Hosted Desktop Solution, Things to Consider about Client Devices, and Choosing A Display Protocol
Earlier this month, OpenStack Summit was conveniently held in Leostream’s back yard of Boston. I took the opportunity to avoid my Waltham commute, attend a particularly interesting session, and participate in some great follow-up conversations centered on OpenStack VDI. Here’s what I learned.
VDI was supposed to save us money. By virtualizing desktops, we mobilized the workforce, maximized resource utilization, and reduced hardware costs. So, the cost-savings had to follow naturally, right? Well, once those pesky licensing fees started to add up, suddenly that big money-saving VDI initiative became just as pricey, if not more so, than dedicated hardware. So, does that mean that the VDI Revolution was a flop?
The other week, while giving a demonstration of our VDI management platform, I tossed out the word “orchestration”. It’s a term you often hear from organizations that are moving resources into the cloud. Invoking the orchestration card, however, brought on the question of how, exactly, our platform was different from all of the other cloud orchestration tools on the market.
As hardware costs rise, organizations and IT professionals need solutions to maximize resources and minimize costs - all without sacrificing user experience. This can be a tall order when your users are graphics-heavy power users whose hardware requirements come with a 4-figure price tag. Making the most of every GPU is priority number one, and often, dedicated hardware for every single virtual machine just isn’t feasible.
It’s time for volume three of our “Making VDI Work” series. In this series, we highlight various
infrastructure components that make up your hosted desktop solution, whether you’re hosting virtual or physical desktops in your data center or in a cloud. In our first installment, we talked about your client devices, and the users who are attached to them. Now, let’s look at how you get a client device connected to the user’s hosted resource.
This past Thursday, I sat down with Leostream CEO Karen Gondoly to discuss hosting graphics-rich applications in Microsoft® Azure® Clouds in our latest webinar – “Graphics-Rich Applications at Cloud Scale with Azure and Leostream.”
No one can deny that, for years, Amazon Web Services has dominated the public cloud market. If you need a service in the cloud – storage, backup, compute, DevOps, you name it – AWS has a service for you. But, while Amazon Workspaces provides a baseline for VDI in the public cloud, I’ve neither seen nor heard a stampede of organizations rushing to put their desktop workloads in the cloud. Why is that?
Today, we are pleased to announce our partners at Canonical have released the public beta of their Juju Marketplace where users can test drive the new Leostream Juju charm, along with many other third party charms, for a complete hosted desktop solution you can deploy in a snap.
Remember Mickey in The Sorcerer’s Apprentice when he is tasked to carry heavy buckets of water to fill up the Sorcerer’s pool? Mickey is exhausted and dismayed – until he discovers the Sorcerer’s wand and learns about the magic of automation! He enchants a broom to do the heavy lifting for him. Mickey sits back and relaxes while his broom does all the work – until that broom becomes many brooms who carry bucket after bucket, filling the pool until it becomes an overflowing tidal wave, sweeping him away!