Configuration Management - diagram

Tutorial: Configuration Management – Vagrant + Ansible + Jenkins

20 August, 2015

Main target: Jenkins CI automatically installed in multiple environments.

Video tutorial on managing automatic configuration on local and remote environments with Ansible.

What is configuration management?

Configuration management (CM) refers to a discipline for evaluating, coordinating, approving or disapproving, and implementing changes in artifacts that are used to construct and maintain software systems. An artifact may be a piece of hardware or software or documentation. CM enables the management of artifacts from the initial concept through design, implementation, testing, baselining, building, release, and maintenance.

What benefits gives us configuration management?

  • Reduce manual repetitive processes.
  • Create a software version known, reliable, proven and repeatable.
  • Achieve greater confidence in the project team.
  • Increase in quality; processes, products and team.
  • Increased responsiveness and innovation

Tutorial: Requirements

Complete list of software used:

This is the architecture that I follow:

Configuration Management - Arquitectura

The entire contents of the tutorial include:

Tutorial: Step by step

1. Architecture

(CM01b-intro-arquitectura)

2. Used software

(CM01c-intro-software)

3. Configuring Vagrant via the Vagrantfile

(CM02-vagrant-init)

4. Creation of an Ansible Playbook for the Jenkins CI installation process

(CM03-ansible-playbook)

5. Refactoring the Ansible Playbook to use Roles structure

(CM04-ansible-refactor-roles)

6. Port forwarding with Nginx

(CM05-nginx-jenkins-automatico)

7. Refactor the Ansible Playbook to accept Ubuntu 12

(CM06-refactoring-jdk7)

8. Jenkins CI automatically installed into Amazon AWS Linux OS

(CM07-aws-jenkins-automatico)

9. Share versioned code on Github

(CM08-git_push-github)

    Tags: , , , , , , , , , ,

    Leave a Comment