Continuous configuration automation: Difference between revisions

Content deleted Content added
Kharnagy (talk | contribs)
Created page with ''''Continuous Configuration Automation''' ('''CCA''') – Is the methodology or process of automating the deployment and configuration of settings and software f...'
 
SA - IaC
Line 18:
| date= 14 May 2015
}}</ref>
 
==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".<ref name="CCA" /> There are a few different CCA tools including [[Ansible (software)]], [[Chef software]], [[Otter (software)]], [[Puppet 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 | publisher= Network World | access-date=14 December 2015
}}</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]]
|date=18 February 2015
}}</ref>
 
==Evaluation Factorsfactors==
As enterprises are moving towards implementing CCA tools, evaluations of various tools occur and may consider the following:<ref>{{cite report
<ref>{{cite report
|last= Fletcher | first= Colin | last2= Cosgrove | first2=Terrence
|title=How I&O teams can combine CCA tools With Containers to Achieve Operational Efficiecies
Line 28 ⟶ 37:
| date=25 March 2016
}}</ref>
 
*Skills and training required to implement and maintain tool
*Content and support of the Platform and Infrastructure – tool specified for Windows or Linux etc.
Line 34 ⟶ 42:
*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==
{{Reflist|30em}}
 
[[Category:Agile software development]]
[[Category:Software development process]]