Download as PDF, PPTX
Uploaded byAntons Kranga
DevOps.2D: two dimensions of engineering
The document discusses the essential aspects of DevOps automation and engineering, emphasizing the need to remove organizational silos and build autonomous teams for efficient management of releases. Key topics include idempotent deployments, the use of Git as a source of truth, and the importance of treating infrastructure as code, alongside contemporary practices like incorporating operators in cloud environments. It concludes by advocating for micro clusters and reducing unnecessary tools to streamline processes in engineering.
More Related Content
Similar to DevOps.2D: two dimensions of engineering
DevOps.2D: two dimensions of engineering
- 1. AgileStacks DevOps.2D: two dimensions ofengineering Antons Kranga
- 2. @acankr AgileStacks ~whoami AntonsKranga 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
- 3.
- 4.
- 5. @acankr AgileStacks Culture * Removeorganisational silos * Build autonomous teams * Manage releases Engineering DevOps
- 6. @acankr AgileStacks * Removeorganisational 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 * Removeorganisational 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 talkabout Engineering
- 9.
- 10.
- 11. @acankr AgileStacks Cloud Networking Containers … appdb cachestorage Cluster InfrastructureStack Security Performance Scalability Availability Architectureilities…
- 12. @acankr AgileStacks Cloud Networking Containers … appdb cachestorage Cluster InfrastructureStack DeploymentTechnology Security Performance Scalability Availability Architectureilities…
- 13.
- 14.
- 15.
- 16.
- 17.
- 18.
- 19. @acankr AgileStacks Code git dev ops Contract betweenengineers Code is… Repeatable Evolving
- 20. @acankr AgileStacks Code git dev ops Exact modelof the System Code is… Contract between engineers Repeatable Evolving
- 21. @acankr AgileStacks D forDeployment
- 22.
- 23.
- 24.
- 25.
- 26.
- 27.
- 28.
- 29.
- 30. @acankr AgileStacks Has names Longliving 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 ismy pet? application database
- 32. @acankr AgileStacks Where ismy pet? application database pet cattle
- 33. @acankr AgileStacks Where ismy pet? application database pet cattle code code
- 34. @acankr AgileStacks Where ismy 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
- 36.
- 37.
- 38.
- 39.
- 40. @acankr AgileStacks Idempotent deployment Cloud Networking Containers … Cluster #3ab56d3 Cloud Networking Containers … Cluster === #3ab56d3 Repeateddeployment produces the same result Every component must be idempotent
- 41. @acankr AgileStacks Idempotent deployment Cloud Networking Containers … Cluster #3ab56d3 Cloud Networking Containers … Cluster === #3ab56d3 Repeateddeployment produces the same result Every component must be idempotent Commit hash is an exact version
- 42.
- 43. @acankr AgileStacks Git isthe only source of truth
- 44. @acankr AgileStacks Git isthe only source of truth User makes a pull request to start deployment
- 45.
- 46.
- 47.
- 48. @acankr AgileStacks mike Cloud Networking Containers … Cluster … gitcode + operator #73ba2ef Pull Request webhook notification check difference
- 49. @acankr AgileStacks mike Cloud Networking Containers … Cluster … gitcode + operator #73ba2ef Pull Request webhook notification check difference deploy change
- 50.
- 51.
- 52.
- 53.
- 54.
- 55.
- 56.
- 57. @acankr AgileStacks D forDelivery
- 58. @acankr AgileStacks Every commitcan trigger a new release Wait time is a waste for engineering
- 59.
- 60.
- 61.
- 62.
- 63. @acankr AgileStacks mike gitci#73ba2ef Change must be non deterministic
- 64. @acankr AgileStacks mike gitci#73ba2ef Change must be non deterministic Deployment must be atomic
- 65. @acankr AgileStacks mike gitci#73ba2ef Change must be non deterministic Deployment must be atomic Application must not becomes a pet
- 66. @acankr AgileStacks mike gitci#73ba2ef Change must be non deterministic Deployment must be atomic Application must not becomes a pet Deployment breaks stack immutability
- 67. @acankr AgileStacks Invert dependenciesof application Good delivery means
- 68. @acankr AgileStacks Invert dependenciesof application Application should only make assumptions about it’s state Good delivery means
- 69. @acankr AgileStacks Invert dependenciesof application Application should only make assumptions about it’s state Application should not make assumptions about environment Good delivery means
- 70. @acankr AgileStacks Invert dependenciesof 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
- 71.
- 72. @acankr AgileStacks Operator isthe program that performs automated operation
- 73. @acankr AgileStacks Operator isthe program that performs automated operation Operator typically writes in general purpose programming language
- 74. @acankr AgileStacks Operator isthe program that performs automated operation Reduces need of complex CD tools like GoCD or Spinnaker Operator typically writes in general purpose programming language
- 75.
- 76.
- 77.
- 78.
- 79. @acankr AgileStacks serviceoperator backend react john declare newstate check state
- 80. @acankr AgileStacks serviceoperator backend react john declare newstate converge check state
- 81. @acankr AgileStacks Cloud Networking Containers Cluster git Infrastructure Stack mikegit ci db Scenario: Deployment requires database change
- 82. @acankr AgileStacks Cloud Networking Containers Cluster git Infrastructure Stack mikegit ci db operator Scenario: Deployment requires database change
- 83. @acankr AgileStacks Cloud Networking Containers Cluster git Infrastructure Stack mikegit ci#73ba2ef db operator Scenario: Deployment requires database change app
- 84. @acankr AgileStacks Cloud Networking Containers Cluster git Infrastructure Stack mikegit ci#73ba2ef db operator Scenario: Deployment requires database change app
- 85.
- 86. @acankr AgileStacks You needto think in both D.
- 87. @acankr AgileStacks You needto think in both D. All code must be idempotent
- 88. @acankr AgileStacks You needto think in both D. All code must be idempotent Avoid big over configured clusters. Use micro clusters
- 89. @acankr AgileStacks You needto 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 Thispresentation has been available https://goo.gl/2hGR5S