Continuous Configuration Automation
Continuous Configuration Automation (CCA) – Is the methodology or process of automating the deployment and configuration of settings and software for infrastructure both physical and virtual [1]
Contents
Overview
Continuous Configuration Automation solves challenges related to infrastructure and application configuration management. CCA tools address these challenges through a systematic programmable framework which allows for ease of configuration and Orchestration though coding, planning, and incrementally adopting industry best practices.[2] [3]
Relationship to DevOps
CCA tool are included in this realm of DevOps tooling and are often included as part of a DevOps toolchain. CCA tools help automate infrastructure which helps achieve some of the key DevOps goals. CCA grew out of a need created by the changing market – with the increase in a push to develop more reliable software faster, infrastructure agility and productivity became a reality.[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]
CCA 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 traditional Infrastructure as Code frameworks, CCA tools leverage IaC to “Change configure and automate infrastructure".[1] There are a few different CCA tools including Ansible (software), Chef software, Otter (software), Puppet 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]
Evaluation factors
As enterprises are moving towards implementing CCA tools, evaluations of various tools occur and may consider the following:[7]
- Skills and training 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
See also
- Infrastructure as Code, the automation of hosting infrastructure, again by describing it through a machine-processable document
References
<templatestyles src="Reflist/styles.css" />
Cite error: Invalid <references>
tag; parameter "group" is allowed only.
<references />
, or <references group="..." />
- ↑ 1.0 1.1 1.2 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.