Configuration management

See also DevOps, Software Configuration Canagement (SCM)

Snippet from Wikipedia: Configuration management

Configuration management (CM) is 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. The CM process is widely used by military engineering organizations to manage changes throughout the system lifecycle of complex systems, such as weapon systems, military vehicles, and information systems. Outside the military, the CM process is also used with IT service management as defined by ITIL, and with other domain models in the civil engineering and other industrial engineering segments such as roads, bridges, canals, dams, and buildings.

Snippet from Wikipedia: Software configuration management

In software engineering, software configuration management (SCM or S/W CM; also expanded as source configuration management process and software change and configuration management) is the task of tracking and controlling changes in the software, part of the larger cross-disciplinary field of configuration management. SCM practices include revision control and the establishment of baselines. If something goes wrong, SCM can determine the "what, when, why and who" of the change. If a configuration is working well, SCM can determine how to replicate it across many hosts.



  • Ansible
  • BladeLogic
  • CFEngine
  • Chef
  • Chef Delivery
  • Cobbler
  • Congruit
  • Consul
  • Foreman
  • Micro Focus
  • Packer
  • PalletOps
  • Puppet
  • RackHD
  • Rudder
  • SSH
  • Salt
  • Terraform
  • Vagrant
  • method/configuration_management.txt
  • Last modified: 2022/08/16 10:43
  • by Henrik Yllemo