Almost 7 months after the release of vSphere 4.0 (and its Update 1), VMware finally publishes a Hardening Guide that can be used to secure every aspect of the virtual infrastucture.
It’s not the final version of the document but just the first, public draft (internally called Rev B). Nonetheless every VMware administrator is highly encouraged to download and check it.
The guide is divided in five sections (excluding the introduction):
- Virtual Machines
- Console OS (for ESX)
VMware didn’t provide a timeframe for the final release but welcomes feedbacks from the community.
It’s no secret that I am not a fan of Microsoft Virtualisation, they seem to be constantly two years behind VMware and are still taking an approach of delivering the hypervisor using a bloated hypervisor based on an aging kernal. However, it won’t always be thus, through acquisition and sheer determination Microsoft will produce something that’s worthwhile – they always do. When Novell had the best Directory Service out there Microsoft ruled the world with Active Directory, when Lotus were beginning to get an edge in the market with Notes, Microsoft made Exchange so good we didn’t care that Notes did all the database stuff and was good at replication too. In the meantime its nice to have an answer to those people that ask “Why not Microsoft?”, so here is a good guide from WindowsITPro to understanding the offerings as they currently stand.
Having read Microsoft’s document I can draw the following conclusions in summary:
- Microsoft is now using the term ‘OSE’ (Operating System Environment) to describe the ‘thing’ that gets a licence applied to it – this means any entity that runs a Microsoft OS – this could be a physical server, blade or partition or a virtual server or image that is running.
- Use terms for the software licence(s) specify the number of instances of the software that you may run at a particular time rather than the numbers of copies of software that is installed. Each software licence allows you to create and store any number of instances of the software on any of your servers or storage media.
- Microsoft has clarified the 90-day rule and points back to Application Server Licence Mobility guidance
NOTE: Still makes me laugh to see Microsoft announcing amazing new features that VMware had in v2.5!
From the (Very Microsoft Biased) Hypervoria.com site
Managing how you share CPU, memory and storage resources is the key to avoiding performance problems in any virtual environment. Hyper-V environments are no different. This paper will cover some lessons learned in years of experience managing capacity resources in a VMware environment and how those same techniques can be applied to a Hyper-V environment.
Since many of you are already familiar with VMware, we will be comparing Hyper-V to VMware. We will cover how to manage resources (CPU, memory storage and disk I/O) to obtain the maximum safe VM density, how to avoid performance bottlenecks, and how to compute how much capacity there is to add virtual machines for each host and cluster.
When I see sites I like, I like to promote them – the presentation content (Visio and PPT) from Xtravirt’s Presentation Packs are really useful.
Site Link is http://xtravirt.com/