By popular demand the presentation that Ed Hoppitt delivered opening Cloud Camp London on 30th April 2015. This deck is a simple explanation of Container technology borrowing some great analogies from the shipping industry that anyone can get their head around. It also then deconstructs the elements that go in to making VMware's Cloud Native Apps announcements around Project Photon (Ultra Lightweight LINUX Distribution for running containers) and Project Lightwave (Identify and Access management for container based platforms).

1. Containers – What’s all the fuss about ?
Ed Hoppitt, CTO Ambassador, EMEA
VMware Advisory Services
CloudCamp London 30th April 2015
V2.1
@edhoppitt

2. 2
Gratuitous use of
shipping container
based analogies ahead

3. Moving from Rigid Structures to Fluid Business
3
Now
Unpredictable
Shared
Rapid Iteration
Instant
Billions
“Built to Change”
Then
Known
Owned
Methodical Planning
Slow
Millions
“Built to Last”
Competition
Assets
Innovation
App Deployment
Customers
Organization

4. Hybrid
Containers
Data
AnalysisApp
DevOps
Openstack
PaaS
It’s all about this loop

5. Deploying Containers – Need to Know
Cars Consumer Goods Frozen Foods Beer Pizza
An engine that allows any
payload to be encapsulated
as a lightweight portable self-
sufficient container …
… that can be manipulated
using standard tools and run
consistently on any delivery
platform.
*Slide Adapted from Docker Slide by Ben Golub – VMworld 2015

6. Deploying Containers – Need to Know
Developer’s Laptop QA Server Data Center Public Cloud Contributors Laptop
Static Website User DB Web Front End Queue Analytics DB
An engine that allows any
payload to be encapsulated
as a lightweight portable self-
sufficient container …
… that can be manipulated
using standard tools and run
consistently on any delivery
platform.
*Slide Adapted from Docker Slide by Ben Golub – VMworld 2015

7. How does that translate in the IT world ?

8. Taking the analogy back to the shipping world ….

9. So what ?
Enabler for Micro-Service Architectures – Monoliths are dead,
applications are de composed into decoupled, small containers built for a
simple purpose. This enables the business to much more quickly architect,
deploy and monetize and provides a Lego-Brick for Cloud deployments.
Brings Dev and Ops closer together – Unlike Chef and Puppet which are
often seen as sitting at the forefront of the DevOps movement, containers
allow the Dev team to work inside the container and the Ops team to safely
work outside the container. This enables the business to respond faster.
Consistency required for Continuous Integration (CI) – By ensuring a
consistent development framework regardless of it sitting on a developers
laptop or a production datacenter the consistency needed

10. What components are needed for a shipping operation ?
Customer
Shipping Operations

11. What components are needed for a shipping operation ?
Mapping / Shipping Lanes / Route Planning
Shipping Planning and Scheduling
Manifest
Customer
Shipping Operations

12. What components are needed for a shipping operation ?
Mapping / Shipping Lanes / Route Planning
Deployment, Orchestration and Scheduling
Identity and
Authentication
Engine
Customer
Shipping Operations

13. What components are needed for a shipping operation ?
Mapping / Shipping Lanes / Route Planning
Deployment, Orchestration and Scheduling
Identity and
Authentication
Engine
Ultra-Light Linux Platform
Customer
Shipping Operations

14. What components are needed for a shipping operation ?
Software-Defined Networking
Deployment, Orchestration and Scheduling
Identity and
Authentication
Engine
Ultra-Light Linux Platform
Customer
Shipping Operations

15. What components are needed for a shipping operation ?
Software-Defined Networking
Deployment, Orchestration and Scheduling
Identity and
Authentication
Engine
Ultra-Light Linux Platform
Hypervisor
Developer
Operations