Devops Tools and Configuration Management

Mauricio SilvaBlog1 Comment

DevOps culture requires increased communication between teams of development, quality and operation. It also requires a centralized environment for the operation of DevOps practices automation cycle tools.

Introduction

Have you ever figured out how to manage thousands of machines or nodes on an enterprise infrastructure? And if you need to upgrade a software, will it go into each node? If so, you’re doing it the wrong way.

Items such as startup, connection strings, paths, keys, and other associated variables are typical examples of configuration items.

To make work easier and to leave everything safer and with less manual intervention, the use of DevOps tools are highly recommended.

Tools for increasing communication and activity orchestration

The DevOps culture requires increased communication between teams of development, quality and operation. It also requires a centralized environment for the operation of DevOps practices automation cycle tools. And to support these practices there are specific DevOps tools for increasing collaboration between teams.

Source Code Analysis Tools

The DevOps culture requires developers to write quality code. In recent years, it has been possible to quantify what code quality is in a practical way. Often vague terms such as cyclomatic complexity, modularity, high cohesion, and weak coupling have become actionable metrics in simple tools like Visual Studio Code Review and SonarQube.

Source Code Management Tools

It is impossible to work with the DevOps culture without properly managing the source code. And here we are talking about tools like Microsoft TFS (Team Foundation Server), Mercurial or Git.

Git, which was popularized from the experience of the Linux community in keeping distributed development of its kernel.

Build Automation Tools

These tools are at the heart of build management practice and are typically technology-specific. The Java EE community uses tools such as Ant and Maven and most recently started adopting Gradle for its build processes. The Microsoft community uses Visual Studio , Microsoft Team Services. The Javascript community regularly uses tools such as Grunt and Gulp.

Gains we can have with these tools

  • If someone enters a server and makes an improper change, the configuration manager will automatically make the correction and can generate a report of the fact.
  • If any service that should have been active and was inactive, the configuration manager will automatically upload this service, without the need to trigger it.
  • Installation of any service or tool (jboss, glassfish, jenkins, etc) will be done through configuration management and description of the group of nodes that should have that standard, avoiding installation and manual maintenance.
  • Greater control of the machine park (physical or VM’s) with service SLA and low recovery.
  • It results in high-performance teams making more frequent implementations and delivering projects on shorter deadlines.
  • Lets you make changes with fewer errors and fix crashes faster.

 

One Comment on “Devops Tools and Configuration Management”

  1. the source code management techniques were really good and i loved the way of your reports . thank you for posting this

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.