'

Infrastructure as Code: Why it Matters

Понравилась презентация – покажи это...





Слайд 0

Infrastructure as Code Why it matters


Слайд 1

Carl Caum Puppet Labs Technical Marketing (I don’t know what that means either) @ccaum


Слайд 2

DevOps


Слайд 3

DevOps is a response to the adversarial culture found in traditional IT organizations


Слайд 4

“Ops won’t let us use the latest Ruby for some reason.” “Don’t the developers know anything about logging?” “Why can’t the developers build packages?” “Why does it take so long for Ops to deploy this code?” “Why won’t Ops just make this change? It’s small” “The devs don’t care that this code doesn’t scale.”


Слайд 5

The cause Dev Ops


Слайд 6

The solution Dev DevOps Ops


Слайд 7

Product Delivery Process Problem Statement Problem Prioritization Design / Development Deployment Monitoring Product Management Dev DevOps Ops


Слайд 8

The Three Ways -- Gene Kim


Слайд 9

Systems Thinking Understand the performance of the entire system, not each individual silo


Слайд 10

Amplify Feedback Loops Build quick, short, feedback into the process


Слайд 11

Culture of Experimentation and Learning Enforce a culture of continuous experimentation, risk taking, and learning.


Слайд 12

Top 5 Predictors of IT Performance Puppet Labs DevOps Survey


Слайд 13

● Peer reviewed change process When teams hold themselves accountable for the quality of its code through peer review, performance increases. Change Approval Boards (CABs) decrease performance. ● CABs have negligible impact on system stability while significant negative impact on throughput.


Слайд 14

● Version Control Single source of truth ● Causality is easily determined ● Benefits extend to both system and application configuration


Слайд 15

● Proactive Monitoring Diagnose problems faster ● Test the application, not just the infrastructure ● Post deploy tests


Слайд 16

High Trust Culture ● Bureaucracy kills (productivity) ● Trust increases throughput


Слайд 17

● Win-Win culture Act with expertise, not authority ● Interactions are about both teams achieving the shared business goals


Слайд 18

Empathy rarely extends beyond our line of sight


Слайд 19

● Help devs set up the development environment [ops] Empathy ● Help devs set up the CI system ● Understand the required infrastructure throughout the feature’s development


Слайд 20

● Understand the constant fires Ops deals with [dev] Empathy ● Help develop the deployment process for the feature ● Be on call ● Monitor the application post deployment


Слайд 21

The Business


Слайд 22

● Speed Business Goals ● Innovation ● Availability ● Stability


Слайд 23

● Time-to-market matters [Business] Speed ● Cycle time matters ● Dependable cadence matters


Слайд 24

● Collaboration [Business] Innovation ● Experimentation ● Rapid validation ● Market clarity


Слайд 25

[Business] Availability ● 70% of all downtime is caused by configuration drift and unauthorized configuration change* ● Downtime costs $2.5 billion for Fortune 1000* *Wiley Global Research


Слайд 26

[Business] Stability ● Infrastructure Trust ● Mean-time to recovery


Слайд 27

Infrastructure as Code


Слайд 28

DevOps is to Infrastructure as Code as Agile is to Scrum


Слайд 29

Infrastructure as Code is a requirement for DevOps, but is not sufficient


Слайд 30

Pragmatism


Слайд 31

Pragmatic Goals ● ● ● ● ● Production-like Dev Env Peer Review and Pairing Continuous Delivery Policy Driven Development Auditing


Слайд 32

● Code is portable Production-like Dev Env ● Code is reusable ● Code is version controlled (Vagrant is awesome)


Слайд 33

● Code can be contributed by anyone Peer Review and Pairing ● Code changes can be reviewed by anyone ● Code can be worked on as a team (give me git or give me death)


Слайд 34

● Code is repeatable Continuous Delivery ● Code is shareable ● Code is promotable ● Code is testable


Слайд 35

● Policies are for humans, not computers Policy Driven Development ● Constraints can be tested and enforced with code ● Tests can be run in any environment since code is portable


Слайд 36

● Code execution can provide detailed, accurate reports on actions taken Auditing ● Code promotion and execution provide authorization records ● Code run reports provide defensible audit trails


Слайд 37

Tips


Слайд 38

● Automate the most repetitive tasks in Ops Start ● Use Law of Accelerating Returns to increase admins’ free time ● Once a FTE’s worth of time is gained, have sysadmins spend more and more time working alongside developers


Слайд 39

● Approachability ● Opinionated The Language ● Declarative ● Idempotency ● Reporting


Слайд 40

Conclusion


Слайд 41

DevOps is about culture but requires pragmatism


Слайд 42

Collaboration is key in relation to the product delivery process


Слайд 43

Infrastructure as Code is necessary but is insufficient


Слайд 44

The language matters (period)


Слайд 45

Data Is Awesome Check out the Puppet Labs DevOps survey https://puppetlabs.com/2014-devops-report


Слайд 46

fin


Слайд 47


×

HTML:





Ссылка: