Virtualizing business critical systems requires that a layer of virtualization management solutions be added to the virtualization platform. Virtualization management solutions in the areas of virtualization security, virtualization configuration management, virtualization service and capacity management, virtualization service and capacity management, virtualization provisioning and lifecycle management and backup and recovery should be added to the platform.
With the release of vSphere 4.1 there have been some great enhancements that have been added with this release. In one of my earlier post I took a look at the vSphere 4.1 release of ESXi. This post I am going to take a look at vSphere 4.1 availability options and enhancements. So what has changed with this release? A maximum of 320 virtual machines per cluster has been firmly set. In vSphere 4.0 there were different VM/Host limitations for DRS as well as different rules for VMware HA. VMware has also raised the number of virtual machines that can be run in a single cluster from 1280 in 4.0 to 3000 in the vSphere 4.1 release. How do these improvements affect your upgrade planning?
• • 1 Comment
Virtualization Security, Configuration Management, Service and Capacity Management, Provisioning and Lifecycle Management, and Backup/Recovery are essential functions that must be added to a virtualization platform when virtualizing business critical applications. VMware vSphere is clearly the market leading and most robust virtualization platform – and clearly the virtualization platform most suitable as the foundation of a virtualization system designed to support business critical applications. However, the virtualization platform must be complemented with third party solutions in these areas in order to create a system that can truly support business critical applications in an effective manner.
When you hear the term “host” when talking about virtual environment, what is the first thing you think of? For me, the answer is simple, a host is an appliance. For years now I have been standing on my soap box and preaching the power and fundamentals of automation in building and configuring your virtual environment. I came across a thread on the VMware VMTN Community Forum where a concerned individual was in a position that he was going to have to rebuild his host from scratch. What he did to get himself into this position was to run a hardening script on the host and then the host became broken and unusable. This person was concerned that he did not have a backup of the host and was looking for a way to rollback.
When you read books on virtualization, cloud computing, security, or software product sheets a common word that shows up is Policy. Tools often claim to implement Policy, while books urge you to read or write your Policy. But what does Policy imply?
Webster (webster.com) defines policy as:
1 a : prudence or wisdom in the management of affairs b : management or procedure based primarily on material interest
2 a : a definite course or method of action selected from among alternatives and in light of given conditions to guide and determine present and future decisions b : a high-level overall plan embracing the general goals and acceptable procedures especially of a governmental body
When you read policy in product literature and books we are looking at definition number 2 and often a over b. But what does this mean to those who administer and run virtual environments or make use of cloud services?
Catbird and HyTrust have teamed up to deliver a product that provides front-end access and compliance control for well understood actions via HyTrust, for all other actions, including intrusions, Catbird Security provides compliance control, firewall, IDS, and IPS. In other words, proactive security via HyTrust and reactive security via Catbird.
Unless you have been on vacation or hiding under a rock then you have heard the latest buzz in the industry that vSphere 4.1 has been released. There have been a lot of blog posts on the topic already. You can find one example here, here and what we at virtualizationpractice.com posted here. The thing I want to hit on for this post is the fact that this release will be the last release for full version of ESX. Moving forward on any new releases of ESX will be strictly ESXi. Anyone that knows me over the years knows that I have not really been a big fan of getting rid of the full version ESX Server. Call me old school and the fact that I have spent a great deal of time developing the automation used in the environments that I have supported over the years and have been really happy with what I was able to accomplish via kickstart and bash.
I just finished writing all the content for my next book entitled VMware ESX and ESXi in the Enterprise: Planning Deployment of Virtualization Servers (2nd Edition) which continues the discussion on Dynamic Resource Load Balancing (DRLB). DRLB is the balancing of virtualized workloads across all hosts within a cluster of virtualization hosts without human intervention. This is the ultimate goal of automation with respect to virtualization and therefore the cloud. In effect, with DRLB the virtualization administrators job has been simplified to configuration and trouble shooting leaving the virtual environment to load balance work loads on its own.
• • 1 Comment
Which is better – Virtual Desktop Infrastructure or Presentation Virtualization? If you have, say, a Citrix XenApp PV solution – you may may be tempted at the reduced cost per license of VDI – XenDesktop appears to be almost half the cost per user than XenApp. Maybe you’ve a VMware vSphere back-end and the thought of having one platform to manage is appealing. Maybe you have a different solution – perhaps Quest’s vWorkspace or Ericom’s Webconnect and are wondering what all this fuss about moving between PV and VDI is all about?