Continuous configuration automation: Difference between revisions

Revision as of 21:14, 28 October 2016

Revision as of 21:18, 28 October 2016

Line 1:

'''Continuous Configurationconfiguration Automationautomation''' ('''CCA''') is the methodology or process of automating the deployment and configuration of settings and software for infrastructure both physical and virtual.<ref name="CCA" >{{cite report

|last= Fletcher | first= Colin | last2= Cosgrove | first2=Terrence

|title=Innovation Insight for Continuous Configuration Automation Tools

Line 8:

==Overview==

Continuous Configurationconfiguration Automationautomation solvesis challengesmarketed relatedfor to[[data infrastructurecenter]] and application [[configuration management]]. CCA tools address these challenges through a systematic programmable framework which allows for ease of configuration and Orchestrationorchestration though coding, planning, and incrementally adopting industry best practices.<ref>{{cite web| url= http://info.easydynamics.com/blog/continuous-integration-infrastructure-as-code |title= Continuous Integration: Infrastructure as Code in DevOps | last= Ramos | first= Martin | website= easydynamics.com | date= 4 November 2015}}</ref>

<ref>{{cite report |title=Infrastructure As Code: Fueling the Fire for Faster Application Delivery |publisher=Forrester |date=March 2015}}</ref>

==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.<ref name="CCA" /> Gartner describes CCA as “Embodying [[Lean software development|lean]], [[agile software development | 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.”

<ref >{{cite web

| url=http://devops.com/2015/05/14/moving-from-infrastructure-automation-to-true-devops/

Line 21:

}}</ref>

==CCA toolsTools==

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 [[Infrastructureinfrastructure as Codecode]] (IaC) 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

Line 33:

==Evaluation factors==

AsEvaluations enterprises are moving towards implementingof CCA tools, evaluations of various tools occur and may consider the following:<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 44:

*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==