Infrastructure as code: Difference between revisions

Revision as of 11:55, 30 January 2016

Revision as of 11:59, 30 January 2016

Line 62:

====Community content====

An important aspect when considering CCA tools is the community content. 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/> Vendors like [[Puppet (software)|Puppet]] and [[Chef (software)|Chef]], those that have been around a significant amount of time, 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?
| last= Sturgeon |first= Phil
| date= 28 October 2012
}}</ref> other vendors rely on adjacent communities and leverage other IaC frameworks such as [[PowerShell]] DSC.<ref name=powershell/> As the field continues to develop and change, the community based content will become ever important to how IaC tools are utilized.

Notable CCA tools include:

{| class="wikitable"

! Tool Name !! Released by !! Method !! Approach

! Released by

!Method

!Approach

|-

|! [[Ansible (software)|Ansible Tower]]

| [[Ansible (software)]]

|Push

|Declarative & Imperative

|-

|! [[CFEngine]]

| CFEngine

| Pull

| Declarative

|-

|! [[Chef (software)|Chef]]

| Chef

| [[Chef (software)]]

|Pull

| Imperative

|-

|![[Otter (software)|Otter]]

|Inedo

|Push

|Declarative & Imperative

|-

|! [[Puppet (software)|Puppet]]

| Puppet

| [[Puppet (software)]]

|Pull

|Declarative

|-

|! [[SaltStack]]

| SaltStack

|Push

|Declarative & Imperative

|}