This document provides an overview of DevOps, including: 1) It discusses Garry, a product owner whose team had slow and manual software delivery processes until discovering DevOps. 2) DevOps is defined as a culture change involving shared responsibility between development and operations teams to deliver software rapidly through practices like continuous integration, delivery, infrastructure as code, and monitoring. 3) The benefits of DevOps are outlined as faster and more frequent software delivery, improved quality, security, and compliance through automation and visibility across the software lifecycle. 4) Examples of DevOps in action include deploying a web application directly from a development machine versus through an automated build and test process on a separate build box.

1. DevOps
Malinda Kapuruge
Senior Engineer - microservices
09 / Oct / 2018
– why, what and how?

2. This is Garry
… he is a product owner
… sometimes happy

3. Garry got a problem
• Software delivery takes too long
• Not frequent enough
• Poor biz responsiveness
!
We will deploy
a new version
to Prod
(hopefully !!!)

4. This is Garry’s team

5. Garry’s team got a problem too
Manual processes

7. One day, $hit hits the fan …

8. Slow and painful recovery that requires
a considerable time and effort

9. The FIX !
(fingers crossed)

10. So what is wrong here ?

11. It’s NOT the crash !
And, it’s not the person who
added the wrong patch
($hit happens)

12. How do we find a solution ?

13. Garry discovers Devops! No joke !!

14. So, what is Devops ?

15. Hold on!

16. Business / corporate
Dev Ops

17. Dev
Ops
Whatever…

18. Dev
Ops
Hey, I need a new server
to host this
application…
Sure! Create a ticket.
Come back in two
weeks. SORRY! Busy!!

20. So, what the heck is Devops
Anyways ?

21. It is a culture change

22. Shared responsibility

23. Dev Ops
Think ops
Think dev

24. Dev Ops
How can I write better programs,
so that my application can be
easily and quickly deploy/scale ?
How can I provide better ops,
so that the programs can be
built, tested and deployed efficiently?

25. DevOps
How we get things
DONE! DONE !!
Thinking end-to-end …
Visibility end-to-end …

26. Don’t be mistaken.
You still need to do the same work, i.e.,
coding, testing, deploying and monitoring.
But now you doing it in a more integrated and
transparent manner.

27. Devops
• Rapid IT delivery
• Adopt agile and lean practices
• To improve collaboration between operations and development
• Programmable infrastructure
• Automate everything
• Feedback -> optimize
• Identify bottlenecks
• Usage patterns

28. Devops (end to end)

29. Devops is
NOT - a set of tools
- something you can buy

30. Agile!=devops
Agile Values
Devops

31. Cloud
computi
ng
Container
isation
Microse
rvices
Agile
…
Economie
s of scale

33. Devops benefits
• Deliver faster
• Deliver frequently
• Smaller feedback cycles
• Smaller releases
• Quality – fewer mistakes – fewer bugs
• Security (fine-grained access)
• Compliance (business expectations, regulations, standards)
• Accountability (events for every change, auditing)

34. Let’s see some action

35. Let’s deploy a web application
Web browser
End user
Dev machine
Web server

36. Demo 1
Web server
Dev machine

37. Demo 2
Web server
Build box
Dev machine Dev machine

38. What happened there?
• In Demo 1, we deployed a nodejs application to production server
directly from the dev machine.
• Very easy, but very risky.
• In Demo 2, a build box is used to automate the build and test our
change.
• Demo 2 setup shows more maturity compared demo 1
• The code build and deploy concerns are decoupled
• How can we further improve Demo 2 ?

39. The processes and tools may
vary between organizations!

40. Make sure to pick ones that fit
your needs!
Continuously iterate to improve
your processes and tools!!
Aim for higher maturity!!!

41. Let’s
dig
deeper

42. Devops Essentials
plan
create
verify
package
release
configure
monitor
Agile Development
Continuous Integration
Continuous Delivery
Devops

43. Continuous Integration
• Build and test every time there is a code change
• Code commit / merge -> automated build and testing
• Clean master (or develop) branch
• Version control strategies – Git
• Small increments
• Long isolated development -> merge conflicts
Coding in
a branch
Create pull
request
Code
review
Merge

44. Automated Testing
• Build pipeline performs testing, e.g., before every merge
• Quality gates – SonarQube
• Confidence to deliver
• Test pyramid
• Unit tests (test a unit of code in isolation)
• Integration tests (modules tested as a group)
• Regression tests (whenever something is changed)
• Contract tests
• tests the interactions between modules
Acceptance tests
Integration tests
Unit tests

45. Automated Testing
• Test pyramid – a lot of unit tests
• Test coverage reports
• Microservices –> many interactions to test
• Reduce the amount of integration tests
• Slow. Hard to detect issues
• Contract testing as Unit tests (fast)
• Pact Framework
ms1
ms2
ms3
ms4

46. Continuous Delivery
• Software can be released to production at anytime
• A set of design principles
• Any version to any environment
• A deployment pipeline
• Speed and Quality
• Continuous deployment requires continuous delivery

47. Continuous Delivery - example
Code
change
Branch
build and
test
Merge
and test
Build
artifact Test 1
Prod
Staging 1
Staging 1
Test 1
v3
Artifact repo
v1 v2
v2
v2
v2

48. Infrastructure as code
• Versioned
• Repeatable
• Standardized
• Automating tests and configuration free up valuable time
• Deploy the complete system, any day, any time
• Self-recovery
• Idempotence
• Immutability
• Cattle vs Pets
• Reveal possibilities to optimize

49. Infrastructure as code

50. Monitoring and analytics

52. How to measure the success?

53. KPI Description
Change lead time From coding to deploy in production
Change volume Features pushed to production per deploy
Deployment frequency Number of deployments per day
Success rate Successful deployments / total deployments
Time to detect defects Mean time taken to detect a bug in the
production
Time to recover Mean time to recover
Other application metrics For example, improvements in resource
consumption due to devops feedback.

54. Tools
• So many vendors
• So many alternatives
• Cost vs business requirements
• SaaS devops tools
• Vendor lockin
• Overlap different phases of Devops cycles
• Separate ops team. Champions

55. Question time…
What is Blue-Green deployment ?

56. Some new trends
• PaaS
• Containers
• Microservices
• …

57. PaaS
• Challenging and helping at the same time
• Security concerns
• On demand infrastructure
• Wipe out and re-create the complete infrastructure within an hour
• Do that with your own server. Good luck!
• Demand fluctuations - Scalability

58. Containers
• Shared OS
• Application portability
• Isolation
• Cloud friendly
• Docker
• opencontainers.org
https://www.zdnet.com/article/what-is-docker-and-why-is-it-so-darn-popular/

59. Container orchestration
• Kubernetes
• For container orchestration
• Distribution
• Scheduling
• Logical container units
• When there are hundreds of containers to manage
• Works with docker

60. Microservices
The BIG
monolith
ms1
ms2
ms3
ms4
Better granularity - Scalability, security etc.

61. Look for new trends. Innovate
and adapt (or simply copy from
others)
I know I am talking to Uni students.

62. Can Devops Fail?

63. Of course !

64. Causes of failure
• Lack of willingness
• Lack of trust
• Resistance to change
• Lack of leadership vision
• Lack of knowledge
• Devops taken as ops
• Old baggage
• Lack of patience

65. I’m a student. Where should I start ?
• Learn Linux Fundamentals. Please !
• Learn the devops concepts (Here I covered few…)
• Learn Devops-y languages, e.g., Python, Perl, Gradle
• Learn about new devops tools and learn their pros and cons, e.g.,
Kubernetes vs Docker Swarm
• Join a meetup
• Improve soft skills

66. Conclusion
• Devops is a culture change
• There are
• business benefits, e.g., faster feature delivery
• technical benefits, e.g., faster defect detection and recovery
• Concepts
• Devops is not a silver bullet
• Continuously optimize

67. Thank you
Any questions?
@kaushalye