Skip to main content

What are VMware ESX Server Cluster Pools?


A cluster is defined as "a group of tightly coupled computers that work together closely so that in many respects they can be viewed as though they are a single computer" (per Wikipedia). A VMware ESX Cluster is no difference. Clusters are used for 3 things- 1) high availability, 2) load balancing, and 3) high performance computing. VMware ESX clusters are used for #1 and #2. With a VMware ESX Cluster, you define 2 or more physical machines that will provide resources for the hosts (or resource pools) that are assigned to that cluster. By using ESX clusters, you can achieve high availability (VM HA) and load balancing of virtual machines (called VMware DRS, discussed below)
Just to reiterate, here is why you use VMware ESX Clusters:
  • if one of the physical hosts goes down, the other physical host starts up the virtual guests machines that the original virtual host was running (VM HA).
  • if one physical host is over utilized by a virtual guest, that virtual guest is moved to the other physical host (VMware DRS, discussed in the resource pool section, below).
Both of these features use VMotion to move these virtual guests from one system to another.
How do you identify a cluster inside Virtual Center? A cluster has an icon that looks like a group of 3 servers, like this:
When you click on the Cluster icon, on the right, you will see that status of that cluster and you can configure the cluster. Here is what it looks like:
Notice how you are able to view the total CPU &Memory resources, number of hosts, total number of processors, total number of virtual machines, and the migrations that have been performed. This cluster has VMware HA and fully automated DRS enabled. That means that if any of the servers in the cluster fail, the other machines will automatically take over those virtual guests. Also, with automated DRS, the virtual guests will be automatically migrated to obtain the best possible performance for all machines, according to the resource pool settings.
So what is a resource pool?

What are VMware ESX Server Resource Pools?

A VMware ESX Resource pool is a pool of CPU and memory resources. Inside the pool, resources are allocated based on the CPU and memory shares that are defined. This pool can have associated access control and permissions.
You would want to use a pool to ensure that CPU and RAM resources are allocated fairly across systems or to ensure that certain systems are giving the resources they need to perform the tasks that the application on that server demand.

Inside VMware Virtual Center, Resource pools will be shown with the "pie chart" icon, like this:
Resource pools can be contained inside Clusters. Clusters contain hosts or resource pools, and and "Datacenters" contain Hosts and Clusters.
Here you see a resource pool inside a Cluster.
When setting up a resource pool, you must configure the limit, reservation, and share settings for both CPU & Memory for all virtual guest machines in the pool. Here is what that configuration windows looks like:
Back on the Resource Allocation tab for that resource pool, you can see a summary of the resources used by each VM and how that related to the resource pool:

Adding Alarms & Permissions

You can add alarms (alerts) and permissions on both clusters and resources pools. Thus, you could create a group of users who could only manage a single resources pool of server. To add an alarm or permission at the cluster or resource pool level, just right-click on the cluster or pool.

Summary

In summary, VMware ESX Clusters & Resource Pools are very important pieces of VMware's Virtual Infrastructure (VI). To take advantage of all that VI has to offer, you must understand and properly configure VMware Clusters & Resource pools. With clusters & resource pools, you can ensure that one system doesn't run away with the resources of the others, ensure that your virtual server load is balanced, and guarantee that if a virtual server goes down, all systems in that cluster will be brought up on another physical server.

Popular posts from this blog

HOW TO EDIT THE BCD REGISTRY FILE

The BCD registry file controls which operating system installation starts and how long the boot manager waits before starting Windows. Basically, it’s like the Boot.ini file in earlier versions of Windows. If you need to edit it, the easiest way is to use the Startup And Recovery tool from within Vista. Just follow these steps: 1. Click Start. Right-click Computer, and then click Properties. 2. Click Advanced System Settings. 3. On the Advanced tab, under Startup and Recovery, click Settings. 4. Click the Default Operating System list, and edit other startup settings. Then, click OK. Same as Windows XP, right? But you’re probably not here because you couldn’t find that dialog box. You’re probably here because Windows Vista won’t start. In that case, you shouldn’t even worry about editing the BCD. Just run Startup Repair, and let the tool do what it’s supposed to. If you’re an advanced user, like an IT guy, you might want to edit the BCD file yourself. You can do this

AD LDS – Syncronizing AD LDS with Active Directory

First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N

DNS Scavenging.

                        DNS Scavenging is a great answer to a problem that has been nagging everyone since RFC 2136 came out way back in 1997.  Despite many clever methods of ensuring that clients and DHCP servers that perform dynamic updates clean up after themselves sometimes DNS can get messy.  Remember that old test server that you built two years ago that caught fire before it could be used?  Probably not.  DNS still remembers it though.  There are two big issues with DNS scavenging that seem to come up a lot: "I'm hitting this 'scavenge now' button like a snare drum and nothing is happening.  Why?" or "I woke up this morning, my DNS zones are nearly empty and Active Directory is sitting in a corner rocking back and forth crying.  What happened?" This post should help us figure out when the first issue will happen and completely avoid the second.  We'll go through how scavenging is setup then I'll give you my best practices.  Scavenging s