This document discusses how platform-as-a-service (PaaS) can learn from lessons of standardization in manufacturing. It argues that PaaS provides standardized, open, interoperable components like manufacturing provided standardized parts. PaaS also enables standard processes to drive automation and modularity, just as standardized processes increased efficiency in manufacturing. Further, PaaS offers standardized infrastructure that abstracts implementation details and fundamentally changes economics by reducing manual tasks, mirroring the impact of standardized infrastructure in shipping.

1. Session title
1
Platform-as-a-Service:
Lessons from Manufacturing
Gordon Haff
@ghaff
ghaff@redhat.com

2. Session title
2
IT Ops is under pressure

3. Session title
3
Environment is out of control

4. Session title
4
Developers want (need) the latest tools

5. Session title
5
The business is demanding more
AGILITY! VELOCITY!

6. Session title
6
Closing the gap with a cloud

7. Session title
7
From Platform to Platform-as-a-Service

8. Session title
8
The history of the world in one graph
Source: Gregory Clark

9. Session title
9
Many different things contributed

10. Session title
10
Focus on three (plus one)
Standard parts
Standard process
Standard infrastructure
Adaptability

11. Session title
11
Some early standard parts
Système Gribeauval (1765)
Cannons
Standard bores
Eli Whitney (1801)
Muskets with interchangeable parts
Still costly and handmade

12. Session title
12
PaaS: (Choice of many) standard parts
Standardized
Open
Interoperable
Multi-vendor
Multi-platform

13. Session title
13
Bringing process to standardization
Brunel and Maudslay’s sailing blocks
“...So that ten men, by
the aid of this
machinery, can
accomplish with
uniformity, celerity
and ease, what
formerly required the
uncertain labour of
one hundred and ten.”

14. Session title
14
PaaS: Standard process
Eliminate redundancy
Create repeatability
Drive modularity
Automate relentlessly
Code Deploy Run

15. Session title
15
Automating application scaling

16. Session title
16
Automating continuous integration with Maven and Jenkins
Code

17. Session title
17
PaaS: Standard infrastructure
Process drives tools
(not the other way
around)
Abstraction of
implementation
details

18. Session title
18
Transformative effect
of standardized
infrastructure
Reduction of
repetitive manual
tasks
Fundamentally
changes economics
Lessons from the shipping container

19. Session title
19
Linux containers and PaaS

20. Session title
20
Linux containers build on common platform
Combination of kernel features:
namespaces, control groups,
SELinux
Provide lightweight isolation of
process, network, filesystem
spaces.
Break up the single monolithic
runtime concept and turns Linux
back into a multi-instance, multi-
version, multi-tenant OS

21. Session title
21
Docker makes containers more useful
Builds on Linux Containers, adds
an API, an image format and a
delivery and sharing model
Provides aggregate packaging to
bind application and its runtime
dependencies for deployment into
a Linux Container

22. Session title
22
Common infrastructure for app deployment & management

23. Session title
23
Inflexible manufacturing
Any customer can have a car
painted any color that he wants so
long as it is black.
Henry Ford
General Motors Fairfax Assembly Plant in Kansas City, Missouri

24. Session title
24
Increasing flexibility
Lean manufacturing
JIT
BTO

25. Session title
25
PaaS: Flexibility through DevOps
[1] http://itrevolution.com/the-three-ways-principles-underpinning-devops/
Gene Kim’s THREE “WAYS” OF DEVOPS[1]

26. Session title
26
How do the three ways translate?
STANDARDIZED ENVIRONMENTS
AUTOMATED PROVISIONING

27. Session title
27
How do the three ways translate?
CONTINUOUS INTEGRATION
CONTINUOUS DELIVERY

28. Session title
28
How do the three ways translate?
DEVELOPER SELF-SERVICE
RAPID PROTOTYPING

29. Session title
29
• Apply agile continuous improvement
• Ensure that each DevOps process implemented (such as
test-driven infrastructure, continuous delivery, etc.) maps
to a business impact
• Monitor for unintended side effect.
• Foster a learning-centric approach to process
improvement, rather than to use these exercises as a
means to punish missing expectations
Summarized from
Data-Driven DevOps: Use Metrics to Help Guide Your Journey
May 2014
Gartner DevOps recommendations

30. Session title
30
Gartner DevOps metrics pyramid
Data-Driven DevOps: Use Metrics to Help Guide Your Journey
May 2014

31. Session title
31
DevOps implemented makes life better
ACCELERATED APP DELIVERY FOR
THE BUSINESS

32. Session title
32
DevOps implemented makes life better
ACCELERATED APP DELIVERY FOR
THE BUSINESS
SELF-SERVICE ACCESS TO THE
LATEST TOOLS FOR DEVS

33. Session title
33
DevOps implemented makes life better
ACCELERATED APP DELIVERY FOR
THE BUSINESS
STANDARDIZED AND
CONTROLLED ENVIRONMENTS
FOR OPS
SELF-SERVICE ACCESS TO THE
LATEST TOOLS FOR DEVS

34. Session title
34
About Me
• Red Hat Cloud Product Strategy
• Twitter: @ghaff
• Google+: Gordon Haff
• Email: ghaff@redhat.com
• Blog: http://bitmason.blogspot.com
• Formerly: Illuminata (industry analyst), Data
General (minicomputers/Unix/NUMA/etc.)

35. Session title
35
Questions?
Gordon Haff
@ghaff
ghaff@redhat.com