Content deleted Content added
m Removing link(s) Wikipedia:Articles for deletion/Otter (software) closed as delete (XFDcloser) |
|||
(253 intermediate revisions by more than 100 users not shown) | |||
Line 1:
{{Short description|Data center management method}}
{{multiple issues|
{{Advert|date=March 2018}}
{{Technical|date=November 2021}}
}}
'''Infrastructure as code''' ('''IaC''') is the process of managing and provisioning computer [[data center]] [[Resource|resources]] through machine-readable definition files, rather than physical [[Computer hardware|hardware]] configuration or interactive configuration tools.<ref name="AWS in Action, IaC" />
The [[IT infrastructure]] managed by this process comprises both physical equipment, such as [[bare-metal server]]s, as well as [[virtual machine]]s, and associated configuration resources.
The definitions may be in a [[Version Control System|version control system]], rather than maintaining the code through manual processes.
The code in the definition files may use either scripts or declarative definitions, but IaC more often employs [[declarative programming|declarative]] approaches.
==Overview==
IaC grew as a response to the difficulty posed
| last1=Bower |first1=Joseph L.
| last2= Christensen | first2= Clayton M.
| title= Disruptive Technologies: Catching the Wave
| journal= [[Harvard Business Review]]
}}</ref> created widespread scaling difficulties in the enterprise that were previously experienced only at large, multi-national companies.<ref name="CCA" >{{cite report
|last1= Fletcher | first1= Colin | last2= Cosgrove | first2=Terrence
|title=Innovation Insight for Continuous Configuration Automation Tools
|website=Gartner
|url=http://www.gartner.com/document/3119319?ref=unauthreader
| date=26 August 2015
}}{{dead link|date=December 2021|bot=medic}}{{cbignore|bot=medic}}</ref> With new tools emerging to handle this ever-growing field, the idea of IaC was born. The thought of modeling infrastructure with code, and then having the ability to design, implement, and deploy application infrastructure with known software best practices appealed to both software developers and IT infrastructure administrators. The ability to treat infrastructure as code and use the same tools as any other software project would allow developers to rapidly deploy applications.<ref >{{cite journal
| last=
| title= Version Your Infrastructure
| url=
|
}}</ref>
==Advantages==
The value of IaC can be broken down into three measurable categories: cost, speed, and risk.{{cn|date=September 2019}} Cost reduction aims at helping not only the enterprise financially, but also in terms of people and effort, meaning that by removing the manual component, people are able to refocus their efforts on other enterprise tasks.{{citation needed|date=March 2017}} Infrastructure automation enables speed through faster execution when configuring your infrastructure and aims at providing visibility to help other teams across the enterprise work quickly and more efficiently. Automation removes the risk associated with human error, like manual misconfiguration; removing this can decrease downtime and increase reliability. These outcomes and attributes help the enterprise move towards implementing a culture of [[DevOps]], the combined working of [[Software development|development]] and [[Information technology operations|operations]].<ref >{{cite web
| url=http://devops.com/2015/05/14/moving-from-infrastructure-automation-to-true-devops/
| title= Moving from Infrastructure Automation to True DevOps
Line 37:
}}</ref>
==Types of approaches ==
There are generally
| url= https://www.scriptrock.com/blog/articles/declarative-vs.-imperative-models-for-configuration-management
| title= Declarative v. Imperative Models for Configuration Management: Which Is Really Better?
| website= Scriptrock.com
| access-date= 14 December 2015
| archive-date= 31 March 2015
| archive-url= https://web.archive.org/web/20150331062438/https://www.scriptrock.com/blog/articles/declarative-vs.-imperative-models-for-configuration-management
| url-status= dead
}}</ref> The declarative approach defines the desired state and the system executes what needs to happen to achieve that desired state. Imperative defines specific commands that need to be executed in the appropriate order to end with the desired conclusion.<ref >{{cite magazine
|last= Loschwitz | first= Martin
| date= 14 November 2014
| title= Choosing between the leading open source configuration managers
| url=http://www.admin-magazine.com/Archive/2014/23/Choosing-between-the-leading-open-source-configuration-managers
| magazine= Admin Network & Security
| ___location= Lawrence, KS USA | publisher= Linux New Media USA LLC
}}</ref>
==Methods==
Infrastructure as Code (IaC) allows you to manage servers and their configurations using code. There are two
==Tools==
There are many tools that fulfill infrastructure automation capabilities and
===Continuous
All [[
====Community content====
{{see also|List of systems management systems|Comparison of open-source configuration management software}}
Community content is a key determinant of the quality of an open source CCA tool. 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?
|
|first= |
|access-date=29 January 2016
|archive-date=1 February 2016
|archive-url=https://web.archive.org/web/20160201185444/https://philsturgeon.uk/devops/2012/10/28/puppet-or-chef/
|url-status=dead
}}</ref> Other vendors rely on adjacent communities and leverage other IaC frameworks such as [[PowerShell]] DSC.<ref name=powershell/> New vendors are emerging that are not content-driven, but model-driven with the intelligence in the product to deliver content. These visual, object-oriented systems work well for developers, but they are especially useful to production-oriented DevOps and operations constituents that value models versus scripting for content. As the field continues to develop and change, the community-based content will become ever more important to how IaC tools are used, unless they are model-driven and object-oriented.
Notable CCA tools include:
{| class="wikitable"
! Tool
|-
![[CFEngine]]
|Northern.tech (1993)
|Pull
|Declarative
|[[C (programming language)|C]]
| -
|-
![[Puppet (software)|Puppet]]
|Puppet (2005)
|Push and Pull
|
| [[C++]] & [[Clojure]] since 4.0, [[Ruby (programming language)|Ruby]]
| -
|-
!
|
|Pull
|Declarative and imperative
|[[Ruby (programming language)|Ruby]]
| -
|-
![[SaltStack]]
|SaltStack (2011)
|Push and Pull
|Declarative
|[[Python (programming language)|Python]]
| -
|-
! [[Ansible (software)|Ansible]] / [[Ansible (software)#Ansible Automation Platform|Ansible Tower]]
| [[Red Hat]] (2012)
| Push and Pull
| Declarative and imperative
|[[Python (programming language)|Python]]
| -
|-
! [[
| [[HashiCorp]] (2014)
| Push
| Declarative and imperative
|[[Go (programming language)|Go]]
| -
|-
!Otter
|Inedo (2015)
|Push
|Declarative
| -
| Windows-oriented
|-
![[Pulumi]]
|Pulumi (2018)
|Push
|Declarative and imperative
|[[Go (programming language)|Go]]
| -
|-
! [[
| [[Linux Foundation]] and contributors (2023)
| Push
| Declarative
| [[Go (programming language)|Go]]
| Terraform fork
|}
Other tools include [[AWS CloudFormation]], [[cdist]], [[StackStorm]], [[Juju (software)|Juju]], and Step CI.
==Relationships==
===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 ===
The 2020 Cloud Threat Report released by Unit 42 (the threat intelligence unit of cybersecurity provider [[Palo Alto Networks]]) identified around 200,000 potential vulnerabilities in infrastructure as code templates.<ref>{{Cite web|url=https://www.informationweek.com/cloud/cloud-threat-report-shows-need-for-consistent-devsecops/a/d-id/1337023|title=Cloud Threat Report Shows Need for Consistent DevSecOps|website=InformationWeek|date=13 February 2020|language=en|access-date=2020-02-24}}</ref>
== See also ==
* [[Docker (software)| Docker]]
* [[IT infrastructure]]
* [[Infrastructure as a service]]
* [[Orchestration (computing)|Orchestration]]
* [[Continuous configuration automation]]
* [[Landing zone (software)]]
==References==
{{Reflist
<ref name="AWS in Action, IaC" >{{Cite book
|title=Amazon Web Services in Action
|
|last2=Wittig |first2=Michael
|year=2016
Line 134 ⟶ 178:
}}
{{Use dmy dates|date=June 2017}}
[[Category:Agile software development]]
Line 140 ⟶ 186:
[[Category:Systems engineering]]
[[Category:Orchestration software]]
[[Category:Cloud computing]]
|