Infrastructure as code: Difference between revisions

Content deleted Content added
Peratae (talk | contribs)
m Improved grammar
m Remove extra spaces, rephrase sentence to be more specific
Line 10:
 
==Overview==
IaC grew as a response to the difficulty posed by [[utility computing]] and second-generation web frameworks. In 2006, the launch of [[Amazon Web Services]]’ [[Elastic Compute Cloud]] and the 1.0 version of [[Ruby on Rails]] just months before<ref >{{cite journal
| last1=Bower |first1=Joseph L.
| last2= Christensen | first2= Clayton M.
Line 66:
====Community content====
{{see also|List of systems management systems|Comparison of open-source configuration management software}}
AnCommunity importantcontent aspectis whena consideringkey CCAdeterminant tools,of ifthe theyquality areof an open source, isCCA the community contenttool. As [[Gartner]] states, the value of CCA tools is "as dependent on user-community-contributed content and support as it is on the commercial maturity and performance of the automation tooling".<ref name=CCA/> Established vendors such as [[Puppet (software)|Puppet]] and [[Chef (software)|Chef]] have created their own communities. Chef has [[Chef Community Repository]] and Puppet has [[PuppetForge]].<ref >{{cite web
|url=https://philsturgeon.uk/devops/2012/10/28/puppet-or-chef/
|title=Puppet or Chef?
Line 130:
 
==Relationship to DevOps==
IaC can be a key attribute of enabling best practices in [[DevOps]]. Developers become more involved in defining configuration and Ops teams get involved earlier in the development process.<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 | access-date= 29 January 2016 | archive-url= https://web.archive.org/web/20160206165308/http://info.easydynamics.com/blog/continuous-integration-infrastructure-as-code | archive-date= 6 February 2016 | url-status= dead }}</ref> Tools that utilize IaC bring visibility to the state and configuration of servers and ultimately provide the visibility to users within the enterprise, aiming to bring teams together to maximize their efforts.<ref>{{cite report |title=Infrastructure As Code: Fueling the Fire for Faster Application Delivery |publisher=Forrester |date=March 2015}}</ref> Automation in general aims to take the confusion and error-prone aspect of manual processes and make it more efficient, and productive. Allowing for better software and applications to be created with flexibility, less downtime, and an overall cost-effective way for the company. IaC is intended to reduce the complexity that kills efficiency out of manual configuration. Automation and collaboration are considered central points in DevOps; infrastructure automation tools are often included as components of a [[DevOps toolchain]].<ref>{{cite report | last1= Wurster | first1= Laurie F. |last2= Colville | first2= Ronni J. |last3= Height| first3= Cameron | last4= Tripathi | first4= Somendra | last5= Rastogi | first5= Aditi | title= Emerging Technology Analysis: DevOps a Culture Shift, Not a Technology| publisher= Gartner }}</ref>
 
== Relationship to security ==