Continuous configuration automation explained

Continuous configuration automation (CCA) is the methodology or process of automating the deployment and configuration of settings and software for both physical and virtual data center equipment.^[1]

Overview

Continuous configuration automation is marketed for data center and application configuration management. CCA tools use a programmable framework for configuration and orchestration through coding, planning, and incrementally adopting policies.^[2] ^[3]

Relationship to DevOps

CCA tools are used for what is called DevOps, and are often included as part of a DevOps toolchain. CCA grew out of a push to develop more reliable software faster.^[1] Gartner describes CCA as “Embodying lean, agile and collaborative concepts core to DevOps initiatives, CCA tools bring a newly found level of precision, efficiency and flexibility to the challenges of infrastructure and application configuration management.”^[4]

Tools

CCA tools support administrators and developers to automate the configuration and Orchestration of physical and virtual infrastructure in a systematic way that give visibility to state of infrastructure within an enterprise. Generally thought of as an extension of infrastructure as code (IaC) frameworks.^[1] CCA tools include Ansible, Chef software, Otter, Puppet (software), Rudder (software) and SaltStack.^[5] Each tool has a different method of interacting with the system some are agent-based, push or pull, through an interactive UI. Similar to adopting any DevOps tools, there are barriers to bring on CCA tools and factors that hinder and accelerate adoption.^[6]

Notable CCA tools include:

Tool	Developed by	Method	Approach	Written in
Ansible	Red Hat	Push	Declarative and imperative	Python
CFEngine	Northern.tech	Pull	Declarative	C^[7]
Chef	Progress	Pull	Imperative	Ruby
Otter	Inedo	Push	Declarative and imperative	-
Puppet	Puppet	Pull	Declarative	C++, Clojure since 4.0, Ruby
Salt	VMware	Push and Pull	Declarative and imperative	Python
Terraform	HashiCorp	Push	Declarative	Go

Evaluation factors

Evaluations of CCA tools may consider the following:^[8] ^[9]

Skills, training, and cost required to implement and maintain tool
Content and support of the Platform and Infrastructure – tool specified for Windows or Linux etc.
Delivery method and likening flexibility – important for scalability
Method of interacting with managing system
Support and training availability and cost
Incorporation of orchestration with configuration management
Security and compliance reporting

Notes and References

Fletcher . Colin . Cosgrove . Terrence . Innovation Insight for Continuous Configuration Automation Tools . Gartner . 26 August 2015.
Web site: Continuous Integration: Infrastructure as Code in DevOps . Ramos . Martin . easydynamics.com . 4 November 2015 . 11 May 2016 . 6 February 2016 . https://web.archive.org/web/20160206165308/http://info.easydynamics.com/blog/continuous-integration-infrastructure-as-code . dead .
Infrastructure As Code: Fueling the Fire for Faster Application Delivery . Forrester . March 2015.
Web site: Moving from Infrastructure Automation to True DevOps . Phillips . Andrew . DevOps.com . 14 May 2015.
Web site: Puppet vs. Chef vs. Ansible vs. Salt . Venezia . Paul . 21 November 2013 . . Network World . 14 December 2015 . 18 July 2018 . https://web.archive.org/web/20180718030604/https://www.networkworld.com/article/2172097/virtualization/puppet-vs--chef-vs--ansible-vs--salt.html . dead .
Garner Market Trends: DevOps – Not a Market, but Tool-Centric Philosophy That supports a Continuous Delivery Value Chain . . 18 February 2015.
Web site: CFEngine 3.18.0 Documentation - What is CFEngine?.
Fletcher . Colin . Cosgrove . Terrence . How I&O teams can combine CCA tools With Containers to Achieve Operational Efficiecies . Gartner . 25 March 2016.
Fletcher . Colin . Cosgrove . Terrence . Market Guide for Continuous Configuration Automation Tools . Gartner . 8 December 2016.