Buying the Managed Objects assets of Novell would give VMware a credible entry into the Business Service Management realm with product assets that could compete head to head with those from CA, IBM, HP and BMC – especially on the VMware platform. However there were significant issues with BSM as implemented by all of these vendors, and acquiring a BSM product set would not in an of itself address those all of those (Integrien helps with root cause) issues. The real answer here remains a virtualization and cloud competent performance assurance capability which should be attainable without recreating the baggage of BSM.
• • 2 Comments
Desktop virtualization often focuses on solutions provided by Citrix and VMware. Quest’s vWorkspace is an enterprise ready solution and its partnering with the likes of Virtual Computer offer customers looking to reduce the cost and simplify their desktop service implementation.
There has been a lot of noise about a negotiations between VMware and Novell, rumors are that it regards the purchase of the SUSE division, now firstly every thing that follows is pure supposition on my part, I have no insider knowledge. now mike has put forward one argument on why a VMware purchase of Novell SUSE assets make very good corporate sense. However I put another idea into the fray.
The Virtualization Security Podcast on 9/16 was the first in a series of Virtual Desktop Security discussions we will be having. The special guest panelist was Bill McGee from Trend Micro who helped us to understand their implementation of Deep Security 7.5’s Anti-Virus and Anti-Malware (AV collectively) within the virtual desktop.
Trend Micro’s product makes use of enabling technology within vShield Endpoint to provide offloaded AV and Anti-Malware scanning of virtual machines using only one set of rules and one VM to do the actual scanning. Removing the per VM rule set and processing that currently takes place within the VM.
VMware may buy SUSE from Novell for a host of reasons, one of the most important of which may be that it gets access to Mono and thereby creates a .NET cloud to compete with Microsoft Azure. Paradoxically, we expect that Microsoft will want this to happen.
Anticipating the formal announcement was a widely leaked report that View 4.5 would ship without Virtual Profiles, the user profile management solution that VMware OEMed from RTO Software in fall 2009. VMware finally confirmed that the leak was correct on the first day of VMworld 2010, but even then held back from announcing its interim solution until after the formal product launch. Then rather than simply offer View customers a copy of Virtual Profiles as a standalone product, VMware chose instead to partner with Liquidware Labs to enable them to offer Liquidware Labs’ ProfileUnity to View customers at a substantial discount. While VMware’s position is that Virtual Profiles will ship with View 4.5 at some point in the future, the decision to offer ProfileUnity instead did nothing to address the concerns of potential customers, especially those who might finish up paying twice for a profile management system. The only good news for View customers is that ProfileUnity’s agent-less and database-less architecture should make the future migration to Virtual Profiles a simple matter when the time comes to move.
VMware dominates the enterprise virtualization platform business with vSphere, and is poised to create a vSphere compatible public cloud ecosystem around vCloud. Layering Management software on top of these platforms is a logical progression up the value stack, as is layering an applications platform (vFabric) on top of vSphere and vCloud. VMware’s end user computing strategy seems to be too tied to VDI to be able to break out of the fundamental limitations associated with this approach, and will likely leave the larger question of how to manage the next generation desktop to the previously mentioned startups and perhaps Symantec.
There used to be a FedEx commercial that had a saying “when it just has to be there overnight”. What if we did a play on words and changed the saying to work with Fault-Tolerance and or High Availability. The saying would be something like “when it just has to remain running overnight”.
There seem to be three styles of IO Virtualization (IOV) taking place within the virtual environment. At VMworld, the IO Virtualization companies were out and talking to people about their wares, products, and approaches to IO Virtualization. These three methods are:
* Converged Network Adapters used within Cisco UCS, HP Matrix, etc.
* Attached IOV top of rack devices such as the Xsigo Device
* PCIe Extenders
Each of these provide unique benefits to your virtual environment but which to use? First, we need to know what each of these approaches brings to the table.