Continuous configuration automation: Difference between revisions

Revision as of 18:48, 8 March 2017

Revision as of 18:21, 30 March 2017

Line 1:

'''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 [[data center]] equipment.<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 configuration automation is marketed for [[data center]] and application [[configuration management]]. CCA tools address these challenges throughuse a programmable framework which allows for ease of configuration and orchestration through coding, planning, and incrementally adopting industry best practicespolicies.<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>

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

==Relationship to DevOps==

CCA tooltools are includedused infor thiswhat realmis ofcalled [[DevOps]] tooling, and are often included as part of a [[DevOps toolchain]]. CCA grew out of a push to develop more reliable software faster.<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 22 ⟶ 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 traditional [[infrastructure as code]] (IaC) frameworks, CCA tools leverage IaC to “Change configure and automate infrastructure".<ref name="CCA" /> There are a few different CCA tools includinginclude [[Ansible (software)|Ansible]], [[Chef software]], [[Otter (software)|Otter]], [[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 44 ⟶ 43:

| date=8 December 2016

}}</ref>

*Skills, training, and cost required to implement and maintain tool

Line 51 ⟶ 49:

*Method of interacting with managing system

*Support and training availability and cost

*Incorporation of orchestration with [[Configurationconfiguration Managementmanagement]]

*Security and compliance reporting