Difference between revisions of "Configuration management"
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
== Configuration Management Timeline == | == Configuration Management Timeline == | ||
| − | * 2012 [[Ansible]] push | + | * 2012 [[Ansible]] (push) |
| − | * 2011 [[Saltstack]] push | + | * 2011 [[Saltstack]] (push) |
* 2009 [[Chef]] pull | * 2009 [[Chef]] pull | ||
* 2005 [[Capistrano]] | * 2005 [[Capistrano]] | ||
Revision as of 11:46, 27 May 2022
wikipedia:Configuration management (CM) can be defined a systems engineering process for establishing and maintaining consistency of a product's performance, functional, and physical attributes with its requirements, design, and operational information throughout its life. Different tools can help to manage configuration managemnt, such as Ansible or puppet.
Configuration Management Timeline
- 2012 Ansible (push)
- 2011 Saltstack (push)
- 2009 Chef pull
- 2005 Capistrano
- 2005 Puppet pull
Activities
- Review different Configuration management alternatives and help to complete this article
- Review wikipedia:Comparison of open-source configuration management software
Related terms
See also
- Configuration management: Chef, cdist, capistrano, Ansible, puppet, SaltStack
- IaC: Terraform, Chef, cdist, capistrano, Harrow, puppet, Ansible, CFEngine, Cloud Deployment Manager, pulumi, juju, SaltStack, Azure Resource Manager (ARM), Google Deployment Manager, AWS CloudFormation, Pulumi, Heat, Spacelift, Oracle Cloud Resource Manager, KICS, Troposphere, CaC, IaC scanning
- wikipedia:Configuration Management (ITSM)
Advertising:
