VMworld is clearly the largest dedicated virtualization conference, and yet from an Open Source perspective it is slightly disappointing because the VMware ecosystem naturally attracts proprietary software vendors, and also some of the more interesting activities in Open Source are through multi-vendor foundations which do not have the same marketing budgets as vendors themselves.
Nevertheless, there are a number of key Open Source players, and some interesting smaller players, represented at VMworld.
Oracle (who by virtue of the acquisition of Sun owns Java) announced late on Thursday August 13th that it has filed suit against Google for infringing upon copyrights and patents related to Java. “In developing Android, Google knowingly, directly and repeatedly infringed Oracle’s Java-related intellectual property. This lawsuit seeks appropriate remedies for their infringement,” Oracle spokeswoman Karen Tillman said in a statement. The full complaint may be found here.
What exactly is Microsoft going to do to counter VMware, and how are they going to do it? We have published numerous articles that have laid out how VMware is pursuing strategies that have the strong potential to significantly erode Microsoft’s role in the systems software market. To summarize, here is the list of VMware initiatives:
The previous post Secure Mutli-Tenant Virtualization – How to get there?, was only concerned with Infrastructure as a Service however the new announcement from VMware SpringSource and Google leads to one of the first Platform as a Service that has simplified the motion of applications between different cloud providers, provided the basis for the application exists within the environment. That basis is Spring. Applications built on Spring can now run on Google AppEngine, VMware Clouds such as VMforce, VMware vSphere infrastructures, and other participating clouds.
This is a Wow! moment for the adoption of Java based PaaS Cloud as any real kind of interoperability across these clouds has been lagging by a large margin. For PaaS and Applications built using the Spring PaaS a solution has been found.
“Virtual Machine” seems to have two distinct meanings:
- Sysadmins deal with “system” virtual machines, i.e. guest operating systems running on a VM host.
- The application programmer generally deals with a “process” virtual machine, such as
- the Java Virtual Machine
- the Common Language Runtime (CLR) for .NET
The “process” virtual machine may be running on an operating system which (in turn) may be running as a “system” virtual machine on a VM host. So, in some sense when we put a .NET application on Windows on Hyper-V (or a Java application on Linux on ESXi) we are actually virtualizing twice. The question arises as to whether we can actually virtualize only once, by putting the CLR or the JVM directly on the VM Host. In this action of course we remove the operating system.
Virtualization of servers, the initial business of the VMware, and still the source of the lion’s share of VMware’s revenue is about injecting a layer of software between the hardware in the data center and the operating systems as a result of this additional level of layering providing a set of additional set of functions (easier backup, easier disaster recover, flexibility, etc.). This business is entirely independent of the operating systems and the applications running on those operating systems.