Just as DevOps emerged to meet new business needs, new approaches in security are now needed to address the challenges of a DevOps-driven world. These new security approaches themselves must incorporate DevOps practices that rely on modularity, automation, standardization, auditability, and mirrored systems.
In this article we review the book Infrastructure as Code - Managing Servers in the Cloud written by Kief Morris, who is leading Continuous Delivery and DevOps at ThoughtWorks Europe. In over 300 pages, Morris lays down the foundation for Infrastructure as Code and outlines the main patterns and practices recommended for building it.
This article explains the goals of proper application delivery using immutable infrastructure: automated, flexible, scalable, secure and transparent; and how to take gradual steps toward those goals.
As infrastructure becomes code, reviewing (and testing) provides the confidence necessary for refactoring systems. Reviews also help spread consistent best practices throughout the organization.
DevOps is the industrialization of IT, says Nati Shalom. Organizations that wish to optimize for speed and cost cannot afford silos anymore."Doing DevOps" is not adding new features to existing tools.
“Infrastructure as Code” is a tenet of the DevOps community. We’ll make a brief introdution to Chef, a well-known IT automation tool, and use it to illustrate the state of the art.
In this article you will find guidance on how to get started realizing a Continuous Delivery vision, especially in the context of existing development and release environments in large enterprises.