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]
Overview
Continuous configuration automation is marketed for data center and application configuration management. CCA tools address these challenges through a 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 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 traditional infrastructure as code (IaC) 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
Evaluations of CCA tools 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
References
- 1 2 3 Fletcher, Colin; Cosgrove, Terrence (26 August 2015). Innovation Insight for Continuous Configuration Automation Tools. Gartner (Report).
- ↑ Ramos, Martin (4 November 2015). "Continuous Integration: Infrastructure as Code in DevOps". easydynamics.com.
- ↑ Infrastructure As Code: Fueling the Fire for Faster Application Delivery (Report). Forrester. March 2015.
- ↑ Phillips, Andrew (14 May 2015). "Moving from Infrastructure Automation to True DevOps". DevOps.com.
- ↑ Venezia, Paul (21 November 2013). "Puppet vs. Chef vs. Ansible vs. Salt". networkworld.com. Network World. Retrieved 14 December 2015.
- ↑ Garner Market Trends: DevOps – Not a Market, but Tool-Centric Philosophy That supports a Continuous Delivery Value Chain (Report). Gartner. 18 February 2015.
- ↑ Fletcher, Colin; Cosgrove, Terrence (25 March 2016). How I&O teams can combine CCA tools With Containers to Achieve Operational Efficiecies. Gartner (Report).