Ryan Cook - Ignite - Oh no! MGMT wants to do DevOps now

Transcript

2. Oh No! MGMT wants to do DevOps Now
3. My Adventures Joined Red Hat 2 years ago Inception Convergence Systems Design and Engineering @cooktheryan
4. Take a deep breath PAUSE
5. Why change? Enable everyone to do their best work Everyone has “skin in the game” Move faster Safer deployments All voices are heard The CTO read an article about it
6. Automation
7. Pre-Automation Workflow Developer writes and packages code Developer tells Ops code is ready Change record created Ops run scripts from Developer on system(s) Ops tells Developers/QA code deployment has been successful Developer/QA tells Ops to deploy code in next environment
9. Quick Wins! Pre-Bake Images TravisCI Code Reviews Jenkins Ansible Cucumber
10. Not as quick of Wins Container/Container Platform Sandbox Environment Re-write of applications for elasticity Infrastructure as Code Intelligent scaling
11. Change Record APIs! Automatically submit change requests Post Git messages into a change Check status of a change before proceeding
12. Stay informed IRC, Slack, or other group chat system Many to Many communication Tie in automation Irregularity reporting Change Records Git log Start and Stop times
13. Automation workflow Developer pushes a commit Jenkins polls git server Unit testing Artifact created Notification of deployment beginning Artifact deployed to systems Cucumber testing Notification of success/failure Update Change Deploy to next environment
14. Measure success…or failure Change Record reports Jenkins Job Output ELK Splunk
15. Culture
16. Question everything
17. Everyone’s opinion matters Regardless of title, position, age, race, etc
18. Communication Agile retrospectives Complaint Fest Plan work LGTM and +1’s on changes
19. Bad behaviors That’s not my job Ryan broke the environment Ryan broke the environment again
20. Demos Help ensure planned work is getting done More people asking questions Inspire other teams
21. ! = Netflix And that’s ok