An introduction to DevOps, from first principles. You'll learn about the Three Ways of DevOps, CAMS, the benefits as asserted by the State of DevOps Report 2016 and some case studies, geared towards the financial industry.

1. DevOps
Working Together for Brilliant Outcomes

2. 2016
State of
DevOps Report
https://puppet.com/resources/white-paper/
2016-state-of-devops-report

3. 4600
professionals surveyed in 2016
(25000 over five years)

4. Continuous collaboration between
development and operations in the entire
service lifecycle, providing (much) more
business value, (much) faster and with (much)
less risk.

5. “DevOps is also characterized by operations
staff making use of many of the same
techniques as developers for their systems
work.”
The Agile Admin. What Is DevOps?

6. Dev
Developers
QA Engineers
System Analysts
Produt Owners
Product Managers

7. Ops
System Administrators
InfoSec
Release Engineers
Network Engineers
DBAs

8. Organization Sizes
<
1010000+ 9999-500 499-100 99-20 N.
A.
52%

9. The Three Ways Of
DevOps
http://itrevolution.com/the-three-ways
-principles-underpinning-devops/

10. Beware of Local Optimizations

11. Let’s say average cycle time* for a development team is 5 days.
Dev - 5 daysInput
Output

12. Let’s say average cycle time* for a development team is 5 days.
Dev - 5 daysInput
Output
And, after much effort,
we optimize it.
Dev - 4 days

13. Let’s say average cycle time* for a development team is 5 days.
Dev - 5 daysInput
Output
And, after much effort,
we optimize it.
Dev - 4 days
YAY!

14. We deserve a pat in the back!

15. Or do we?

16. YAY!
Dev
4 days
Business

17. Yaayyy…. ?
Dev
4 days
Business
QA
10 days

18. Oh boy…
Dev
4 days
QA
10 days
Business
Release
15 days
Customer

19. Visualize The Whole Workflow

20. The First Way: System Thinking
Dev Ops
Business Customer

21. System Thinking
● Be Aware of the Whole System
● Increase Flow
● Optimize Globally
● Avoid Moving Defects Downstream

22. 2555x
shorter Lead Times

23. Releasing Is Not The End
Of The Story

24. After Releasing…
Success Beyond
Wildest Dreams
Unexpected Usage
Patterns
Lousy
Performance
Incidents

25. Creating Feedback Loops
Is Of The Essence

26. The Second Way: Amplify Feedback Loops
Dev Ops
Business Customer

27. Amplify Feedback Loops
● Understand your Customers
● Respond to your Customers
● Create Feedback Loops
● Shorten the Feedback Loops

28. 200x
more Frequent Deployments

29. The Scientific Method
The best way to learn since the 17th century

30. The Scientific Method
Ask a
Question
Hypothesis
ExperimentResults
And again
and again
and again…

31. “Ronaldo: first to
arrive at training, last
to leave.”

32. : to do something again and again in order to
become better at it
: to do (something) regularly or constantly as an
ordinary part of your life
Practice

33. If it hurts, do it more often.

34. The Third Way
Culture of
Continual Experimentation
and Learning

35. Culture Of Continuous
Learning
● Make Time For Improving Daily Work
● Reward Teams For Taking (Calculated)
Risks
● Introduce Faults To Increase Resilience

36. 3x
lower Change Failure Rate

37. Case Studies

39. Wealthfront (USA)
● 2.5B$ of assets under management
● Lean Startup approach
● Developers push to production on first
day of work
● Prioritize Safety AND Speed

40. ● Strict coding standards
● Code reviews
● Fix-It days to clean up tests and improve
coverage
● Infrastructure as Code
Wealthfront (USA)

41. ● Dark launches
● Canary deployments
● Sophisticated monitoring and alerting
Wealthfront (USA)

42. Highly regulated FX market in UK
LMAX (UK)

43. “We employ the latest techniques to ensure high software quality, including test driven
development, Continuous Integration (CI) and Continuous Deployment.
Our CI private cloud system constantly runs a battery of over 6000 functional,
acceptance, security and performance tests against the code base to ensure, monitor
and improve quality of execution.
This is matched with the use of industry leading automated deployment and server
configuration management to ensure that the platform matches the code in quality of
build.”
LMAX (UK)
https://www.lmax.com/trading-tech

44. ING Bank (Holland)
● 180 cross-functional teams
● Infrastructure setup from 200 days to 2
hours
● Eliminated 500 duplicated apps
● Replacing ESB with microservices
http://www.slideshare.net/CAinc/continuous-delivery-the-ing-story-i
mproving-time-to-market-with-devops-and-continuous-delivery

47. Culture
The pillarThe pillar

48. Before Agile
Clients
Business
Analysts
Developers Testers
SysAdmins

49. After Agile
Clients
Cross Functional
Team
Operations

50. Bring down the Silos!

51. DevOps
Clients
Cross Functional
Team
GREAT
SUCCESS!
Ops

52. Source: Rouan Wilsenach - DevOpsCulture
Shared
Responsibility
Feedback Automation
Build Quality In
No Silos Autonomous teams
Team
Culture
Organizational
Culture

53. DevOps Departments
(is this a good thing?)
16% in 2014 19% in 2015 22% in 2016

54. 2.2x
more likely to
Recommend their Organization to a Friend

55. Automation
All the things!

56. https://danashby.co.uk/2016/10/19/continuous-testing-in-devops/
You can
automate tests...

57. You can automate...
Deployment
Builds
Cluster
Management
JobScheduling
Failure
Recovery

58. You can automate...
Monitoring
Disaster
Recovery
Logging
Instrumentation

59. You can automate...
Configuration
ManagementSecrets
Management
Service Discovery
Security
Analysis

60. Infrastructure Configuration
Management
An example with a bit more detail

61. Snowflakes
are
beautiful

62. Each one is
unique...

63. Load balancer
Hmmmm...

64. Do you know, for a fact, how any
one of your servers is precisely
configured?

65. Infrastructure as Code
● Auditable
● Readable
● Precise
● Versioned
● (Automatically) Testable

66. # execute 'apt-get update'
exec { 'apt-update': # exec resource named 'apt-update'
command => '/usr/bin/apt-get update' # command this resource will run
}
# install apache2 package
package { 'apache2':
require => Exec['apt-update'], # require 'apt-update' before installing
ensure => installed,
}
# ensure apache2 service is running
service { 'apache2':
ensure => running,
}
It’s just code.
https://www.digitalocean.com/community/tutorials/getting-started-with-puppet-code-manifests-and-modules

68. 24x
faster Recovery from Failures

69. Measurement
Measure (everything) to improve

71. Build. Measure. Learn.
Measure what matters.
Metrics are people, too.
Measure the macro.
http://theleanstartup.com/principles
http://fourhourworkweek.com/2009/05/19/vanity-metrics-vs-actionable-metrics/

72. Build. Measure. Learn.
A/B Tests.
Per-customer metrics.
Funnel metrics and cohort analysis.
Keyword (SEM/SEO) metrics

73. Not only business metrics...

74. Do you know...
the latency of your service?
at P50, P90, P99?
your service-level objective?

75. Do you know...
… when your service is misbehaving?
…why it’s misbehaving?
…when it’s needed?

76. 22%
less time spent on
Unplanned Work or Rework

77. Sharing
is caring.

78. Share...
ideas & implementations
problems & solutions
failures & successes

79. Share...
… inside and outside your organization.
Go to meetups, conferences.
Create communities of interest.

80. Sharing is providing feedback.

81. C ulture
A utomation
M easurement
S haring

82. 50%
less time spent
Remediating Security Issues

83. Practices
Adoption

84. That’s all, folks!
Thank you.