What Is Configuration Management in Devops

Post oleh : Digital Chandu | Rilis : 8:58 AM | Series :

The basic point of Configuration Management in DevOps is to provide,

Infrastructure as a Code

Configuration as Code

In DevOps practice there are many advantages of "Infrastructure as Icon" and "Configuration as Icon".

• Configurations are controlled in version.
• Automatic and uniform
• Removes dependency
• Error adjusting settings
• Enhances collaboration between operations and development team
• Drift reform repair
• Consider infrastructure as a flexible resource
• Automatic scaling of the infrastructure
• Maintain consistency in settings

In this section, we'll learn about Configuration Manager, Version Manager, and request Performance Monitoring in DevOps.

Here, in Box 1, we will focus on Configuration Management and understand what configuration management is and how DevOps differ in traditional methods.

First, let's know what configuration management is?

Configuration management, as the name explains itself, is more than managing all the configurations of the environments in which the application is implemented.

As we know, there are different environments within SDLC in DevOps, ranging from unit testing, integration testing, system testing, receiving testing, and end user testing.

As I explained in previous lessons that the environment created for these tests will become more complex gradually as we move towards the environment of production and production.

Thus, CMM, in essence, is a process for managing all configurations of each of these environments.

Then what is the difference between conventional configuration management and DevOps configuration management?

In traditional configuration management methods, the team used different environments to manage these configurations using official documents, where each configuration was used to write to the documents, and the configuration manager or team used to manage the versions of those documents.

When it changes, it also takes responsibility for preparing the environment and managing the configuration manually.

Now in DevOps, as a general rule, all of these configuration management processes are fairly automated, and the configurations are packaged as code or scripts and managed using the version control tool.

In this context, we can call a process integration group with developers in managing environments using a control tool in a single version.

DevOps Online Training

facebook

twitter

Tweet

google+

linkedin