Continuous configuration automation: Difference between revisions

Revision as of 13:07, 21 September 2023

Revision as of 19:55, 26 April 2024

Line 21:

==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.<ref name="CCA" /> CCA tools include [[Ansible (software)|Ansible]], [[Chef software]], [[Otter (software)|Otter]], [[Puppet (software)]], [[Rudder (software)]] and [[SaltStack]].<ref >{{cite web | url= http://www.networkworld.com/article/2172097/virtualization/puppet-vs--chef-vs--ansible-vs--salt.html | title= Puppet vs. Chef vs. Ansible vs. Salt | last= Venezia | first= Paul | date= 21 November 2013 | website= networkworld.com[[Network World]] | publisher= Network World | access-date= 14 December 2015 | archive-date= 18 July 2018 | archive-url= https://web.archive.org/web/20180718030604/https://www.networkworld.com/article/2172097/virtualization/puppet-vs--chef-vs--ansible-vs--salt.html | url-status= dead }}</ref> 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.<ref >{{cite report

|title=Garner Market Trends: DevOps – Not a Market, but Tool-Centric Philosophy That supports a Continuous Delivery Value Chain

|publisher=[[Gartner]]