Download as PDF, PPTX
![83
•Someone forks our GitHub repo
•They write a post: rake new_post[‘Some post’]
Our new process is
awesome
Wednesday, August 21, 13](https://image.slidesharecdn.com/eac-130821093133-phpapp02/75/Everything-as-Code-111-2048.jpg)
![83
•Someone forks our GitHub repo
•They write a post: rake new_post[‘Some post’]
•They submit a pull request to us.
Our new process is
awesome
Wednesday, August 21, 13](https://image.slidesharecdn.com/eac-130821093133-phpapp02/75/Everything-as-Code-112-2048.jpg)
![83
•Someone forks our GitHub repo
•They write a post: rake new_post[‘Some post’]
•They submit a pull request to us.
•We revise it via a GitHub discussion
Our new process is
awesome
Wednesday, August 21, 13](https://image.slidesharecdn.com/eac-130821093133-phpapp02/75/Everything-as-Code-113-2048.jpg)
![83
•Someone forks our GitHub repo
•They write a post: rake new_post[‘Some post’]
•They submit a pull request to us.
•We revise it via a GitHub discussion
•We merge the commit.
Our new process is
awesome
Wednesday, August 21, 13](https://image.slidesharecdn.com/eac-130821093133-phpapp02/75/Everything-as-Code-114-2048.jpg)
![83
•Someone forks our GitHub repo
•They write a post: rake new_post[‘Some post’]
•They submit a pull request to us.
•We revise it via a GitHub discussion
•We merge the commit.
•DEPLOY!
Our new process is
awesome
Wednesday, August 21, 13](https://image.slidesharecdn.com/eac-130821093133-phpapp02/75/Everything-as-Code-115-2048.jpg)
Uploaded byWayne Walls
Everything as Code
This document discusses DevOps concepts and tools. It introduces configuration management tools like Chef, Puppet, and Ansible that can automate server infrastructure setup. Monitoring and metrics collection with Nagios and Graphite is also covered. The document advocates for adopting an Agile development methodology and continuous delivery model. It shares one organization's experience transitioning their blog to use GitHub, Octopress, and Rackspace Cloud Files which improved their content publishing workflow.
In this document
Powered by AI
Introduction to DevOps by Hart Hoover. Overview of cultural methodology and core principles.
Overview of configuration management tools like Chef, Puppet, and Ansible. Explains nodes, environments, and desired state of configurations.
Discusses monitoring through Nagios and plugins. Highlights automation as a core principle in DevOps.
No culture buy-in means failure in DevOps implementation. Discusses software development lifecycle and integration.
Emphasis on Scrum and Kanban methodologies within DevOps practices, illustrating agile teams and key meetings.Importance of continuous delivery, quick fixes post-deployment, testing during development phases.
Focus on open-source solutions, industry standards, and themes relevant to DevOps tools and strategies.
Highlights the transformation of a complicated process to a streamlined GitHub workflow, showcasing how effective processes enhance productivity.
Wraps up the session, encouraging participation and summarizing the key points discussed.
More Related Content
Everything as Code
- 1. everything as code hart hoover cloudevangelist Wednesday, August 21, 13
- 2. WHAT IS devops? 2 Wednesday,August 21, 13
- 3. 3 Culture & WorkMethodology Wednesday, August 21, 13
- 4. 4 What Does DevOpsEnable? Wednesday, August 21, 13
- 5.
- 6.
- 7.
- 8.
- 9.
- 10.
- 11.
- 12.
- 13.
- 14.
- 15.
- 16.
- 17.
- 18. •Nodes: Servers •Environments: Groupsof nodes (Dev/QA/Prod) •Recipes: Describes the desired state of a node •Cookbooks: Group of Recipes •Roles: Group of Cookbooks (Web) •Attribute: information about the current state of a node 18 Wednesday, August 21, 13
- 19.
- 20.
- 21.
- 22. •Nodes: Servers •Environments: Groupsof nodes (Dev/QA/Prod) •Manifests: Describes the desired state of a node •Catalog: Group of Manifests •Facts: information about the current state of a node 22 Wednesday, August 21, 13
- 23. PUPPET TOOLS 23 Test Kitchen- soon librarian-puppet puppet-lint Vagrant Wednesday, August 21, 13
- 24. PUPPET vs. CHEF 24 Wednesday,August 21, 13
- 25.
- 26.
- 27. •Nodes: Minions •Environments: Groupsof nodes (Dev/QA/Prod) •States: Describes the desired state of a node •Grains: information about the current state of a node 27 Wednesday, August 21, 13
- 28.
- 29.
- 30. •Hosts: Servers •Groups: Groupsof Hosts (Dev/QA/Prod) •Play: Describes the desired state of a Host. •Playbook: Group of Plays •Roles: Group of Hosts (Web) •Facts: information about the current state of a Host. 30 Wednesday, August 21, 13
- 31. ANSIBLE vs. SALTSTACK 31 Wednesday,August 21, 13
- 32. 32 Measure All theThings Wednesday, August 21, 13
- 33. CollectD + GRAPHITE 33 Wednesday,August 21, 13
- 34. CollectD + GRAPHITE 34 Wednesday,August 21, 13
- 35. CollectD + GRAPHITE 35 Wednesday,August 21, 13
- 36.
- 37.
- 38. 38 • Application MonitoringService • Agent-based • Plugins Wednesday, August 21, 13
- 39. 39 Automate All theThings Wednesday, August 21, 13
- 40.
- 41.
- 42.
- 43.
- 44.
- 45.
- 46. 42 SOME OF THESE!= SUCCESS Wednesday, August 21, 13
- 47. 43 NO CULTURE BUY-IN= NO DEVOPS Wednesday, August 21, 13
- 48. 44 SOFTWARE DEVELOPMENT LIFECYCLE Wednesday,August 21, 13
- 49.
- 50.
- 51. 45 DEV OPS+ QA+ Wednesday,August 21, 13
- 52. 45 DEV OPS+ QA+ = DEVOPS Wednesday,August 21, 13
- 53. How to Embrace DevOps 46 SCRUMKANBAN AGILE Wednesday, August 21, 13
- 54. SCRUM 47 Scrum Master Product OwnerDevelopers Wednesday, August 21, 13
- 55. Product Backlog Sprint Backlog Sprint Working increment of thesoftware 48 1. Design 5. QA 2. Build 4. Release 3. Configure Wednesday, August 21, 13
- 56. 49 1. Design 5. QA2. Build 4. Release 3. Configure Wednesday, August 21, 13
- 57. SCRUM: KEY MEETINGS 50 BacklogGrooming Sprint Planning Daily Scrum Sprint Review Sprint Retrospective Wednesday, August 21, 13
- 58. Features In ProgressBlocked Tabled Testing Complete Feature A Feature B Feature C 51 KANBAN Wednesday, August 21, 13
- 59. Features In ProgressBlocked Tabled Testing Complete Feature A Feature B Feature C 52 KANBAN Wednesday, August 21, 13
- 60. Features In ProgressBlocked Tabled Testing Complete Feature A Feature B Feature C Feature E Feature D 52 KANBAN Wednesday, August 21, 13
- 61. Features In ProgressBlocked Tabled Testing Complete Feature AFeature BFeature C Feature E Feature G 53 KANBAN Wednesday, August 21, 13
- 62. Features In ProgressBlocked Tabled Testing Complete Feature AFeature BFeature C Feature E Feature D Feature F Feature G 53 KANBAN Wednesday, August 21, 13
- 63. Features In ProgressBlocked Tabled Testing Complete Feature A Feature B Feature C Feature E Feature D Feature F Feature G 54 KANBAN Wednesday, August 21, 13
- 64. Features In ProgressBlocked Tabled Testing Complete Feature A Feature B Feature C Feature E Feature D Feature F Feature G Feature H Feature I 54 KANBAN Wednesday, August 21, 13
- 65. Features In ProgressBlocked Tabled Testing Complete Feature A Feature B Feature C Feature EFeature D Feature F Feature G Feature H Feature I 55 KANBAN Wednesday, August 21, 13
- 66. AGILE DEVELOPMENT • Individualsand interactions over process and tools • Working software over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a plan 56 Wednesday, August 21, 13
- 67. AGILE TEAMS 57 Traditional TeamsAGILE Teams Project Manager / Team Lead Servant Leader / Facilitator Self-Organized Wednesday, August 21, 13
- 68.
- 69.
- 70. 60 What Version isin Production? Wednesday, August 21, 13
- 71. 61 Issues are Found,Fixed & Redeployed Quickly Wednesday, August 21, 13
- 72. 62 Test as YouDevelop Wednesday, August 21, 13
- 73. 63 Same Best Practices Wednesday,August 21, 13
- 74. 64 Tag, Branch &Release Code that Defines Infra Wednesday, August 21, 13
- 75. 65 Coverage Lifecycle OverVarious Stages Wednesday, August 21, 13
- 76.
- 77.
- 78.
- 79.
- 80.
- 81.
- 82.
- 83. 70 INDUSTRY STANDARD! OPEN SOURCE! Wednesday,August 21, 13
- 84.
- 85.
- 86. 70 THEMES! PLUGINS! INDUSTRY STANDARD! OPEN SOURCE! WEKNOW IT! Wednesday, August 21, 13
- 87.
- 88.
- 89.
- 90. 74 Scaling WordPress is complicated Wednesday,August 21, 13
- 91. 74 Scaling WordPress is complicated Wednesday,August 21, 13
- 92. 75 Our process wasterrible Wednesday, August 21, 13
- 93. 75 •Someone emails oneof us a post Our process was terrible Wednesday, August 21, 13
- 94. 75 •Someone emails oneof us a post •We read it and send it back to them for revisions. Our process was terrible Wednesday, August 21, 13
- 95. 75 •Someone emails oneof us a post •We read it and send it back to them for revisions. •They rewrite it and send us a new file... via email. Our process was terrible Wednesday, August 21, 13
- 96. 75 •Someone emails oneof us a post •We read it and send it back to them for revisions. •They rewrite it and send us a new file... via email. •Round and round we go. Our process was terrible Wednesday, August 21, 13
- 97. 75 •Someone emails oneof us a post •We read it and send it back to them for revisions. •They rewrite it and send us a new file... via email. •Round and round we go. •We email the finished article to our editor, Andrew. Our process was terrible Wednesday, August 21, 13
- 98. 75 •Someone emails oneof us a post •We read it and send it back to them for revisions. •They rewrite it and send us a new file... via email. •Round and round we go. •We email the finished article to our editor, Andrew. •Andrew emails us a different copy with his edits. Our process was terrible Wednesday, August 21, 13
- 99. 75 •Someone emails oneof us a post •We read it and send it back to them for revisions. •They rewrite it and send us a new file... via email. •Round and round we go. •We email the finished article to our editor, Andrew. •Andrew emails us a different copy with his edits. •We copy/paste into WordPress and post. Our process was terrible Wednesday, August 21, 13
- 100.
- 101.
- 102.
- 103. 79 Rackspace Cloud Files isGLOBAL Wednesday, August 21, 13
- 104. 80 Rackspace Cloud Files isCHEAP Wednesday, August 21, 13
- 105.
- 106.
- 107.
- 108.
- 109. 83 Our new processis awesome Wednesday, August 21, 13
- 110. 83 •Someone forks ourGitHub repo Our new process is awesome Wednesday, August 21, 13
- 111. 83 •Someone forks ourGitHub repo •They write a post: rake new_post[‘Some post’] Our new process is awesome Wednesday, August 21, 13
- 112. 83 •Someone forks ourGitHub repo •They write a post: rake new_post[‘Some post’] •They submit a pull request to us. Our new process is awesome Wednesday, August 21, 13
- 113. 83 •Someone forks ourGitHub repo •They write a post: rake new_post[‘Some post’] •They submit a pull request to us. •We revise it via a GitHub discussion Our new process is awesome Wednesday, August 21, 13
- 114. 83 •Someone forks ourGitHub repo •They write a post: rake new_post[‘Some post’] •They submit a pull request to us. •We revise it via a GitHub discussion •We merge the commit. Our new process is awesome Wednesday, August 21, 13
- 115. 83 •Someone forks ourGitHub repo •They write a post: rake new_post[‘Some post’] •They submit a pull request to us. •We revise it via a GitHub discussion •We merge the commit. •DEPLOY! Our new process is awesome Wednesday, August 21, 13
- 116.
- 117.
- 118.
- 119.
- 120.
- 121.
- 122.
- 123.
- 124.
- 125.
- 126.
- 127.