Coming on the heels of VMware’s acquisition of Nicira, Oracle announced today that it is acquiring network virtualization vendor Xsigo Systems for an undisclosed amount.
I was reading through a recent article about the new Java 7 release, which contradicts Oracle’s current support statement with respect to licensing. The License from Oracle exclusively states Java 7 is only supported on those hypervisors Oracle currently supports: Oracle VM, VirtualBox, Solaris Containers, and Solaris LDOMs except where noted. That last phrase is rather tricky, so where do we find such notes. Is the noted the support document stating that they support Oracle products within a VMware VM? Or is it somewhere else in the license? This leaves out all major hypervisors: Citrix, VMware, and Microsoft. If you cannot find a note saying things are supported, somewhere.
This implies quite a bit for the future of Java support within most PaaS environments being built today. In essence, they cannot upgrade to Java 7. Which means they may fall behind. This would impact OpenShift, Amazon, Google, CloudFoundry, SalesForce, and others.
EMC, the majority owner of VMware, has agreed with the Department of Justice not to acquire 33 Virtualization Patents from Novell as part of a side-transaction in the acquisition of Novell by Attachmate. The Statement from the Department of Justice sheds significant light on the deal that had been struck between Novell and a newly-created company formed by Microsoft, EMC, Apple, Oracle to acquire a portfolio of patents for $450M, and the anti-trust threat that the Department of Justice saw to the Open Source community. And whilst the spotlight has been on Microsoft’s role, it seems that the role of EMC in seeking to acquire Virtualization patents was at least as concerning to the Department of Justice.
Cloud.com had lined itself up with Citrix by using only XenServer in the commercially-licensed version of its IaaS product, and now is being used by Citrix to ensure OpenStack supports XenServer (which it doesn’t at the moment), presumably to keep Red Hat’s KVM under control and VMware out. We’ve also been trawling through the available OpenStack documentation to understand why NASA thinks its cloud is more scalable than Eucalyptus. It seems to be all to do with how the state information is passed amongst the various servers that make up the system. GPL-based Open Core models break down when you move to multi-vendor foundations because the cross-licensing of IPR under GPL immediately infects the recipient codebase, and precludes commercial licensing of the resulting combined work. The result is that the GPL Open Core business model doesn’t work in the same way, and both Eucalyptus and Cloud.com cannot apply their current business model in these multi-vendor foundations. It is a big blow for Eucalyptus. They have turned their biggest potential customer into a massive and credible competitor, built in their own image (only – at least from a PR perspective – much more scalable).
In OpenStack the API is implemented in a separate service which translates external http requests into commands across the internal message bus, and so it looks (on the face of it) possible for someone (preferably Oracle) to implement the Oracle DMTF submission as a separable new API server module without disrupting the OpenStack architecture. In OpenStack the API is implemented in a separate service which translates external HTTP requests into commands across the internal message bus, and so it looks (on the face of it) possible for someone (preferably Oracle) to implement the Oracle DMTF submission as a separable new API server module without disrupting the OpenStack architecture.
When we put a .NET application on Windows on Hyper-V (or a Java application on Linux on ESXi) we are actually virtualizing twice. Can we 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. Oracle is taking the lead in this area with JRockit VE JVM. There is no VMware support, the only hypervisor it supports is Xen, or more precisely Oracle VM. it only comes bundled only with an Application Server, namely Oracle WebLogic Suite Virtualization Option. The entire stack inside the virtual machine is in “User Mode” in other words the JVM and the drivers are all in the same memory address space and you don’t need to switch contexts into Kernel Mode in order to perform I/O or network access. Does VMware have a strategic initiative (or even a skunkworks) to engineer a similar bundle for its SpringSource runtimes? Or are they just concentrating on scaling out with as per the Google announcement?
Quite a bit has gone on in our industry in the last year. While this is not intended to be a comprehensive review of all that has occurred, we hope that we have captured the important events that have shaped virtualization and cloud computing.