There’s a lot of good information being shared out there! With all due credit to the original authors, here’s a few links that I found particularly interesting or useful. I hope you agree!
- The VI Team Blog posted a list of interesting things in Update 2. They identify things like Enhanced VMotion Compatibility (EVC) and monitoring and availability enhancements. For example, did you know that VM failure monitoring is now fully supported and not experimental? One thing that caught my eye when I first announced Update 2 was VSS support. What I hadn’t really noted about this was the fact that this extends into the application layer, meaning that VSS-aware applications will be quiesced for VCB-based backups. This brings application data consistency to VCB-based backups, and this is a big deal.
- And while we’re discussing the VI Team Blog, have a quick look at part 1 and part 2 of their tips for deploying VI. The discussion of Fibre Channel path selection policy with active/passive storage arrays is particularly helpful.
- Rich over at VM /ETC brought some interesting facts to my attention regarding the free version of ESXi in this post. I was not aware, for example, that the Remote CLI was read-only with free ESXi. Very interesting, and quite useful.
- Duncan at Yellow Bricks has also been pumping out some very helpful information, with an update on HA advanced options and a pointer to a document describing what happens if VirtualCenter crashes. One of the HA options that caught my eye was an option that allows VMotion interfaces to be used for HA. This means that we can easily provide additional HA redundancy simply by configuring VMotion interfaces. Handy!
- Chris Wolf brings to light information on PXE booting ESXi, and in so doing discusses the idea of the “stateless hypervisor.” This is an idea that is gaining a lot of ground, also being the subject of the release of a utility designed specifically around that very idea (but for ESX, not ESXi). When I design a VI environment, I’m already treating the hypervisor as mostly stateless; all the data and “important” information is stored on the SAN. To fully embrace the idea of a stateless hypervisor, we also need to incorporate auto-configuration.
That’s it for now. If any readers have any interesting links they’d like to share, please do so in the comments below. Thanks!