Ben Kepes is a content adviser for VentureBeat’s recent CloudBeat 2012 conference.
EMC and VMware will announce a semi-autonomous business unit dedicated to cloud services this week, a well-placed source has told me.
The unit, to be managed from within EMC at first, will combine some assets from the parent company along with some from VMware, a company that EMC is a majority shareholder of.
EMC plans the announcement for Tuesday, December 4, according to my source.
EMC declined to comment for this article, and VMware chief technical officer Stephen Herrod gave a resounding “no comment” when I asked him what the rumors would mean for his company.
My source tells me the makeup of the new unit will be close to what GigaOm suggested in the initial scoop. The unit will essentially roll up all the different cloud infrastructure and platform offerings from both VMware and EMC including:
- Cloud Foundry, an open source platform-as-a-service (PaaS) project initiated by VMware but with a significant ecosystem of third-party companies building products on top of it. (Disclosure: I am an investor in Appsecute, a PaaS management layer that includes support for Cloud Foundry-based PaaS.)
- The Big Data offering out of EMC, Greenplum.
- Project Rubicon, the EMC/VMware joint venture covering cloud infrastructure.
My source tells me that, as many industry insiders expected, the new unit will be run by former VMware CEO Paul Maritz and that Maritz has, since he stepped down from the CEO role, been working behind the scenes on the strategy for the new unit.
Let’s call it “VMCloud” for now, though we don’t know for sure what EMC will call the new unit.
Contrary to initial thoughts, I am led to believe that the new unit will not be a standalone company but rather a composition of different parts, run out of EMC. It appears the plan is to consolidate the different components in the short to medium term and spin it out as a standalone company thereafter. Part of the reason to keep it within EMC in the initial stages is to help minimize the pain of separating out the different units. I am told there is some staff culling involved in the process.
While the move isn’t at all unexpected, it is a surprise that the new unit looks set to remain within the mothership. Much of the reason for dividing the cloud components off is the tension created by the new businesses, which are somewhat disruptive to the traditional revenue streams of both VMware and EMC. Putting them in an autonomous separate company would give the cloud components more leeway to pursue their own business, independent from interference.
There have also been concerns from customers and partners of the cloud units about the intentions of both EMC and VMware. As an example of this, many partners within the Cloud Foundry ecosystem have told me of their anxiety about the intentions of VMware when it comes to the open source PaaS. While they’re excited about the opportunity the initiative brings, they are also mindful of the potential for VMware to act in a manner at odds with the aims of the community. Neither VMware nor EMC are well-known as organizations quick to embrace an “open” style of business.
In my view, the new business, as it looks likely to be constituted, doesn’t go far enough to really give it the ability to stand on its own two feet.
Earlier this year I wrote an opinion piece after the first rumors of the new company were scooped by GigaOm. In my piece I suggested that it would take a complete severing of the connection between VMware/EMC and the cloud business units (Cloud Foundry, Greenplum. and Rubicon) to remove the barriers to further success for the individual units. This is true for several reasons:
- The companies’ traditional businesses are highly lucrative but are being eroded by cloud companies such as Amazon Web Services
- A more compelling cloud story would create a situation is created that is toxic to its high margin businesses as above
- As a peripheral issue, VMware’s application assets are disconnected, disjointed, and largely irrelevant
- VMware has a vibrant growing ecosystem around CloudFoundry, but PaaS adds confusion to the existing business and a potential cloud-specific future business
In my view, the initiative should be seen as an opportunity to review the whole of both VMware’s and EMC’s businesses. As such they should not only spin out the cloud units together as an independent entity but also take further, bolder steps. Here’s what I think EMC and VMWare need to do:
- Ditch the niche applications – VMware has, in the past few years, acquired a number of cloud application companies. Sliderocket, Zimbra, and Socialcast are disconnected from what the company does and hence are a distraction from the core business. My advice is to flick off Sliderocket and Zimbra and make an assessment on whether Socialcast can be folded in as a fabric quickly and easily.
- Understand that the future is heterogeneity – Create a standalone entity that is focused on cloud infrastructure – include infrastructure management business DynamicOps in with this and direct the existing infrastructure business to “play nicely” with the new unit. The new business can be a stellar vendor of public and private cloud technologies, and the DynamicOps inclusion can mean that the products have a compelling story when seen alongside customer use of existing VMware products and services. In doing so, VMware disrupts the IT management and service provision space before other players are able to do so themselves.
- Go hybrid – Microsoft has signaled it is finally going to play a compelling game in the hybrid cloud space. I’m predicting an expansion of the “private Azure” play well beyond service providers. If VMware decides that it wants to keep all of its infrastructure business together, then it has to do the right thing and forego some short-term hyper-profit for long-term stability. It needs to provide DynamicOps to customers as an accessible and open turnkey solution to bring together all their assets (physical, virtual, public, and private) under one pane of glass and make sure that it incentivizes its salespeople to effect the move – it’s going to be hard but some kind of quota system that mandates lower margin but longer-term cloud sales is going to be necessary.
- Let PaaS shine – The biggest barrier to Cloud Foundry hitting it out of the park (beyond customer confusion about what PaaS actually is, of course) is the uncertainty around VMware’s intentions. A cloud unit where both infrastructure and platform product are built with a view to openness would help reduce the concerns of the community.
The individual business units have much potential but, as is often the case, it is only through a logical and consistent mix of products that they can be successful.
VMware and EMC have a big opportunity to build an exceptionally compelling business that could be very competitive in the new cloud world, but it’ll take courage and conviction to make the big decisions that are needed for this to occur.
Ben Kepes is a technology evangelist, investor, commentator, and a business adviser. Ben covers the convergence of technology, mobile, ubiquity, and agility, all enabled by the cloud. His areas of interest extend to enterprise software, software integration, financial/accounting software, platforms and infrastructure as well as articulating technology simply for everyday users. You can follow Ben on Twitter.
Photo credit: ChadScott via photopin
VentureBeat’s VB Insight team is studying marketing and personalization...
Chime in here, and we’ll share the results