VMware PEX 2010: a short comment on DRS IO February 14, 2010
Posted by vneil in Virtualisation, VMware.1 comment so far
There has been a good amount of coverage from the VMware Partner Exchange in Las Vegas last week but one bit of news that caught my attention was the mention of DRS for IO. The only blog post I saw it mentioned was in this post by Duncan Epping. After a quick google I found this great post by Ian Koenig over on his blog from last September.
It looks like if it was mentioned at PEX it might be coming soon, I had kind of hoped it might have been in vSphere as the next logical extension of DRS after CPU and Memory resource scheduling.
The way we run our current cluster is one big cluster with test and production VMs spread across all the host servers with their VMDKs also mixed on datastores. They are distributed into appropriate resource groups and all this helps to even the workload and make full use of all resources.
The cluster is not heavily burdened at the moment and we are continuing to P2V Windows servers and deploy new Linux servers onto it. I see IO DRS as an extremely helpful tool with the growth of the number of VMs in the cluster to keep the necessary prioritising of production over testing.
In the meantime I’ll keep an eye out for any more news on IO DRS.
Getting started February 11, 2010
Posted by vneil in ESX, ESXi, Virtualisation, VMware.1 comment so far
As I mention in the about page I have decided to start this blog to try and give a little bit back to the community and post some of my experiences with working in virtualisation.
The idea when I thought about starting this blog was to add more information about ESXi to the VMware blogging arena as most of the information I read was about ESX. Unfortunately since I decided to create this blog (it’s taken me a few weeks to get going) VMware have beaten me to it and they’ve started a major push to promote ESXi and seem to be selling it as an upgrade to move from ESX to ESXi, which I find a strange choice of words. I guess they could mean to upgrade from ESX3.5 to ESXi4.0 because otherwise it would just be a change of install base and methods, not an upgrade. VMware also added an ESXi contest to their vSphere Blog which has meant a sudden glut of ESXi blog entries popping up, it seems my timing for starting an ESXi focused blog was a little off.
I won’t be down hearted , I will continue with my mission and help promote ESXi and detail some of the experience we have had running it in our 2 production clusters which consist of a 10 and a 20 node cluster.
VirtuallyNil 