1. Bringing Order to the Chaos Understanding Configuration Management Steven Murawski smurawski@chef.io

2. © ITEdgeintersection. All rights reserved. http://www.ITEdgeintersection.com Introduction  Overview  Setting the Stage  The Industry Response  Modeling Infrastructure as Code  Source Control and the Build Pipeline (Continuous Delivery)  Testing Infrastructure

3. © ITEdgeintersection. All rights reserved. http://www.ITEdgeintersection.com Setting the Stage  In it's current state, IT is stuck in a downward spiral, with problems compounding on each other, making it tougher and tougher to address. This situation make each successive project more likely to be the one that collapses the house of cards.

4. © ITEdgeintersection. All rights reserved. http://www.ITEdgeintersection.com Setting the Stage  This spiral includes:  fragile artifacts become more fragile  technical debt grows  date-driven application projects focus only on features, sacrificing non- functional requirements, which results in more fragile artifacts in production  application deploy take longer, become more turbulent, and continually gets worse  IT Ops is mired in firefighting, and therefore cannot do preventive work or new projects  long feature delivery cycle times result in more political decision making, meaning more focus on features (vs. non-functional requirements)

5. © ITEdgeintersection. All rights reserved. http://www.ITEdgeintersection.com

6. © ITEdgeintersection. All rights reserved. http://www.ITEdgeintersection.com Setting the Stage  The Current State -Six Weeks To Provision a VM!? #ChangeManagementFailSix Weeks To Provision a VM!? #ChangeManagementFail  Executives Are Talking  “So long IT Pro” “So long IT Pro”  2013/2014/2015 State of DevOps Reports  DevOps Enterprise Summit  “Cloud” Has Made Infrastructure as easy as a having a Credit Card and making an API Call

7. © ITEdgeintersection. All rights reserved. http://www.ITEdgeintersection.com The Industry Response  Infrastructure as Code  Apply  Version Control,  Continuous Delivery,  Test-Driven Development,  and Software Development Practices To Infrastructure Management ( like CFEngine, Puppet, Chef, and DSC )

8. © ITEdgeintersection. All rights reserved. http://www.ITEdgeintersection.com

9. © ITEdgeintersection. All rights reserved. http://www.ITEdgeintersection.com

10. © ITEdgeintersection. All rights reserved. http://www.ITEdgeintersection.com

11. © ITEdgeintersection. All rights reserved. http://www.ITEdgeintersection.com

12. © ITEdgeintersection. All rights reserved. http://www.ITEdgeintersection.com Modeling Infrastructure as Code  Move from Imperative to Declarative  Refactor Infrastructure to reduce complexity and duplication  Build in consistency by using the same model across environments  Model with resources

13. © ITEdgeintersection. All rights reserved. http://www.ITEdgeintersection.com From Imperative to Declarative … add-windowsfeature web-server … VS windowsfeature ‘WebServer’ { name = ‘web-server’ }

14. © ITEdgeintersection. All rights reserved. http://www.ITEdgeintersection.com Source Control and the Build Pipeline

15. © ITEdgeintersection. All rights reserved. http://www.ITEdgeintersection.com Testing Infrastructure  Linting  Checks for style and syntax correctness  Examples:  FxCop, StyleCop, Rubocop, Foodcritic, PSScriptAnalyzer

16. © ITEdgeintersection. All rights reserved. http://www.ITEdgeintersection.com Testing Infrastructure  Unit Testing  Checks your logic, with as few side effects as possible  Examples:  xUnit, MSTest, rspec, Pester, ChefSpec

17. © ITEdgeintersection. All rights reserved. http://www.ITEdgeintersection.com Testing Infrastructure  Acceptance or Integration Testing  Checks the end to end use of the component under test  Examples:  xUnit, MSTest, rspec, Pester  Test-kitchen

18. © ITEdgeintersection. All rights reserved. http://www.ITEdgeintersection.com Final Comments  If you want to do infrastructure as code, first  Use source control for anything affecting production (with your team)  Get production artifacts deployed from source control (could be by way of an artifact repository)  Next,  Find one painful part of your configuration process and put some configuration management in place to do that part. (using the above pipeline)

19. © ITEdgeintersection. All rights reserved. http://www.ITEdgeintersection.com References  Culture  The Phoenix Project  Beyond Blame: Learning from Failure and Success  Leading the Transformation: Applying Agile and DevOps Principles at Scale  Automation  Continuous Delivery  The Practice of Cloud Systems Administration  Promise Theory

20. © ITEdgeintersection. All rights reserved. http://www.ITEdgeintersection.com Review

21. © ITEdgeintersection. All rights reserved. http://www.ITEdgeintersection.com Please use Event Board to fill out a session evaluation. Questions? Thank you!