From DevOps Summit Silicon Valley, November 2015 Manufacturing has widely adopted standardized and automated processes to create designs, build them, and maintain them through their life cycle. However, many modern manufacturing systems go beyond mechanized workflows to introduce empowered workers, flexible collaboration, and rapid iteration. Such behaviors also characterize open source software development and are at the heart of DevOps culture, processes, and tooling. In this session, Red Hat’s Gordon Haff will discuss the lessons and processes that DevOps can apply from manufacturing using: - Container-based platforms designed for modern application development and deployment. - The ability to design microservices-based applications using modular and reusable parts. - Iterative development, testing, and deployment using Platform-as-a-Service and integrated continuous delivery systems.

1. Gordon Haff, @ghaff, ghaff@redhat.com
William Henry, @ipbabble, whenry@redhat.com
Cloud & DevOps Product Strategy
3 November 2015
MANUFACTURING PLUS OPEN SOURCE
EQUALS DEVOPS

2. WHAT IS DEVOPS?

3. DevOps applies open
source principles and
practices with...

4. TOOLS drawing
from innovative
development
communities

5. Automation of
PROCESS from
development
through ongoing
operations

6. CULTURE
of collaboration
valuing openness
and transparency

7. WHAT MANUFACTURING
AND OPEN SOURCE
CAN TEACH US

8. PRINCIPLES FOR SUCCESS
● Adopt appropriate tooling
● Understand the process
● Drive modularity
● Automate repeatable processes
● Create culture
● Continuous iteration and improvement

9. ALL WAS NOT WELL IN THE US
AUTO BUSINESS

10. WHAT
HAPPENED?
Taiichi Ohno, Inventor of the Toyota Production
System (TPS)
W. Edward Demming, champion of
statistical process control

11. IN SOFTWARE, IT’S CALLED DEVOPS

13. TOOLS FOR
OPERATIONS*/INFRASTRUCTURE
Containerized infrastructure
Orchestration
Policy-based governance
Configuration management
Automation
Packaging
Updates
* But they bleed into developer land!

14. TOOLS FOR DEVELOPER* WORKFLOWS
Collaboration
CI/CD
Issue tracking
Source code control
Code review
Platform-as-a-Service
* But they bleed into ops land!

15. CI/CD PIPELINE TOOLSET
CI/CD Workflow
UI
gerrit

17. Insert copy.
BEYOND LOCAL MAXIMA: REUSE

18. PLATFORM THINKING WINS
“45–47% passenger cars will use one of top 20 platforms by
2015.”
EvaluServe, 2012

19. COMPONENTIZED APPS + APIS
Lighter-weight communications
protocols
Improved understanding of functional
separation
More open source and vendor-neutral
philosophies
Scale-out infrastructure
standardization and automation
Alignment with evolving practices
such as DevOps

20. AUTOMATE (MANY OF) THE THINGS

21. AUTOMATION AS A CI/CD PROCESS

22. AUTOMATION ACROSS ENVIRONMENTS
Continuous Integration /
Continuous Deployment
Image & Package &
Metadata Repository
src repo
Dev./Build QA Production
in OHC

23. AUTOMATING TRUST
● Workflow vulnerabilities/risks
○ Source control - github
○ CI - Jenkins
○ Provisioning - Chef, Puppet, Ansible, Vagrant
○ Identity management - Keystone
● Content chain of custody
○ Container certification
○ Signed repositories
● Ongoing lifecycle management
○ Policy-based placement & monitoring -
ManageIQ
○ Monitoring - Nagios

24. NEED TO DEFINE METRICS
Deployment Frequency
404Page not found
99.999
Change Volume Lead Time
Deployment Failure Rate Mean Time to Recover Service Availability
- +

26. Toyota Way has been driven so
deeply into the psyche of
employees at all levels that it has
morphed from a strategy into an
important element of the
company's culture.
CREATING CULTURE

27. “Our culture is too difficult!”
Really?
Consider post war Japan.
https://leanhomebuilding.wordpress.com/page/4/

28. Culture = f (l, o, i, t, …)
where:
l = leadership
o = organization
i = incentives
t = trust
… = many other things
Open source offers guidance

29. LEADERSHIP AND
VISION
BUT NO ONE
ORGANIZATIONAL
STRUCTURE

30. SOLVE
SPECIFIC
PROBLEMS

31. TRANSPARENCY

32. RICH
COMMUNICATION
FLOWS

33. DON’T
FEAR
FAILURE

34. INCENTIVES
MATTER

35. Open source is driving
DevOps
But it’s more than the code!

36. Credits
Tools: Dorli Photography, cc/flickr https://www.flickr.com/photos/dorlino/4946061042/
Robots: davidgariepy, cc/flickr https://www.flickr.com/photos/davidgariepy/2495011427/
Kids programming: Esti Alvarez cc license
Dev: Nelson Pavlosky/flickr under CC http://www.flickr.com/photos/skyfaller/113796919/
Ops: Leonardo Rizzi/flickr under CC http://www.flickr.com/photos/stars6/4381851322/
Rainbows and Unicorns: http://kaigumo.deviantart.com/art/Unicorns-Fart-Rainbows-3-151273843
Join hands: https://www.flickr.com/photos/vogelium/10565496565/
Thanks to J.P.Morgenthal for some of his thoughts about culture change. See also http://www.slideshare.net/JPMorgenthal1/process-
andorgtrumpcultureinentdevops
Governance models: http://oss-watch.ac.uk/resources/governancemodels
Transparent code: iStockPhoto
Linux Collaboration Summit: Linux Foundation
Wipeout: https://www.flickr.com/photos/andymorffew/15843725192
No: Wikimedia
Formal garden: https://www.flickr.com/photos/ukgardenphotos/12073131333
Wildflowers: https://www.flickr.com/photos/karlskamera/14424047561

37. THANK YOU
plus.google.com/+RedHat
linkedin.com/company/red-hat
youtube.com/user/RedHatVideos
facebook.com/redhatinc
twitter.com/RedHatNews