Figure 1.9 The products in the VMware Infrastructure suite work together to provide a scalable, robust, and reliable framework for creating, managing, and monitoring a virtual enterprise.
The next chapter will begin a start-to-finish look at designing, implementing, managing, monitoring, and troubleshooting a virtual enterprise built on VI3. I’ll dive into much greater detail on each of the products I introduced in this chapter. This introduction should provide you with a solid foundation so we can discuss the different products beginning with the next chapter. You can use this introduction as a reference throughout the remaining chapters if you want to refresh your base knowledge for each of the products in the suite.
Master It You want to centralize the management of ESX Server hosts and all virtual machines.
Master It You want to minimize the occurrence of system downtime during periods of planned maintenance.
Master It You want to provide an automated method of maintaining fairness and balance of resource utilization.
Master It You want to provide an automated restart of virtual machines when an ESX Server fails.
Master It You want to institute a method of providing disaster recovery and business continuity in the event of virtual machine failure.
Chapter 2 Planning and Installing ESX Server
Now that you've been introduced to VMware Infrastructure 3 (VI3) and its suite of applications in Chapter 1, you're aware that ESX Server 3 is the foundation of VI3. The deployment, installation, and configuration of the ESX Server requires adequate planning for a VMware-supported installation.
In this chapter you will learn to:
♦ Understand ESX Server compatibility requirements
♦ Plan an ESX Server deployment
♦ Install ESX Server
♦ Perform postinstallation configuration
♦ Install the Virtual Infrastructure Client (VI Client)
Planning a VMware Infrastructure 3 Deployment
In the world of information technology management, there are many models that reflect the project management lifecycle. In each of the various models, it is almost guaranteed that you'll find a step that involves planning. Though these models might stress this stage of the lifecycle, the reality is that planning is often passed over very quickly if not avoided altogether. However, a VI3 project requires careful planning due to hardware constraints for the ESX Server software. In addition, the server planning can have a significant financial impact when calculating the return on investment for a VI3 deployment.
VMware ESX Server includes stringent hardware restrictions. Though these hardware restrictions provide a limited environment for deploying a supported virtual infrastructure, they also ensure the hardware has been tested and will function as expected as a platform for VMware's VMkernel hypervisor. Although not every vendor or whitebox configuration can play host to ESX Server, the list of supported hardware platforms will continue to change as newer models and more vendors are tested by VMware. The official VMware Systems Compatibility guide can be found on VMware's website at http://www.vmware.com/pdf/vi3_systems_guide.pdf. With a quick glance at the systems compatibility guide, you will notice Dell, HP, and IBM among a dozen or so lesser-known vendors. Within the big three, you will find different server models that provide a tested and supported platform for ESX Server.
The Right Server for the JobSelecting the appropriate server is undoubtedly the first step in ensuring a successful VI3 deployment. In addition, it is the only way to ensure VMware will provide any needed support.
A deeper look into a specific vendor, like Dell, will reveal that the compatibility guide identifies server models of all sizes (see Figure 2.1) as valid ESX Server hosts, including:
♦ The 1U PowerEdge 1950
♦ The 2U PowerEdge 2950 and 2970
♦ The 4U PowerEdge R900
♦ The 6U PowerEdge 6850 and 6950
♦ The PowerEdge 1955 Blade Server
Figure 2.1 Servers on the compatibility list come in various sizes and models.
The model selected as the platform has a direct effect on server configuration and scalability, which will in turn influence the return on investment for a virtual infrastructure.
Calculating the Return on Investment
In today's world, every company is anxious and hoping for the opportunity for growth. Expansion is often a sign that a company is fiscally successful and in a position to take on the new challenges that come with an increasing product line or customer base. For the IT managers, expansion means planning and budgeting for human capital, computing power, and spatial constraints.
As many organizations are figuring out, virtualization is a means of reducing the costs and overall headaches involved with either consistent or rapid growth. Virtualization offers solutions that help IT managers address the human, computer, and spatial challenges that accompany corporate demands.
Let's look at a common scenario facing many successful medium-to-large business environments. Take the fictitious company Learn2Virtualize (L2V) Inc. L2V currently has 40 physical servers and an EMC fibre channel storage device in a datacenter in St. Petersburg, Florida. During the coming fiscal year, through acquisitions, new products, and new markets L2V expects to grow to more than 100 servers. If L2V continues to grow using the traditional information systems model, they will buy close to 100 physical servers during their rapid expansion. This will allow them to continue minimizing services on hosts in an effort to harden the operating systems. This practice is not uncommon for many IT shops. As a proven security technique, it is best to minimize the number of services provided by a given server to reduce the exposure to vulnerability across different services. Using physical server deployment will force L2V to look at their existing and future power and datacenter space consumption. In addition, they will need to consider the additional personnel that might be required. With physical server implementations, L2V might be looking at expenses of more than $150,000 in hardware costs alone. And while that might be on the low side, consider that power costs will rise and that server CPU utilization, if it is consistent with industry norms, might sit somewhere between 5 and 10 percent. The return on investment just doesn't seem worth it.
Now let's consider the path to virtualization. Let's look at several options L2V might have if they move in the direction of server consolidation using the VI3 platform. Since L2V already owns a storage device, we'll refrain from including that as part of the return on investment (ROI) calculation for their virtual infrastructure. L2V is interested in the enterprise features of VMotion, DRS, and HA, and therefore they are included in each of the ROI calculations.
The Price of HardwareThe prices provided in the ROI calculations were abstracted from the small and medium business section of Dell's website, at http://www.dell.com. The prices should be used only as a sample for showing how to determine the ROI. It is expected that you will work with your preferred hardware vendor on server make, model, and pricing while using the information given here as a guide for establishing the right hardware for your environment and budget.
Each of the following three ROI calculations identifies various levels of availability, including single server failure, two-server failure, or no consideration for failover. All of the required software licenses have been included as part of the calculation; however, annual licensing fees have not been included since there are several options and they are recurring annual charges.