The document discusses migrating from a legacy runbook process to a more modern DevOps approach using automation. It notes that while people are often reluctant to automate due to speed and complexity concerns, DevOps relies on collaboration and understanding colleagues' work. The document encourages starting the transition to automation using tools like Ansible and offers contact information for assistance.

1. Migrating the runbook -
a journey from legacy to devops

3. The runbook

6. So why don't people automate?
Speed of entry - just type
It's too hard
"I only need to do this once"

7. So why don't people automate?

8. So why don't people automate?

9. DevOps is common sense

10. Collaboration
Rule One: Understand what your colleagues actually do*
* http://www.ted.com/talks/yves_morieux_as_work_gets_more_complex_6_rules_to_simplify

11. Collaboration

12. Collaboration

13. Collaboration

14. Collaboration + Automation

15. But where do I start?
#!/usr/bin/env perl
for(split(//,'))*))91:+9.*4:1A1+9,1))2*:..)))2*:
31.-1)4131)1))2*:3"')){for(ord){$i+=$_&7;grep(vec($s,
$i++,1)=1,1..($_>>3)-4);}}print"$sn";

16. But where do I start?

17. But where do I start?

19. Mark Phillips
@thismarkp
ansible.com/get-started
Stand H2 - come say hello!