This morning on #c9d9 we talked about Process-as-Code. DevOps at scale requires predictability and consistency. Your application code is versioned. Infrastructure-as-code defines your environments. But what about the process? How do you define your processes as code? What are some use cases and best-practices for ensuring your automation is versionable, testable, and repeatable.
Watch the replay of the episode :
This episode features:
David-Blank Edelman Technical Evangelist (with a hard 'g') for Apcera. USENIX board member. Talkin' about System Administration/DevOps/SRE, Perl, and stuff. @OtterBook | www.apcera.com/blog
J. Paul Reed J. Paul Reed has over 15 years experience in the trenches as a build/release engineer, working with such companies as VMware, Mozilla, Symantec, and Salesforce. He speaks internationally on release engineering, DevOps, operational complexity, and human factors. @jpaulreed | jpaulreed.com
Mark Chassy Mark is learning how to make himself dispensable with automation and continuous data... @mark_chassy
Michael Wittig Cloud Specialist. Author of Amazon Web Services in Action. Software Engineer, Speaker, Teacher and Consultant. @hellomichibye | cloudonaut.io
John Harris Snake, Gopher & Whale handler. Frequent Flyer. Automates all the things. Continuous Delivery Evangelist. @johnharris85 | johnharris.io