DevOps.2D: two dimensions of engineering
•
0 likes•129 views
My DevOps engineering presentation at OpenSlava conference, Bratislava, October 2018. This talk is about important engineering concerns related to infrastructure Deployment and application Delivery
Recommended
More Related Content
What's hot
What's hot (20)
Similar to DevOps.2D: two dimensions of engineering
Similar to DevOps.2D: two dimensions of engineering (20)
More from Antons Kranga
More from Antons Kranga (14)
Recently uploaded
Recently uploaded (20)
DevOps.2D: two dimensions of engineering
- 1. AgileStacks DevOps.2D: two dimensions of engineering Antons Kranga
- 2. @acankr AgileStacks ~whoami Antons Kranga Director of Engineering @ Agile Stacks Building next-gen DevOps automation @acankr github.com/akranga anton@agilestacks.com Speaking (on the left) @OpenSlava 2013, 2014, 2015 • DevOps Automation • Platform as a Service • Containers
- 5. @acankr AgileStacks Culture * Remove organisational silos * Build autonomous teams * Manage releases Engineering DevOps
- 6. @acankr AgileStacks * Remove organisational silos * Build autonomous teams * Manage releases * Automate Infrastructure * Build Continuous Delivery * Build Operators * Collect and visualise feedback data * Cloud computing * Containers Culture Engineering DevOps
- 7. @acankr AgileStacks * Remove organisational silos * Build autonomous teams * Manage releases * Automate Infrastructure * Build Continuous Delivery * Build Operators * Collect and visualise feedback data * Cloud computing * Containers reading reading (???) DevOps Culture Engineering
- 8. @acankr AgileStacks Let’s talk about Engineering
- 10. @acankr AgileStacks Cloud Networking Containers … appdb cachestorage Cluster Infrastructure Stack
- 11. @acankr AgileStacks Cloud Networking Containers … appdb cachestorage Cluster Infrastructure Stack Security Performance Scalability Availability Architectureilities…
- 12. @acankr AgileStacks Cloud Networking Containers … appdb cachestorage Cluster Infrastructure Stack DeploymentTechnology Security Performance Scalability Availability Architectureilities…
- 19. @acankr AgileStacks Code git dev ops Contract between engineers Code is… Repeatable Evolving
- 20. @acankr AgileStacks Code git dev ops Exact model of the System Code is… Contract between engineers Repeatable Evolving
- 21. @acankr AgileStacks D for Deployment
- 26. @acankr AgileStacks Code mike Disposable Deployment Cloud Networking Containers … Cluster … Stack is broken
- 29. @acankr AgileStacks Pet vs Cattle
- 30. @acankr AgileStacks Has names Long living entity Requires patching, backups etc Often needs manual nursing Described as configuration Pet Cattle Have numbers not name Short living entity Immutable Dispose instead of nursing Described as code
- 31. @acankr AgileStacks Where is my pet? application database
- 32. @acankr AgileStacks Where is my pet? application database pet cattle
- 33. @acankr AgileStacks Where is my pet? application database pet cattle code code
- 34. @acankr AgileStacks Where is my pet? application database pet cattle user data
- 35. @acankr AgileStacks Secrets (passwords, ssl etc) Feature toggles Certificates (TLS) Domain names User data backups Good pets
- 37. @acankr AgileStacks Code john Cloud Networking Containers … Cluster #3ab56d3 Idempotent deployment
- 39. @acankr AgileStacks Idempotent deployment Cloud Networking Containers … Cluster #3ab56d3 Cloud Networking Containers … Cluster === #3ab56d3 Repeated deployment produces the same result
- 40. @acankr AgileStacks Idempotent deployment Cloud Networking Containers … Cluster #3ab56d3 Cloud Networking Containers … Cluster === #3ab56d3 Repeated deployment produces the same result Every component must be idempotent
- 41. @acankr AgileStacks Idempotent deployment Cloud Networking Containers … Cluster #3ab56d3 Cloud Networking Containers … Cluster === #3ab56d3 Repeated deployment produces the same result Every component must be idempotent Commit hash is an exact version
- 43. @acankr AgileStacks Git is the only source of truth
- 44. @acankr AgileStacks Git is the only source of truth User makes a pull request to start deployment
- 47. @acankr AgileStacks mike Cloud Networking Containers … Cluster … gitcode + operator Pull Request #73ba2ef web hook notification
- 48. @acankr AgileStacks mike Cloud Networking Containers … Cluster … gitcode + operator #73ba2ef Pull Request web hook notification check difference
- 49. @acankr AgileStacks mike Cloud Networking Containers … Cluster … gitcode + operator #73ba2ef Pull Request web hook notification check difference deploy change
- 56. @acankr AgileStacks Challenges Cloud Networking Containers … Cluster #3ab56d3 Cloud Networking Containers … Cluster gitcode + #3ab56d3 QA production Time to deploy Deployment success rate
- 57. @acankr AgileStacks D for Delivery
- 58. @acankr AgileStacks Every commit can trigger a new release Wait time is a waste for engineering
- 59. @acankr AgileStacks Cloud Networking Containers … Cluster Cloud Networking Containers … Cluster Cloud Networking Containers … Cluster development QA production mike
- 60. @acankr AgileStacks Cloud Networking Containers … Cluster Cloud Networking Containers … Cluster Cloud Networking Containers … Cluster development QA production mike
- 61. @acankr AgileStacks Cloud Networking Containers … Cluster Cloud Networking Containers … Cluster Cloud Networking Containers … Cluster development QA production mike git ci#73ba2ef
- 62. @acankr AgileStacks Cloud Networking Containers … Cluster Cloud Networking Containers … Cluster Cloud Networking Containers … Cluster development QA production mike git ci#73ba2ef
- 63. @acankr AgileStacks mike git ci#73ba2ef Change must be non deterministic
- 64. @acankr AgileStacks mike git ci#73ba2ef Change must be non deterministic Deployment must be atomic
- 65. @acankr AgileStacks mike git ci#73ba2ef Change must be non deterministic Deployment must be atomic Application must not becomes a pet
- 66. @acankr AgileStacks mike git ci#73ba2ef Change must be non deterministic Deployment must be atomic Application must not becomes a pet Deployment breaks stack immutability
- 67. @acankr AgileStacks Invert dependencies of application Good delivery means
- 68. @acankr AgileStacks Invert dependencies of application Application should only make assumptions about it’s state Good delivery means
- 69. @acankr AgileStacks Invert dependencies of application Application should only make assumptions about it’s state Application should not make assumptions about environment Good delivery means
- 70. @acankr AgileStacks Invert dependencies of application Application should only make assumptions about it’s state Application should not make assumptions about environment Application can change state of the stack via operators Good delivery means
- 72. @acankr AgileStacks Operator is the program that performs automated operation
- 73. @acankr AgileStacks Operator is the program that performs automated operation Operator typically writes in general purpose programming language
- 74. @acankr AgileStacks Operator is the program that performs automated operation Reduces need of complex CD tools like GoCD or Spinnaker Operator typically writes in general purpose programming language
- 79. @acankr AgileStacks serviceoperator backend react john declare new state check state
- 80. @acankr AgileStacks serviceoperator backend react john declare new state converge check state
- 81. @acankr AgileStacks Cloud Networking Containers Cluster git Infrastructure Stack mike git ci db Scenario: Deployment requires database change
- 82. @acankr AgileStacks Cloud Networking Containers Cluster git Infrastructure Stack mike git ci db operator Scenario: Deployment requires database change
- 83. @acankr AgileStacks Cloud Networking Containers Cluster git Infrastructure Stack mike git ci#73ba2ef db operator Scenario: Deployment requires database change app
- 84. @acankr AgileStacks Cloud Networking Containers Cluster git Infrastructure Stack mike git ci#73ba2ef db operator Scenario: Deployment requires database change app
- 86. @acankr AgileStacks You need to think in both D.
- 87. @acankr AgileStacks You need to think in both D. All code must be idempotent
- 88. @acankr AgileStacks You need to think in both D. All code must be idempotent Avoid big over configured clusters. Use micro clusters
- 89. @acankr AgileStacks You need to think in both D. All code must be idempotent Avoid big over configured clusters. Use micro clusters Reduce tools if you can
- 90. @acankr AgileStacks Thank you https://www.slideshare.net/akranga/devops2d-two-dimensions-of-engineering This presentation has been available https://goo.gl/2hGR5S