We are a hospital replacing 1500 desktop PCs before our new campus opens in the fall with thin terminals connecting back via RDP to 1500 WinXP VMs as a VDI solution.
2 datacenters
6 HP c-class blade chassis, 3 in each datacenter.
38 HP ProLiant BL480c blades with dual Quad-Core Intel® Xeon® 5300 Series processors and 24GB memory (3GB per core)
8 blades per chassis
4 NICs on each blade, 2 to each internal chassis cisco switch (one uplink each to core datacenter cisco 6513).
VLAN VMotion and Service Consoles (seperately)
2 EVA8000, 1 in each datacenter. 2 clusters will use "EVA1" as primary storage with CA to "EVA2". 2 clusters will use "EVA2" as primary storage with CA to "EVA1".
38x300GB FC drives (one diskgroup), 22x500GB FATA drives (another diskgroup)
4 ESX clusters with DRS & HA
VDI-A: 10 ESX (5 in each datacenter), 400 VMs (40 VM per ESX with room for complete datacenter failover: 80 VMs/ESX with 5 ESX)
VDI-B: 10 ESX (5 in each datacenter), 400 VMs (40 VM per ESX with room for complete datacenter failover: 80 VMs/ESX with 5 ESX)
VDI-C: 10 ESX (5 in each datacenter), 400 VMs (40 VM per ESX with room for complete datacenter failover: 80 VMs/ESX with 5 ESX)
VDI-D: 8 ESX (4 in each datacenter), 320 VMs (40 VM per ESX with room for complete datacenter failover: 80 VMs/ESX with 4 ESX)
8 datastores per cluster/ESX host (one LUN per datastore)
512GB LUNs (50 VMs with 10GB C: drives + config/log/vm swap \[50 * (.5*512MB)=12.8GB swap])
VMs are WinXP SP2 with 512MB memory, 10 GB C: drives. Altiris used for imaging & customization (initially deployed from templates w/customization spec). Appstream used to stream apps.
Did I miss anything? Can anything be improved? We are looking for failover capability as well as management efficiency.
It look very similar to what we are doing for virtual servers. Except we are using XP12000's.
My biggest concern would be the amount of free space available on your LUN's. Maybe I read it wrong. My understanding is the best practice is to not go over 80% utilization of space.
If you have 50 VM's using 10 GB each and ~ 13 GB of swap, you are going to use 100% of your space. Not a good idea.
With that in mind, 512 is 80% of 640GB. Good advice, is this common practice to stay below 80% utilization of the datastore?
I would argue that this is dependant on the LUN function.
This LUN is going to contain growing files in logs, so you do need to put some headroom.
If it was just holding VMDK files and nothing else then perhaps you can squeeze the space a little.
Is 40 vm's per 2-way quad-core blade a number based on real life measurements or that is what you would expect to see ?
Massimo.
We did some load testing on smaller blades (not these exact ones) and found that at 40 VMs, our memory was maxing out but our CPUs were underutilized. The uppers decided to go with the bigger blades for comfortable utilization of memory & CPU but planning to handle up to 80 in a failover state.
I'll let you know how it goes when we get one of these going.
We have XP1024s but they wanted to get some (slightly) cheaper storage to run these.
I can understand wanting cheaper storage. The only reason we're using the 12000's is it is for servers.
The 40:1 ratio doesn't look out of line to me from the testing we have done with XP VM's.
Cheaper storage and your choosing an EVA love it!
Tell me how did you get buy in for this type of implementation?
What are your expected deployment times based on this number of Images?
Bringing the desktops in to the datacenter is a solution being driven by our CIO. We have gone the route with blade PCs and have a number of them but as our need grows, we demonstrated to him the benefits of using vmware for high availability and it was then more preferrable to the CCI blades.
As for the design of the implementation, that has been accomplished by my group with some advice from our HP reseller. We are aiming for high availiability as we are a 24x7 hospital environment.
We expect it will take upwards of a month to deploy 1500 10GB VMs. I am looking in to writing something using the SDK to automate this as it definitely wouldn't be any fun doing it manually through the template deployment wizard.
Sounds like a great project to work on, I've got friends working in hospitals in the UK still struggling with 486's for some things... I get told off for talking VDI at them ![]()
Good luck with the project, sounds very worthwhile and rewarding ![]()
Simon
What are you using to manage the connections or are you doing a 1:1 design?
-Richpo
This sounds like the most awesome-est project, but, why not go with a terminal services project? Do you have applications that don't play nice with Citrix or TS?
We have an aging metaframe installation on a couple NT4 & win2k servers - I don't know why they didn't decide to continue or expand/upgrade that. They want to move away from it for whatever reason.
We have developed a broker in-house to handle 1:1 and pool assignments. We did look at some of the commercially available brokers but in the end decided to write our own because of our unique requirements.