Slides from Jazoon 2014 http://jazoon.com/talk/Talk205/ DevOps & the Dark Side10 ways to convince your team DevOps is a force for good

1. #DevOps @spoole167
https://www.flickr.com/photos/11568888@N03/

2. THE INFORMATION CONTAINED IN THIS PRESENTATION IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY.
WHILST EFFORTS WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF THE INFORMATION
CONTAINED IN THIS PRESENTATION, IT IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED.
ALL PERFORMANCE DATA INCLUDED IN THIS PRESENTATION HAVE BEEN GATHERED IN A CONTROLLED
ENVIRONMENT. YOUR OWN TEST RESULTS MAY VARY BASED ON HARDWARE, SOFTWARE OR
INFRASTRUCTURE DIFFERENCES.
ALL DATA INCLUDED IN THIS PRESENTATION ARE MEANT TO BE USED ONLY AS A GUIDE.
IN ADDITION, THE INFORMATION CONTAINED IN THIS PRESENTATION IS BASED ON IBM’S CURRENT PRODUCT
PLANS AND STRATEGY, WHICH ARE SUBJECT TO CHANGE BY IBM, WITHOUT NOTICE.
IBM AND ITS AFFILIATED COMPANIES SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES ARISING OUT OF THE
USE OF, OR OTHERWISE RELATED TO, THIS PRESENTATION OR ANY OTHER DOCUMENTATION.
NOTHING CONTAINED IN THIS PRESENTATION IS INTENDED TO, OR SHALL HAVE THE EFFECT OF:
- CREATING ANY WARRANT OR REPRESENTATION FROM IBM, ITS AFFILIATED COMPANIES OR ITS OR THEIR
SUPPLIERS AND/OR LICENSORS
#DevOps @spoole167
2

3. Steve Poole
IBM Developer

Making Java Real Since Version 0.9

Open Source Advocate

DevOps Practitioner (whatever that
means!)

Driving Change
#DevOps @spoole167
3

4. You should be able to leave today knowing
 How to explain what DevOps is and what it is not
 How to explain the benefits of DevOps and the Cloud to developers,
‘suits’ and IT specialists’
 Your next step in promoting DevOps
#DevOps @spoole167

5. There are some who assert
that DevOps is just a fashion
That it’s not needed and might
be counter-productive
Is that true?
Let’s start by looking at what’s
happening in our industry
https://www.flickr.com/photos/whatleydude/
#DevOps @spoole167

6. h#ttpDs:e//wvwOw.flpicksr.com/photos/28581681@N04/ @spoole167

7. The surge of Cloud
technologies that offer
compute ‘on tap’ are
making businesses
think differently about
how to buy and use
computing power
https://www.flickr.com/photos/alexbrn/
#DevOps @spoole167

8. https://www.flickr.com/photos/epsos/
Easier than ever before
a business can buy a
CPU
Just for how long they
need it.
No long term capital
investment.
#DevOps @spoole167

9. https://www.flickr.com/photos/skohlmann/
The ability to have a
tidal ‘cloud burst’
capacity is changing
the way software
needs to be
developed
#DevOps @spoole167

10. 35
30
25
20
15
10
5
0
1/1/13 1/1/14 1/1/15 1/1/16 1/1/17
Traditional
Cloud
Does investment ‘just’
move from one place to
to the other?
Will ‘cloud’ capacity just
pick up the slack?
#DevOps @spoole167

11. 35
30
25
20
15
10
5
0
1/1/13 1/1/14 1/1/15 1/1/16 1/1/17
Traditional
Cloud
Will ‘cloud’ capacity just
pick up the slack?
If I can buy X amount
of CPU over a year…
#DevOps @spoole167

12. 35
30
25
20
15
10
5
0
1/1/13 1/1/14 1/1/15 1/1/16 1/1/17
Traditional
Cloud
I can buy 4X over ¼
the time…
And deliver much
earlier!
#DevOps @spoole167

13. 35
30
25
20
15
10
5
0
1/1/13 1/1/14 1/1/15 1/1/16 1/1/17
Traditional
Cloud
Repeatedly…
You thought you were
busy now..
#DevOps @spoole167

14. cloud capacity is
changing the way
software needs to be
designed
https://www.flickr.com/photos/memebinge/
#DevOps @spoole167

15. Means you can start small and
add what you need when you
need it..
and take it away when
you’re done
Do you design systems
to be this flexible and
resilient?
https://www.flickr.com/photos/44534236@N00/
#DevOps @spoole167

16. “Software as a Service”
profoundly changes the
way software is
designed and
delivered
https://www.flickr.com/photos/derekskey/
#DevOps @spoole167

17. No more delivering
parts that someone
else puts together
No more handing your
code off to others to
use in production.
https://www.flickr.com/photos/pmiaki/
#DevOps @spoole167

18. Your software could go
into production
instantly
Like changing the teeth
on a tunnel boring
machine while it’s still
cutting
Ready for that?
Your
software
https://www.flickr.com/photos/mtaphotos/
#DevOps @spoole167

19. Businesses see the opportunities
here
Improved costs, decreased time-to-market,
shorter time to value
“I can now get my ideas into
production in hours,days or weeks. I
can get immediate feedback AND
then I can improve the idea and
repeat”
#DevOps @spoole167

20. Money changes everything
With a measureable and direct
relationship between $ and CPU/RAM
The financial success or failure of a
project is even easier to see
And that means…
Even more focus on value for money
Soon you’ll be choosing s/w
components based on their memory
footprint!
#DevOps @spoole167

21. “Everything fails all the
time [in the cloud]”
Werner Volgels, CTO, Amazon
Your application has to work in
a new way, in a new place.
Where strange behaviors
happen all the time
It needs to be ‘anti-fragile’
https://www.flickr.com/photos/fireflythegreat/
#DevOps @spoole167

22. Whatever you do – your
world is changing.
Old ways of developing
and delivering software are
being replaced with new,
faster, easier and more
powerful ,
alternatives
#DevOps @spoole167

23. #DevOps @spoole167

24. #DevOps @spoole167

25. How are
we doing
so far?
https://www.flickr.com/photos/tm-tm/
#DevOps @spoole167

26. 1 5 10
20
50
150
160
140
120
100
80
60
40
20
0
Bug fix cost
You’ve all seen this sort
of chart
Think about it
differently..
think “time” and
“delay”
#DevOps @spoole167

27. Too often we hear
about
failures in systems that
come about due a
simple bug occurring in
a complex situation or
in a more organic
environment than
expected
#DevOps @spoole167

28. Case Study: A large bank uses agile techniques to create ‘complete’
solutions in < 3 weeks.
But It takes the Ops team about 15 months elapsed before the deployment
process starts and It take about 3 months to complete deployment
why?
3 weeks to develop vs 3 months to make deployable => continuous
backlog
Continuous backlog => some projects never see the light of day
AND Ops need to talk to Dev 15 months after code complete => you can
guess how that turns out….
#DevOps @spoole167

29. #DevOps @spoole167

30. #DevOps @spoole167

31. #DevOps @spoole167

32. #DevOps @spoole167

33. Design, Code
Unit test
Fix bugs
Functional Test
System test
Stage
Configure
Fix bugs
Helpline
Monitor, backup
upgrade, support, repair
security, compliance
Uses
reality
chasm
#DevOps @spoole167

34. Reinforced team separation
Long feedback cycles
Long time-to-market
Tended to increase
‘Release Panic’
BIG
Reality
DEV Chasm OPS
#DevOps @spoole167

35. Time
# of bugs
Start to panic
here
Really panic
here
DEV
Value here
Client
£
OPS
QA
#DevOps @spoole167

36. Time
# of bugs
Start to panic
here
Really panic
here
DEV
Value here
Client
OPS
QA
No
#DevOps @spoole167

37. Time
# of bugs
Feedback
here
Value here
Client
OPS
QA
DEV
$
#DevOps @spoole167

38. $
Time
# of bugs
And here
Client
OPS
QA
DEV
I want value
here
#DevOps @spoole167

39. $
Time
# of bugs
Client
OPS
Move Left
QA
DEV
#DevOps @spoole167

40. Time
# of bugs
Client
QA
OPS
DEV
$ $ $
#DevOps @spoole167

41. SCM Build Build
Orchestration
Continuous Integration
JUnit
Unit
Test
Continuous Feedback
#DevOps @spoole167

42. JUnit
Continuous Integration
Repositor
y
Deployment tools
Continuous Delivery
Performance & QA
Continuous Feedback
#DevOps @spoole167

43. JUnit
Continuous Integration
Continuous Delivery
Continuous Feedback Hosting
#DevOps @spoole167

44. JUnit
Continuous Integration
Continuous Delivery
Continuous Feedback
Continuous Deployment
Continuous Feedback
Hosting
#DevOps @spoole167

45. JUnit
Continuous Integration
Continuous Delivery
Continuous Feedback Hosting
Days? Weeks?
Months?
#DevOps @spoole167

46. Would you believe < 1hr?
Case Study: A fashion retailer can show measureable increase in sales if a
item similar to that seen in the media can be placed on their on-line store
landing page within 1 hr of it appearing in public.
Each product placement is different so they need a fast, agile, approach
that does not jeopardize their on-line stores availability and quality.
We know how to do this..
#DevOps @spoole167

47. JUnit
Continuous Deployment Pipeline
On premises cloud External Cloud
Cloud
Deployment
Orchestrator
#DevOps @spoole167

48. JUn
it
Continuous Deployment
Continuous Feedback
#DevOps @spoole167

49. Startups through to big businesses are demanding the value
that DevOps & Cloud Technologies can offer
1. Production deployment pipeline up and running in days
2. Updates published in hours or minutes – continuously
DevOps helps transition an organization into this new world…
#DevOps @spoole167

50. The cost?
1. Standardized pipelines
2. Dev and Ops teams working together
3. Greatly expanding your horizons and your technical skills
4. Leaving your comfort zone
#DevOps @spoole167

51. 10 ways to convince your team
DevOps is a force for good
#DevOps @spoole167

52. #1 DevOps is not a technology it’s a
movement
It’s about the next stage in working
together to deliver software
It’s about reducing delivery friction through
knowledge sharing
It’s about applying Agile ideas to Ops
It’s about collaboration and sharing
It’s about changing the culture
Manifesto for Agile Software
Development
Individuals and interactions over
processes and tools
Working software over comprehensive
documentation
Customer collaboration over contract
negotiation
Responding to change over following a
plan
#DevOps @spoole167

53. #2 Working together and exploiting “Infrastructure as Code’
approaches and technologies such as Docker, PaaS’s etc enable Ops
teams to bake in their requirements and Dev & QA teams to run in
modes much more like production
#3 Using virtualisation solutions like IaaS and PaaS make deployment
easier and more ‘self-service’. This reduces the overhead on the Ops
team and hence improves delivery time
#4 Its works the other way too – getting Dev team monitoring and
diagnostics baked-in means less back and forth and no need to
access that production server..
#DevOps @spoole167

54. The demonstrable benefits of using DevOps and
Cloud tech are self evident enough now that
everyone wants to do it
Bringing Development & IT together to solve
deployment problems through sharing and
learning creates an organization with
“Strong IT performance”
This is becoming a major competitive
advantage
#5 - 30x deliveries
#6 - 50% reduction in
deployment failures
#7 2x likely to exceed
important business
goals
Source: puppet labs 2014
#DevOps @spoole167

55. “Since DevOps (and Agile) is about failing early and failing fast that approach
can spill over into the day to day culture – let it happen! Make it safe to fail..
And what about security – how about getting security ‘baked-in’ right at the
design time?”
“Using version control for scripts”
“Automating testing”
“Using TDD or BDD”
“we need to adopt Micro-services
design”
Why can’t we get our systems
proactively monitored?”
“How aboout Pair-programming –
even for ops
“Lets be honest – developers are lazy. If you have
to do it twice you’ll write a script. Ops teams
worry about everything the lazy developer didn’t
do. - like security,”
“low-friction organizations are good at recognizing
and removing obstacles – got an HR system that
gets in the way. Hate that corporate expense
tool? Wish you had a corporate expense tool
instead of the paperwork?”
#DevOps @spoole167

56. #9 – DevOps increases Job Satisfaction
IT Companies with high levels of job satisfaction are mostly likely to be
able to deliver consistently and with high quality. (Hint – who get
chosen 1st?)
#10 Adopting DevOps & the Cloud successfully make your
organisation well positioned for exploiting new capabilities – like
Analystics, BigData or even something like IBM’s Watson
#DevOps @spoole167

57. Businesses need to be able to react faster…
…DevOps and the Cloud are key enablers
DevOps is as much a game changer as Agile was…
…this is a Developer, QA and Ops “renaissance”
Don’t be afraid to learn and experiment…
…you’ll benefit even if the tech doesn’t survive
Agile moved you closer to the customer…
…DevOps moves you closer to the IT team
#DevOps @spoole167

58. 1 – Lean and present Docker and PaaS style options to your peers.
Whether Ops or Dev you’ll see the value
2 – Find a buddy in the other camp.
3 – Get ‘real’ monitoring going across your infrastructure and applications
what ever you can monitor do so. And graph it, put up dashboards.
Look for and learn the warning signs of a failing system and get your peers
and detractors to see the value
(BTW – don’t monitor a system when you need to monitor the app!)
4 – Start to tackle automation
look for the places where others are challenged. And fix it for them.
Introduce Chef, Puppet, Bash, Groovy – the goal is automation 1st – cool tech 2nd
#DevOps @spoole167

59. Ask you organisation some difficult questions:
Deployment frequency?
Speed of deployment?
Deployment success rate?
How quickly service can be restored after a failed deployment?
Time from 1 line of code until in hands of the customer?
#DevOps @spoole167

60. #DevOps @spoole167
Thank
You!
https://www.flickr.com/photos/lens-cap/