Yesterday a startup came out of stealth which was founded by a couple of former VMware veterans. I happen to know the majority of them, and have had the pleasure to have worked with them on various things in the past. For instance Platform9‘s three of the four co-founders were all heavily involved in vCloud Director, and the fourth co-founder was VMware employee number 27… but that is not where it stops… there is much more talent on-board. But that is not what this blog is about, this blog is about Platform9, the new company that they have formed and the product they are building.
** note, I did not test the product… it is impossible to provide an analysis of what works / does not work and how they play in this space or compete with others, this is based on a conversation and a demo **
Platform9 is as they say themselves:
… the easiest way for enterprises to implement a private cloud, with intelligent, self-service provisioning of workloads onto their computing infrastructure.
- 100% Cloud Managed: Platform9’s cloud-based model means that there is no complex management software to setup, monitor and upgrade, thus simplifying the operational experience.
- Single Pane of Glass: Platform9 offers unified management across diverse environments – Docker, KVM and VMware vSphere – across datacenters and geographies.
- Based on OpenStack: Platform9 customers get the best of OpenStack with 100% API compatibility.
When I met them last month, they gave a demo and showed me what they had implemented so far: Management of KVM based hypervisors using a very easy to use and slick using web-based user interface. Where the whole management solution was running in “the cloud”.
Creating a new “instance” was literally a few clicks, snapshotting / cloning it… same thing, just a couple of clicks. Now what stood out to me during the demo was the use of the word “instance” instead of “virtual machine”. So I asked them why not “virtual machine”, considering they are all VMware veterans that made more sense to me. The explanation was simple: we want to manage multiple layers. We want to manage KVM VMs, vSphere VMs but for instance also Docker containers. That is why we used a different term than we would normally use… and yes that did make sense to me. I also wondered if they would be able to mix different environments and type of instance in their UI, and the answer was yes. Docker containers, KVM VMs, vSphere VMs (etc) will also be seen in the same single pane of glass. I really like the fact that Platform9 did not limit themselves to just vSphere, or just VMs but rather is focusing on the needs of developers and providing what they require.
Similar to CloudPhysics, Platform9 is taking SaaS approach. The major benefit of course being the agility at which new features/functionality can be introduced to the outside world, or tested against a small subset of customers. Same of course applies to bug fixes / updates. No need to do that yourself, Platform9 will take care of that for you. Promising indeed.
Now there is a lot of competition in this space, as also emphasized by Ben Kepes in his post on Platform9… But to be honest, if I look at one of the examples listed like ServiceMesh, they seem to cater for a completely different market. Platform9 is all about simplicity and managing instances, not so much about creating complex recipes etc. I agree though that there are a lot of vendors playing in this space (and as such competition), or somewhat related space, but that makes it even more interesting to see how Platform9 evolves in my opinion.
For more info, a demo, or a trial:
Platform9 will showcase its product in its booth #324 at VMware’s VMworld Conference, taking place the week of August 25th in San Francisco. The product is currently in beta with general availability planned for later this year. Platform9 currently supports KVM with upcoming support for Docker and VMware vSphere. To register for a free trial, go to: http://www.platform9.com.
James Hess says
I thought it was quite interesting until I realized the implications of “100% Cloud managed”; which seems like an exceedingly bad idea.
Some WAN issue, and the entire infrastructure can no longer be managed? No, thanks….
Meta cloud solutions says
“instance” vs “virtual machine” in the evolved SaaS model eg AWS model does not care if a “VM” goes down – it just kills it and spins another instance to replace it.
In our VM centric enterprise we want to evolve our dev-ops to get into this mindset – it is a barrier – who will win the business? AWS? Google? Azure? VWware?
At this rate its a war of attrition (whoever can burn the least and build the best) to gain the major market share.
@cocquyt
DavidD says
Children or cattle.
Do you treat your VMs as unique snowflakes (children)
Or a commodity that can they be destroyed and recreated (cattle).
IaaS Provider says
I think VMware will win the business, however.. there is a big stack for everybody. I don’t think AWS, Google, Azure or VMware mind on who is winning.. Sharing the stack is also fine for them!