Everything as Code

A simple deck for a presentation on the merits of keeping everything as code from a systems engineering perspective.

Transcript

1. EVERYTHING AS CODE PHIL FENSTERMACHER 1
2. WHAT? Systems and so ware managed by versionable code that is understood by humans and machines. 2
4. user { 'phil': ensure => present, groups => [ 'sudo', 'administrators', ], } 4
5. WHY? You can DevOps! Automation Version everything Shared information 5
6. AUTOMATE EVERYTHING Test Style/Stability/Policy Deploy changes Enforcement Change Requests become a patch 6
7. EVERY. SINGLE. CHANGE. Trivial rollback Smaller, less risky changes Repeatable Leads to overwhelming audit data 7
8. SHARE EVERYTHING Everyone can see what's going on Removes information bottlenecks Informs security teams Improve end user support 8
9. JUMPING AHEAD Infrastructure as Code 9
10. THE USUAL APPLICATIONS Container Builds Configuration Management 10
11. OTHER APPLICATIONS VM Templates (using Packer) Authoritative DNS CAS Applications Database Schema* Docker Services 11
12. GETTING THERE Tooling/Proof of Concept Don't insist on a single tool Security Culture 12
13. LOOKING FORWARD More infrastructure Storage Permissions Collboration 13
14. THANKS! pcfens@wm.edu 14