Chapter 9. Infrastructure as Conversation
Much of the evolution of ChatOps started with software engineers managing source code from the comfort of their chat clients. As outlined in Chapter 5, these are still some of the most common use cases. Originally dubbed “conversation-driven development” at GitHub, ChatOps has evolved well beyond the ability to keep teams up-to-date on information regarding source control repositories. A broad range of teams now manage a large and growing list of services and actions related to IT operations and more.
If you are at all familiar with the principles and disciplines that have evolved from DevOps, you’ve likely heard the phrase “Infrastructure as Code” (IaC). The term refers to the practice of engineers provisioning and managing infrastructure through the use of definition files written in languages such as Ruby, Python, Java, and others. With the widespread adoption of cloud computing and remote data center usage, more and more teams and organizations are turning to IaC for managing these processes.
Traditional “Ops” teams are now engineering scripts written in programming languages that have historically only been used by software engineers. Configuration management services such as Chef, Puppet, Ansible, and SaltStack allow provisioning and management of infrastructure through scripts, triggers, and event actions.
As teams begin to adopt DevOps principles and share more of the roles and responsibilities, sharing becomes one of the key points ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access