The ROI from virtualizing tactical applications is driving by the consolidation in the number of physical servers needed once tactical workloads are virtualized. However, when virtualizing Tier 1 or business critical applications, it is likely that significant consolidation in the number of cores per workload is not possible – leading to the requirement to find a new way to cost justify these projects.
, • • 0 Comments
With the release of vSphere 4.1, VMware has added to their Dynamic Resource Load Balancing (DRLB) suite of tools that I hinted at in my post on Dynamic Resource Load Balancing that I wrote last week as well as providing new memory over commit and other functionality. In essence, vSphere 4.1 is more than a point release, this update includes many features that aid in security, reliability, and is a direct response to customer requests.
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.
• • 0 Comments
Microsoft is bringing its strongest assets – the installed base of its key products in the enterprise, and its library of commercial and custom built applications (and their associated developer communities) along with compelling new technologies like Server App-V to the virtualization and cloud fight. Leveraging Azure and App-V along with these existing enterprise assets makes Microsoft into a much more potentially formidable competitor to VMware than Microsoft is today based solely upon Hyper-V.
• • 0 Comments
During the Virtual Thoughts podcast on 6/29/2010, the analysts discussed various hardware aspects of virtualization trying to determine if the hypervisor was to move into the hardware? and if so how much of it? as well as whose hypervisor? and lastly such a move part of any business model?
Virtual Thoughts is a monthly podcast that looks at the entire scope of virtualization to discuss new trends and thoughts within the virtualization and cloud communities.
This weeks podcast started with a discussion of TPM/TXT and the boost it gives to virtualization security. Since TPM/TXT is based in the hardware and provides a measured launch of an operating system, the next logical discussion was on whether or not the hypervisor would be placed into the hardware?
During the Virtualization Security Podcast on 6/22, Steve Orrin of Intel and Dennis Morreau of RSA joined us to discuss the impact of Intel Westmere chips built-in Trusted Platform Module (TPM) and Trusted Execution Technology (TXT) on Cloud and Virtualization Security. TPM is not all that new, but TXT’s usage in virtualization security is new. Both together can form a hardware root of trust for the virtual environment.
At the moment however, these technologies are limited to just providing a secure launch of a well known hypervisor within the hardware. As such they have not been extended to the virtual machine. TXT however solves a very important issue that at the time the book VMware vSphere and Virtual Infrastructure Security was written had theoretical solutions, I speak of Blue Pill style attacks. There were rumors of Hyperguard or Guard Hype tools becoming available, but they are only research projects. TXT on the other hand, offers protection from Blue Pill style attacks.
Virtual Thoughts Podcast the Rebirth, Join us Tuesday 29th June @ 7:00pm (BST), 2:00pm (EST), 11:00am (PST)
• • 0 Comments
Supporting Tier 1 applications on VMware vSphere requires real time and granular response time and latency instrumentation of the virtual and physical infrastructure. Virtual Instruments Virtual Wisdom complements the instrumentation provided by VMware by providing individual transaction level visibility into the SAN layer of the virtual infrastructure.
There is a cardinal rule that we should all know about, especially for those of us who have spent a lot of time developing kickstart scripts for automated builds of the VMware hosts in your environment, that you do not use windows word editors like Notepad or WordPad when working with Linux files. If you use notepad to edit Linux files it will add unwanted line feeds (LF) to the file which may cause the file to be misinterpreted. If you must use Microsoft Windows as your client OS use Microsoft WordPad which does not modify the file in this way.