Difference between revisions of "Configuration management"
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
* 2010 [[Ansible]] | * 2010 [[Ansible]] | ||
* 2009 [[Chef]] | * 2009 [[Chef]] | ||
| + | * 2005 [[Capistrano]] | ||
* 2005 [[Puppet]] | * 2005 [[Puppet]] | ||
Revision as of 13:04, 3 May 2020
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
- 2010 Ansible
- 2009 Chef
- 2005 Capistrano
- 2005 Puppet
Activities
- Review different Configuration management alternatives and help to complete this article
See also
- Ansible
- Configuration management: Chef, cdist, capistrano, Ansible, puppet, SaltStack
- Monitoring: On call, Monitoring software, Monitoring services, Resource monitoring, Metric colletion tools, network monitoring, SLA Management Monitoring Tools, Alarm/Alert, Resource starvation, Alerts and notifications, Monitoring Kubernetes, VictoriaMetrics, Sensu, LogicMonitor, Distributed tracing, Datadog Monitors
- 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:
