On 4/12/2012, EMC in conjunction with technology partners VMware, Microsoft, Cisco, Brocade, Citrix and Intel announced EMC VSPEX. EMC VSPEX is an specification framework that allows multiple vendors to participate in providing “standard” building blocks for virtualized data centers and private clouds – targeted at accounts who need less than 250 virtualized servers and/or 2000 virtualized users (VDI) and delivered exclusively through EMC/VMware/Cicso/Microsoft/Citrix partners. The goal of this initiative is to provide the mid-market with cost effective, pre-certified, pre-integrated solution sets and leverage standard building blocks from leading vendors. In other words this is VCE/vBlock for smaller companies delivered through the distributor and VAR channels of the respective vendors. Continue reading EMC VSPEX vs. vBlock, or NetApp FlexPod. Can VMware VARs “Refuse” the Offer?
Ever since VMware announced the virtual memory based pricing (the VTAX), many organizations have investigated the question of whether they should cease to rely solely upon VMware vSphere as their virtualization platform. These investigations have been motivated by a desire on the part of upper management in many organizations to protect the organization from what they perceive as the potential for increased licensing costs, if the organization pushes density far enough to have to purchase extra vSphere licenses just to address the configured virtual memory limits in each vSphere license.
As a result of these licensing concerns, financial managers have said to their technical staff (the team that runs vSphere), “Look we are not switching now, we are not even adding something else now, but if we do decide to add something else, please investigate the alternatives and tell us what we would pick as our second virtualization platform”. This is of course a very common sense and highly recommended approach in a situation like this. It is essential to know what your alternatives are, even if you do not want to act upon one of them right now.
As organizations have embarked upon these investigations that they have found the following things:
- Since the last time that many organizations have looked (the technical staff at most enterprises is very happy with vSphere and has had no motivation to look until they were prodded to do so by their financial managers), competing products from Microsoft (Hyper-V), Red Hat (KVM) and Citrix (XenServer) have gotten much better. VMware vSphere still retains a lead in functionality, performance, and scalability, but that lead is narrowing.
- The competing products are less expensive. In some cases much less expensive, and in some cases less expensive enough to matter, but not so much so as to be an overwhelming consideration.
The Virtualization Management Stack Challenge
As soon as organizations come up with a second potential virtualization platform, they then encounter an even more difficult problem that choosing the second virtualization platform. The problem is how to manage two virtualization platforms instead of one. This is a really important consideration because the last thing you want to do is make a mess of managing your virtual environment so that it is just as difficult and expensive to manage as the physical environment that you are moving away from. The primary cause of the mess on the physical side was that most organizations built their management stacks organically over time, and bought overlapping and redundant products for each of the physical environments and the software that ran on them. So the last thing you want to do is repeat this mistake and build two management stacks if you have two virtualization platforms.
Approaches to Cross-Virtualization Platform Management
There are three approaches that you can take to having one cross platform virtualization management strategy:
- Assemble as management stack from best of breed third party solutions that support both of your virtualization platforms. For example, performance and capacity monitoring vendors like VKernel (now part of Quest Software), SolarWinds, VMTurbo, and Zenoss all support multiple virtualization platforms. Application Performance Management vendors like AppDynamics, New Relic, BlueStripe, Correlsense, and ExtraHop Networks tend to be agnostic of the underlying virtualization platform. Most backup vendors like Veeam support more than one hypervisor as well.
- Standardize upon Microsoft SCOM as your management console, and then use plug-ins to SCOM (management packs) to support other virtualization platforms. For example you can use the Veeam nworks product to manage your VMware environment from within Micrsosoft SCOM. You can use the BlueStripe plugin to SCOM to manage all of the applications deployed across both VMware and Hyper-V virtualization platforms.
- Use Hotlink, to extend the reach of vCenter to Hyper-V, KVM, and XenServer. The balance of this article will focus upon this approach.
Hotlink SuperVISOR for VMware 1.5
Hotlink is announcing today a new version of its SuperVisor solution. Hotlink 1.5 allows you to manage vSphere, Microsoft Hyper-V, Red Hat KVM, and Citrix XenServer all from within you vCenter console. Additionally, Hotlink 1.5 adds the following extremely useful functinality:
- Snapshot Manager – Administrators can create, utilize, and manage cross-platform snapshots inside the VMware vCenter console – providing a single point of management for heterogeneous virtual machines
- Template Manager – Users are able to create and deploy a single template across all target hypervisors, eliminating the time-consuming and inefficient process of building and maintaining platform-specific virtual machine templates
- Homogenous Live Migration – VMware vCenter is now extended to provide live migration (e.g. vMotion) of Hyper-V, XenServer, and KVM virtual machines within homogeneous clusters – enabling the robust VMware management capabilities to be utilized for cross-platform, critical workloads
Microsoft SCOM vs. vCenter/Hotlink
One of the huge differences between the Microsoft virtualization management strategy and the VMware virtualization management strategy is that Microsoft has an open management pack architecture that lets anyone add value to SCOM, and Microsoft will partner with vendors that add value to SCOM at a sales and marketing level, while VMware has neither the open and extensible partnering architecture, nor the willingness to partner with management vendors who add value to vSphere.
Hotlink is now in the interesting position of filling this gap for VMware even if VMware does not want it filled. The reason for this is that there are a large number of third party products that use the data from vCenter as the source of the information upon which they build their management functionality. Hotlink now adds data from Hyper-V, KVM, and XenServer environments to the data that vCenter provides to the entire VMware management ecosystem. Therefore Hotlink has effectively made the entire VMware management ecosystem into a cross virtualization platform play. Needless to say, this is wonderful for people who love vCenter. Interestingly enough it also opens the door to be able to use VMware’s own management products like vCenter Operations across other virtualization platforms as vCenter Operations also relies upon the vCenter API data.
Tiering Virtualization Platforms
You tier your storage for very good reasons. Those reasons have to do with matching the cost and the performance of the storage with the requirements of the workloads using the storage. The same thing makes sense when it comes to virtualization platforms as long as you do not drive yourself crazy trying to manage the resulting complexity. The great news with Hotlink is that Hotlink allows you to, for example, add Microsoft Hyper-V to your VMware vSphere environment, and keep using the same management products.
The graph below shows the result of such an approach at one Hotlink customer. Notice that the total number of hosts rises significantly over a 6 year period. However, the number of vSphere hosts goes down as they get reserved for only the most mission critical workloads, and all of the tactical workloads go to Hyper-V.
The economics of this are also very interesting. In the graph below, the top line is what the customer would have spent had they deployed all of the incremental workloads on vSphere. Since the customer in this example is a large Microsoft customer, Hyper-V is essentially free to this customer. So as workloads are deployed on Hyper-V instead, savings in the millions of dollars a year result.
If you are going to have more than one virtualization platform, you should not have more than one virtualization management stack. Hotlink SuperVISOR lets you use the market leading virtualization console (vCenter) to manage other virtualization platforms like Hyper-V, KVM, and XenServer. Furthermore it extends the vCenter API data used by third party management vendors with data from these other platforms, turning Hotlink into the management data broker for the virtualization management industry. Finally Hotlink allows for easily managed tiering of virtualization platforms and the fitting of platforms to their appropriate price/performance use cases
Cloud services are for the most part extremely attractive because they let the provider (vendor) of the cloud service focus upon what they do best (manage some set of layers in the hardware and software infrastructure), and let you focus upon what you do best (typically concern yourself with your applications and your data). Great examples of cloud services that promote agility include simple IaaS services like those available from Amazon or Rackspace, a PaaS service from Engine Yard or Heroku (now part of SalesForce.com), a SaaS service like SalesForce.com, or a storage service like DropBox. For a lot of use cases for for a lot of customers, these services are the computing equivalent of “Look Ma, no hands” in the sense that they deliver what you need with little effort on your part. Continue reading Can Your Cloud Impede Your Agility?
By Greg Schulz, Server and StorageIO @storageio
IO, IO, it’s off to storage and IO metrics we go shifting gears a bit from the recent four part series around SSD topics for physical and virtual environment. A while back I did a post about Why VASA is import to have in your VMware CASA along with another piece about Windows boot IO and storage performance impact on VDI planning. Among other things those two pieces have in common is a theme around the importance of storage and IO metrics that matter. Continue reading IO IO it is off to Storage and IO metrics we go
There has been a lot of buzz and coverage about Windows 8 since its consumer preview. There will be some very cool features with this release and one feature that really stands out with me is that Microsoft added an additional supported processor type in that Windows 8 will run on Intel, AMD and now ARM based processors. That gives Windows 8 the ability to run on desktops as well as mobile phones and tablets.
Think about that, Microsoft has now expanded its desktop presence by adding in the mobile devices and Windows 8 will bring the Metro Interface across all desktops, phones and tablets. Can this be something that will enhance your overall computing experience as well as presenting another option for VDI? Continue reading Windows 8 – Extending the Desktop to the Mobile World
One of the areas where VMware vSphere has had a large advantage over Microsoft Hyper-V has been in the architecture and capabilities of the VMware vSphere Virtual Switch. The most important of these capabilities has been the ability to designate one or more ports on the switch as promiscuous or mirror ports. These ports make a read only copy of all of the data flowing through the switch available to whatever virtual machine is sitting on that port. This is an essential capability for many security products and also performance management solutions like those from ExtraHop Networks that rely upon deep packet inspection to work. Continue reading The Windows Server 8 Hyper-V 3 Extensible Switch