Platform-as-a-Service: Lessons from Manufacturing
35
Session title 1 Platform-as-a-Service: Lessons from Manufacturing Gordon Haff @ghaff [email protected]
-
Upload
gordon-haff -
Category
Technology
-
view
1.738 -
download
2
description
I wrote this presentation for Cloud Expo 2014 in NYC on June 11. Here's the abstract: Software development, like engineering, is a craft that requires the application of creative approaches to solve problems given a wide range of constraints. However, while engineering design may be craftwork, the production of most designed objects relies on a standardized and automated manufacturing process. By contrast, much of what's typically involved when moving an application from prototype to production and, indeed, maintaining the application through its lifecycle remains craftwork. In this session, Red Hat Cloud Product Strategist Gordon Haff discusses how a Platform-as-a-Service (PaaS) like Red Hat OpenShift can bring industrialization to the development and deployment of applications. By abstracting irrelevant details and automating key activities, a PaaS can do for software development productivity and quality what assembly line innovations did for manufacturing.
Transcript of Platform-as-a-Service: Lessons from Manufacturing
Session title
2
IT Ops is under pressure
Session title
3
Environment is out of control
Session title
4
Developers want (need) the latest tools
Session title
5
The business is demanding more
AGILITY! VELOCITY!
Session title
6
Closing the gap with a cloud
Session title
7
From Platform to Platform-as-a-Service
Session title
8
The history of the world in one graph
Source: Gregory Clark
Session title
9
Many different things contributed
Session title
10
Focus on three (plus one)
• Standard parts
• Standard process
• Standard infrastructure
• Adaptability
Session title
11
Some early standard parts
• Système Gribeauval (1765)o Cannonso Standard bores
• Eli Whitney (1801)o Muskets with
interchangeable partso Still costly and handmade
Session title
12
PaaS: (Choice of many) standard parts
• Standardized
• Open
• Interoperable
• Multi-vendor
• Multi-platform
Session title
13
Bringing process to standardizationBrunel 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.”
Session title
14
PaaS: Standard process
• Eliminate redundancy
• Create repeatability
• Drive modularity
• Automate relentlesslyCode Deploy Run
Session title
15
Automating application scaling
Session title
16
Automating continuous integration with Maven and Jenkins
Code
Session title
17
PaaS: Standard infrastructure
• Process drives tools (not the other way around)
• Abstraction of implementation details
Session title
18
• Transformative effect of standardized infrastructure
• Reduction of repetitive manual tasks
• Fundamentally changes economics
Lessons from the shipping container
Session title
19
Linux containers and PaaS
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
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
Session title
22
Common infrastructure for app deployment & management
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
Session title
24
Increasing flexibility
• Lean manufacturing
• JIT
• BTO
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]
Session title
26
How do the three ways translate?
STANDARDIZED ENVIRONMENTSAUTOMATED PROVISIONING
Session title
27
How do the three ways translate?
CONTINUOUS INTEGRATIONCONTINUOUS DELIVERY
Session title
28
How do the three ways translate?
DEVELOPER SELF-SERVICERAPID PROTOTYPING
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
Session title
30
Gartner DevOps metrics pyramid
Data-Driven DevOps: Use Metrics to Help Guide Your JourneyMay 2014
Session title
31
DevOps implemented makes life better
ACCELERATED APP DELIVERY FOR THE BUSINESS
Session title
32
DevOps implemented makes life better
ACCELERATED APP DELIVERY FOR THE BUSINESS
SELF-SERVICE ACCESS TO THE LATEST TOOLS FOR DEVS
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
Session title
34
About Me
• Red Hat Cloud Product Strategy
• Twitter: @ghaff
• Google+: Gordon Haff
• Email: [email protected]
• Blog: http://bitmason.blogspot.com
• Formerly: Illuminata (industry analyst), Data General (minicomputers/Unix/NUMA/etc.)
