Learning ESX, Part One
Lately I've been doing a lot of research on virtualization in the data center. My specific research deals with the innards of VMware VI. We are in the midst of going virtual whole hog and I'm giving myself a crash course on the proper way to do, well, everything. Yes, we've been using virtualization tools for about three or four years now, but we are changing to moving our production servers to this platform, which requires a different approach than the ad hoc test/dev/desktop use we've seen.
Along the way I've picked up a few tips I thought might be useful for others out there that are either contemplating it or in the midst of setting up their first ESX server ( Or VI infrastructure). Because VMware has a lot of moving parts it seems it can be easy to get a little lost. Planning is key to implementation success (isn't it for everything?). Speaking of planning, I found this great thread on Ars Technica about the Biggest Mistake You've Made with a Virtualization Deployment. Very interesting, and it mentions many of the items I have been reading about.
So for starters, what is the best method of deploying an ESX server? Many folks in the communities believe that a scripted install is the best way to do it. Why scripted, even for just a few hosts? Well one good reason is you'll install it the same way on all your hosts. Second good reason, it'll force you to learn how ESX installs, what the defaults are, and how those defaults can be improved upon. For example, disk partitioning. If you just accept the defaults you might outgrow your space. There are several posts on the subject, here's one at VM /ETC on ESX host partitions. It's also worth noting that if you use the Ultimate Deployment Appliance (UDA) to deploy ESX, Mike Laverick has set default partitions that expand on the default and use many of these recommendations. Read His instructions if you want to use UDA as a PXE server to deploy ESX using a script. Using a PXE server from a virtual appliance is not too difficult and it takes the script theory one better, by giving you a repeatable deployment method that requires no media in the drive!
OK, so there is one issue with disk alignment and partitions. The UDA will create a VMFS partition for you, however it won't be aligned. Read the Recommendations for
Aligning VMFS Partitions from VMware to understand the issue and what to do about it. If you create a VMFS parition using the VI client, it will be automatically aligned. So that is my recommendation, use VI client to create VMFS partitions on the ESX host if needed, don't script the install of those type of partitions. In the UDA appliance I deleted the section of the script that created a VMFS partition during install.
That completes our first two tips, script your installs (possibly by using the UDA) and align your VMFS partitions!
Next post I will talk about networking. I've been following Ken Cline's multiple post article The Geat vSwitch Debate and in his next installment he will conclude with his recommendations. I'm not going to bother trying to explain virtual switching, just read Ken's articles!



