VMware do we go from here?

Perhaps it's time the cloud pioneers snap up Docker

Storage Architect VMWorld Europe was held last week in Barcelona. We saw the release of vSphere 6.5, plus a suite of other products and enhancements to the core platform. There was also the announcement of a partnership with AWS, which had many (including myself) scratching their heads as to exactly what it meant. So where is VMware headed?

Core focus

One thing that has become apparent is VMware's focus on a core set of future products that they see as being revenue growth areas for the future. These include NSX (virtualised networking/security) and Virtual SAN (storage). The networking piece is reasonably clear (although the challenge is how to deliver value for customers other than those at scale), but what about storage? VMware is pushing forward with Virtual SAN, now providing the ability to use Virtual SAN resources outside a vSphere cluster. This may be a reaction to other vendors like Nutanix (who offered this feature earlier in the year), but it does start to encroach on the market of their parent company, Dell EMC.

How confusing is that? VMware wants you to ditch the storage array; EMC and Dell wants you to buy more. Where's the cutoff between the two? When should customers move from Virtual SAN to dedicated array, and more importantly, who will tell them – VMware or EMC?

The challenge of containers

Unfortunately, VMware is being attacked on all sides, including the irresistible move towards containerisation. Sometimes described as "virtualisation lite", containers are more akin to running started tasks and batch jobs on the mainframe. A container is really just a collection of processes running an application within a number of isolation wrappers that implement multi-tenancy. However, for VMware, they are a potential existential threat.

Containers run on bare metal or potentially within a VM. Certain aspects of containers are still very immature, including networking and storage. The networking pieces are being addressed and storage has made some advances too, with the ability to use persistent storage and external arrays.

The big problem, however, is the speed of development for the container initiative. Docker, CoreOS, Rancher Labs and others are turning out new software and features with rapid regularity – much faster than VMware are managing to achieve. VMware Integrated Containers and the Photon platform have taken an age to become GA (and are not there yet). Many customers may see these as a cumbersome overhead to running a container ecosystem. Case in point is the new VMware Kubernetes as a service offering. End-users may simply deploy Kubernetes themselves, seeing no benefit to attaching more software (and licensing) around what they have today.

The bigger challenge of public cloud

The bigger challenge, though, will come in the form of the public cloud. VMware has chosen to embrace rather than compete in this area, through new partnerships with IBM (SoftLayer) and AWS. But isn't this just delaying the inevitable? The new "VMware on AWS" offering runs vSphere on bare metal, not nested within AWS, which perhaps provides some level of isolation from the AWS core features. However, over time customers will adapt to the opex model and surely try out AWS features like EC2, S3 and RDS – if they haven't already. VMware appears to making it easy for their customers to move away to public cloud.

Bold statements

Dell acquiring EMC was a big statement. And EMC acquiring VMware was a bold move that paid off big time. Perhaps it's time for VMware to acquire the likes of Docker and make their own bold statement. Server virtualisation has been massively successful; VMware needs to move into the next emerging market and make a play to own that one too, in a market that's moving inexorably to a hybrid model.

What do you think?

Other stories you might like

  • NASA delays SLS rollback due to concerns over rocky path to launchpad
    The road to the Moon is paved with... river rock?

    NASA's Moon rocket is to trundle back into its shed today after a delay caused by concerns over the crawlerway.

    The massive transporter used to move the Space Launch System between Vehicle Assembly Building (VAB) and launchpad requires a level pathway and teams have been working on the inclined pathway leading to the launchpad where the rocket currently resides to ensure there is an even distribution of rocks to support the mobile launcher and rocket.

    The latest wet dress rehearsal was completed on June 20 after engineers "masked" data from sensors that would have called a halt to proceedings. Once back in the VAB, engineers plan to replace a seal on the quick disconnect of the tail service mast umbilical. The stack will then roll back to the launchpad for what NASA fervently hopes is the last time before a long hoped-for launch in late August.

    Continue reading
  • Datacenter operator Switch hit with claims it misled investors over $11b buyout
    Complainants say financial projections were not disclosed, rendering SEC filing false and misleading

    Datacenter operator Switch Inc is being sued by investors over claims that it did not disclose key financial details when pursuing an $11 billion deal with DigitalBridge Group and IFM Investors that will see the company taken into private ownership if it goes ahead.

    Two separate cases have been filed this week by shareholders Marc Waterman and Denise Redfield in the Federal Court in New York. The filings contain very similar claims that a proxy statement filed by Switch with the US Securities and Exchange Commission (SEC) in regard to the proposed deal omitted material information regarding Switch's financial projections.

    Both Redfield and Waterman have asked the Federal Court to put the deal on hold, or to undo it in the event that Switch manages in the meantime to close the transaction, and to order Switch to issue a new proxy statement that sets out all the relevant material information.

    Continue reading
  • Google to pay $90m to settle lawsuit over anti-competitive behavior on the Play Store
    US developers that qualify could receive more than $200,000

    Google is to pay $90 million to settle a class-action lawsuit with US developers over alleged anti-competitive behavior regarding the Google Play Store.

    Eligible for a share in the $90 million fund are US developers who earned two million dollars or less in annual revenue through Google Play between 2016 and 2021. "A vast majority of US developers who earned revenue through Google Play will be eligible to receive money from this fund," said Google.

    Law firm Hagens Berman announced the settlement this morning, having been one of the first to file a class case. The legal firm was one of four that secured a $100 million settlement from Apple in 2021 for US iOS developers.

    Continue reading
  • Devops tool Jenkins now requires Java 11: This might sting a bit
    Final shift set for version 2.357 of developer automation platform

    It has taken a while, but the Jenkins project confirmed this week that Java 11 will be required from this week's Jenkins 2.357 and for the upcoming September LTS release.

    Jenkins, originally authored by Kohsuke Kawaguchi, recently passed its 10th anniversary. Originally known as Hudson, before the Oracle / Sun deal resulted in a fork, the platform is a veteran of the continuous integration and continuous delivery world. It is also written in Java.

    It's going to be a bit of a wrench. Java 11 itself was released in 2018 as a long-term support version, and the Jenkins LTS core has been Java 11-capable for a while now. The June LTS also supports Java 17 (the latest LTS of Java SE.)

    Continue reading

Biting the hand that feeds IT © 1998–2022