Developers doing Operations using Automation<\/h1>\n
<\/p>\n
The end goal of DevOps is to remove all obstacles for developers to rapidly deliver software features, fixes, and run experiments that result in business innovation. \u00a0A good first step towards this goal, for many enterprises, may very well be to move their development and operations teams closer together and improve communications between teams. \u00a0But this\u00a0not enough. If your developers are waiting on IT resources, and unable to easily operate their own applications across environments, then you\u2019re not doing DevOps; at least not yet.<\/p>\n
Slide 66: Adrian Cockroft, Fast Delivery<\/a><\/p>\n Let\u2019s be clear: developers don\u2019t <\/i>want to operate infrastructure (compute, network, storage), manage OS images and patches, implement security policies, etc. You need a solid operations team for all that!<\/p>\n Developers do <\/i>want to operate their applications, end-to-end. This means that developers should be able to rapidly release,\u00a0deploy, and manage their application components in any environment, in a secure, scalable, and repeatable manner. This also means that developers are now responsible for making sure that their applications are always running properly in production.<\/p>\n Enterprises are re-organizing around the concept of DevOps [2]. This does not mean creating a job with DevOps in the title. This means setting up a team whose charter is to enable DevOps, and end-to-end automation, within the Enterprise. In many enterprises, this is a Platform team that works closely with, and supports, several DevOps teams.<\/p>\n Slide 41: Adrian Cockroft, Fast Delivery<\/a><\/p>\n Terms like automation and orchestration are used fairly loosely in our industry and can mean several things. To enable the automated delivery of applications, there are at least three relevant areas of automation to consider:<\/p>\n Each area of automation has different needs, and no single tool will be able to address all of these well. For example, configuration management tools, like Chef and Ansible, are good at infrastructure automation, Jenkins is good for build automation, and newer solutions like Nirmata are purpose built for application automation.<\/p>\n To accomplish the automation required, your operations team will probably need to pick up some automation and programming skills. But that, again, is not the end goal of DevOps or what DevOps is all about.<\/p>\n An important point to consider, when selecting automation tools, is that enterprises will need visibility and control across all of these layers. Platforms\u00a0that attempt to abstract away, or hide the underlying layers, will not work as they quickly become a bottleneck for making changes in the tool chain.<\/p>\n DevOps is:<\/p>\n Developers doing Operations using Automation<\/p><\/blockquote>\n This is the simple definition for DevOps that I\u2019ve started using. When using this definition, whether DevOps is a culture change, or whether its operations teams learning to code, or developers learning to operate, does not seem to matter as much. The goal is clear: get\u00a0your business to succeed by enabling\u00a0product development teams to innovate faster!<\/p>\n Let me know what you think, and if you have any suggestions on how we can improve our understanding of DevOps, and help move our industry forward.<\/p>\n Jim Bugwadia source:\u00a0nirmata.com<\/p>\n [1] Fast Delivery<\/a>, \u00a0Adrian Cockroft,<\/p>\n [2] Organizing Enterprise DevOps<\/a>, Jim Bugwadia<\/p>\n","protected":false},"excerpt":{"rendered":" Over the last few years, I\u2019ve spent quite a bit of time learning and\u00a0discussing DevOps, as well as\u00a0putting into practice\u00a0DevOps principles and values. I\u2019ve read several \u00a0articles that provide detailed\u00a0descriptions of what DevOps is, and what DevOps is not. Most of these talk about moving development and operations teams closer together, the cultural changes involved,\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[32],"tags":[],"class_list":["post-549","post","type-post","status-publish","format-standard","hentry","category-leadership"],"_links":{"self":[{"href":"https:\/\/adriangrigoras.com\/blog\/wp-json\/wp\/v2\/posts\/549","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/adriangrigoras.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/adriangrigoras.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/adriangrigoras.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/adriangrigoras.com\/blog\/wp-json\/wp\/v2\/comments?post=549"}],"version-history":[{"count":1,"href":"https:\/\/adriangrigoras.com\/blog\/wp-json\/wp\/v2\/posts\/549\/revisions"}],"predecessor-version":[{"id":550,"href":"https:\/\/adriangrigoras.com\/blog\/wp-json\/wp\/v2\/posts\/549\/revisions\/550"}],"wp:attachment":[{"href":"https:\/\/adriangrigoras.com\/blog\/wp-json\/wp\/v2\/media?parent=549"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/adriangrigoras.com\/blog\/wp-json\/wp\/v2\/categories?post=549"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/adriangrigoras.com\/blog\/wp-json\/wp\/v2\/tags?post=549"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"DevOps1\"](\"http:\/\/nirmata.com\/wp-content\/uploads\/2015\/02\/DevOps1.png\")
<\/a><\/strong><\/strong><\/p>\nWhat should developers operate?<\/b><\/h2>\n
Who provides the automation?<\/b><\/h2>\n
![\"DevOps2\"](\"http:\/\/nirmata.com\/wp-content\/uploads\/2015\/02\/DevOps2.png\")
<\/strong><\/strong><\/p>\nHow is the automation performed?<\/b><\/h2>\n
\n
Summary<\/b><\/h2>\n
\n@JimBugwadia<\/a>
\nFounder and CEO at\u00a0nirmata.io<\/a><\/p>\nReferences<\/b><\/h2>\n