Configuration Management
Configuration Management
Originally developed in the US military and now widely used in many different
kinds of systems, CM helps identify systems that need to be patched, updated, or
reconfigured to conform to the desired state
Why is Configuration Management
important?
Configuration Management helps prevent undocumented changes from working their
way into the environment. By doing so, CM can help prevent performance issues,
system inconsistencies, or compliance issues that can lead to regulatory fines and
penalties. Over time, these undocumented changes can lead to system downtime,
instability, or failure.
Performing these tasks manually is too complex in large systems. Software
configuration management can involve hundreds or thousands of components for each
application, and without proper documentation IT organizations could easily lose track
of which systems require attention, what steps are necessary to remediate problems,
what tasks should be prioritized and whether changes have been validated and
propagated throughout the system.
A Configuration management system allows the enterprise to define settings in a
consistent manner, then to build and maintain them according to the established
baselines. A configuration management plan should include a number of tools that:
Enable classification and management of systems in groups
Push changes automatically to all affected systems to automate updates and patching
Once data has been collected the organization can establish a baseline configuration,
which should be a known good configuration that can perform its intended operations
without bugs or errors.
When the baseline has been established, the organization should adopt a version control
system.
What are Benefits of Configuration
Management?
Utilizing a Configuration Management system helps avoid problems that occur when
hardware and software systems are improperly configured.
Simply tracking changes can help avoid expensive remediation projects down the road.
CM is insurance you pay for today so you can prevent issues tomorrow.
For example, Configuration Management helps ensure the development, test, and
production environments are the same, so that deployed applications will behave in the
manner that is expected of them.
What are Risks of not using Configuration Management?
This could impact the bottom line in terms of unplanned downtime, additional expense,
and countless hours wasted remediating errors, quality issues, and missed deadlines due
do downtime.
Root cause analysis, remediation, and maintaining service level agreements (SLAs)
would become increasingly difficult without a CM solution deployed.