In the industry, OpenStack is seen as very hard to implement. Considering this, I began to think that most people who deploy OpenStack try to bite off too a large chunk of OpenStack at one go, to implement it all instead of just what they need. OpenStack is a cloud management platform, not the hypervisor, so perhaps we can take some lessons from how we installed VMware products when we just started out. We still implement things using the same patterns for vSphere. We should revisit OpenStack with this history in mind.
Articles Tagged with VMware vSphere
As part of the revised Citrix focus on app and desktop delivery, the XenServer hypervisor is gaining increased attention within Citrix. Is it too little too late, or will IT shops find a way to get over the betrayal they felt when Citrix seemed to abandon XenServer?
Soon the backup power will be available for our new datacenter and the redesign to make use of VMware vCloud Suite is nearing completion. Soon, our full private cloud will be ready for our existing workloads. These workloads however now run within a XenServer based public cloud. So the question is, do we stay in a poorly performing public cloud (mentioned in our Public Cloud Reality series) or move back to our own private cloud? As the Clash put it “Should I Stay or Should I Go Now.”
One of the companies and technologies to watch is Hotlink with its Cross-Platform Management Technology (winner of Best of Show, VMworld 2012). If you have not heard of this before, I think you will in the near future. This technology allows you to use VMware’s vCenter Server to manage and control all major hypervisors and public clouds to include VMware vSphere, Microsoft Hyper-V, Citrix XenServer, Red Hat Enterprise Linux (KVM), CloudStack, and Amazon EC2, all from within VMware vCenter.
DRS is one of the most useful and interesting features of VMware vSphere (to be more specific – feature of versions of vSphere from Enterprise on up). DRS is useful because it prevents workloads (VM’s) that are consuming more than the expected amount of resources, from potentially harming the performance of their neighbors in the same host with this “excess” resource consumption. DRS is interesting because the idea of dynamically balancing the load of a system in order to ensure the performance of the critical workloads running on that system is something that was taken for granted in the days of the mainframe, but has not as yet been well implemented on distributed Intel architecture systems.
In The ROI for Server Virtualization with Business Critical Applications, we showed an example of how the savings from server (specifically core) consolidation might not be as large when one is virtualizing business critical applications (where the physical servers were appropriately sized in the first place) is it is with tactical applications (where the one server per application resulted in massive over-provisioning). At the end of that analysis we also pointed out that the business critical case did not include the other “extra” products that would need to be a part of a business critical application virtualization project. This post proposes a reference architecture for the entire suite of solutions that will be required to virtualize business critical applications. We are going to build this example around VMware vSphere as VMware has the broadest level of third party support in terms of vendors who provide the solutions required to fulfill the requirements of the reference architecture.