Keynote presentation for the Pivotal Cloud Platform Roadshow. Introduces the market drivers for the Cloud Foundry Platform as a Service, discusses open source softwared (Cloud Foundry is OSS) and introduces the fundamentals of the platform.
How do you meet the Customer Expectations ?
By thinking about the entire platform. It’s the IaaS benefits combined with Developer, IT Ops and Infra benefits. All of these combined pack the punch and you can stand up this environment pretty fast.
There’s no single magic bullet, but the ecosystem and new platform thinking that ties your complexities together and automates at scale.
Enterprise Grade with Consumer expectations that’s the promise
Vendors that have caused these silos to emerge hold apps, data, expertise captive. They are proprietary, closed source and maintain a hold on the enterprise because of it.
Some enterprises tried to shift their bargaining power and invested in modern “as a Service” technologies. As it turns out, the same strategic shortcomings remain. Most PaaS solutions today force you to write your application to that specific PaaS and that is where your app will stay, much like writing to an OS. It sits on a public cloud somewhere and cannot be moved without recoding and dependency swaps.
An application written to use AWS features like AutoScaling is great, but not very portable. The proprietary cloud has become the new silo.
The rate and pace of change in our industry only continues to rise. We’re undergoing a transition to a whole new set of platforms and a whole new set of concerns. Cloud platforms, big data, real-time analytics, mobile delivery, systems of engagement and more are all bringing in waves of change and innovation.
The old model of committee-based collaboration to create a standard specification that can then be implemented by multiple vendors is just too slow for this world. Not only is it too slow, but it also does not produce solutions that are as good as those created by refining open source projects in the fire of real user feedback. So the industry has mostly replaced a standards-first approach with an open-source first approach. In many cases, with an open-source *only* approach, but there are also examples of open standards being created behind the bow-wave of open source, ratifying what have become defacto standards. [This recently happened with the Spring Batch project for example, where the lag between the first open source version being used in production, and the JEE standard being complete was about 5 years! That’s an eternity in today’s world of IT].
In the beginning people used to say that open source couldn’t innovate. That it was only good for commoditizing existing capabilities. That it was a race to the bottom which would destroy industry value.
Bullshit.
We never believed that. Still don’t. Open source is the best way to innovate because of the short feedback cycles it can create that we talked about previously. In the last few weeks, we’ve seen a subset of the vendors in the Hadoop space, which is itself just a part of the over 140 projects at the Apache Software Foundation, achieve a combined market valuation of $3Bn (Cloudera = $2Bn, HW = $1Bn). That’s a whole lot of industry value being created through open source. What happened?
First open source became a means of overcoming proprietary lock-in,. Then it replaced standards at the leading edge of industry adoption, fueled by a rate of innovation that standards could never keep up with. Then it became a strategic asset and an integral part of corporate strategy.
Apps are Stateless, all the State lives in Data Services
Cloud Foundry has two big systems within it: Elastic Runtime for managing Applications, and BOSH for managing Services.
BOSH is used to run Elastic Runtime.
http://www.freetechie.com/blog/wp-content/uploads/2010/04/vmware_fusion_500x500.jpg
How do containers and PaaS work together?
One of the capabilities of PaaS, is the orchestration and management of multiple virtual machines and/or containers that depend on each other and work with each other to provide an application that is built and run atop an infrastructure of choice.
Pivotal has released experimental support for Docker containers (a running instance of a Docker image) in their Ops Manager to provide the ability to run multiple Docker images on a single VM. The Diego project further enables enterprises to run 12-factor applications within Docker images as first-class applications so that they can leverage features such as load balancing, aggregate logging, service bindings, team management and refined event auditing that Pivotal CF provides.
So how does Pivotal CF and Docker work together?
Pivotal CF adds many enterprise-grade features for Docker containers, particularly around app health management, monitoring, and orchestration.