MokaFive Suite is a distributed desktop virtualization solution that supports Windows-based virtual machines that execute on either a type II hypervisor running on either Microsoft Windows or Apple OS X, all on MokaFive’s own BareMetal client hypervisor platform. As a distributed desktop virtualization solution MokaFive Suite is capable of operating without a permanent network connection.
Direct comparison between server hosted desktop virtualization and distributed desktop virtualization services and architectures is difficult to perform; and compared to a server hosted desktop virtualization cost model, a distributed desktop virtualization cost model may appear to be incomplete. However, it includes all of the components needed to provide a virtual desktop service, that meets or exceeds the standard baseline requirements I published here. Contrasted with the server hosted desktop virtualization architecture, there is no need for the virtual infrastructure servers or SAN which account for the majority of cost of conventional server hosted desktop virtualization environments.
FAQ
Where did the costs, equipment specification and sizing data come from?
All hardware pricing was obtained direct from the HP Small and Medium Business store front.
The pricing and other data points used in the MokaFive cost model were obtained as follows:
- MokaFive Suite Costs – MokaFive
- Windows Software Assurance Costs – Microsoft Open License Estimated Retail Price List July 2011
- MokaFive Management Server Scalability - MokaFive
- Data Center Power and Cooling Costs – Estimated cost provided by subject matter expert
- Server Power Consumption – HP Power Advisor
- Storage Power Consumption – HP Power Advisor
- Network Switch Power Consumption - Estimate provided by subject matter expert
What is the “Oversubcription” value for?
Oversubscription is the percentage by which you can override the cost model’s server sizing rules. For example, if a VDI server supported 80 concurrent sessions without an oversubscription setting sizing a system to support 81 sessions would automatically require two servers. Within oversubscription of 5% the cost model will allow a server to be oversubscribed by four sessions before allocates a second server. Setting an oversubscription value of zero will rigidly enforce system sizing rules.
Why did you choose to set the Y/N configuration switches this way?
The default settings of the configuration switches ‘Include desktop PC refresh (Y/N)” etc. were set based on the following assumptions:
Include desktop PC refresh – Y
Given that most desktop virtualization initiatives will take place in conjunction with migration to Windows 7 which has a higher resource requirement than Windows XP, a desktop hardware refresh would be advisable. The pricing information included in the model is based on the HP Compaq 6200 Pro desktop PC.
Include Hot Standby Servers – Y
Even though MokaFive Suite does not require continuous availability or connectivity to data center hosted management servers for its operation, it is recommended that a hot standby management server is provided. The ability to deploy urgent application updates and operating system patches must not be compromised through data center hardware failure.
Include Business Continuity Servers – Y
As with Hot Standby Servers; even though MokaFive Suite does not require continuous availability or connectivity to data center hosted management servers for its operation, it is recommended that business continuity servers are provided. The ability to deploy urgent application updates and operating system patches must not be compromised through data center failure.
Note: the configuration switches can be adjusted to meet individual needs and the cost model will recalculate accordingly.
Virtual servers are likely to be the preferred choice in many environments, but incorporating this into the cost model would have added to the complexity of the cost model with no real benefit.
Why didn’t you include Data Center Network Switch Ports?
MokaFive Suite system sizing recommendations suggest that a single management server can support up to 5,000 desktops. Even if physical servers were deployed, as each server only requires two network ports it is unlikely that additional network hardware will be required to support management server deployment in the data center.
Why didn’t you include Data Center Power and Cooling Costs?
As with data center network switch ports; MokaFive Suite can support up to 5,000 desktops per management server, the power requirements associated with the management servers is low and it is unlikely that additional power will be required to support management server deployment.
Will you be providing an operating costs model?
Yes, creating a general OpEx model will take some time, but in the interim I can assist with developing models for specific environments.
What if I disagree with your assumptions?
If you have obtained better pricing for any hardware or software component or if your test results show you can get more or fewer sessions per server, you can change any of the input fields and the model will recalculate accordingly.
Aside from that, please feel free to share any comments you may have or make recommendations for improvement. For my part, I will endeavor to respond to all constructive comments and incorporate any changes that improve the accuracy of the cost model.
Can I have a copy of your cost model?
I’m a firm believer in the value of open source projects. As you can see, I haven’t protected the cost model calculations in any way. so I’m not going to stop you copying it, other than to draw attention to the license which permits it use for non-commercial purposes only. Having said that I would prefer it if you could link to this page rather than embedding the cost model in to your own page or copying it; partly because I’d like to be sure that anyone using it has access to the latest version of the model and any accompany in notes, but also because I think there’s more value to be had by cooperating to improve a single model than in creating multiple competing models.
If you are interested in using it for commercial purposes, then please get in touch.
Change Log
r 1.0
Initial Release - 17th July 2010
We have a 3 year desktop refresh cycle, run a virtual infrastructure that with $0 change back – its free just to get people using it instead of buying dedicated servers, and have shared SAN storage that we charge back at $150 per TB.
With that plugged in to the cost model it would cost me $380 per desktop to deploy MokaFive. That’s excellent compared to VDI. I do have some people that we are thinking would need iPads and I could do with a small VDI environment for them – is there any way I could use MokaFive to manage the VDI desktop so I don’t need to support two desktop management systems?
Thanks for sharing this. I don’t think there’s enough done to publicise the benefits of this type of approach to desktop management, its good to see an independent perspective.
FYI there’s the bad link up at the top where it says ‘ the standard baseline requirements I published here” it doesn’t work on the View cost model either. You also might want to change the cost model so that it defaults to Yes for the desktop refresh.
Thanks for the feedback Iain, I’ll take care of both of them