Facilitating the spread of knowledge and innovation in professional software development



Choose your language

InfoQ Homepage Configuration Management Content on InfoQ

  • CFEngine's Decentralized Approach to Configuration Management

    Mark Burgess and Diego Zamboni introduce CFEngine. They describe the challenges regarding web scale - scale, complexity and knowledge - and how CFEngine helps to tackle those challenges with a fundamentally decentralized and knowledge-oriented approach. An example demonstrates how those ideas translate into practice.

  • The Top Automation Tools for Public Cloud at Scale

    As more organizations expand their use of public cloud services, from early-stage startups to the biggest businesses and governments in the world, the problems of cloud computing at scale start to arise.

  • Purely Functional Configuration Management with Nix and NixOS

    This article gives a short introduction to NixOS, a Linux distribution, and to Nix, the package manager on which NixOS is based. These provide a declarative approach to configuration management with many advantages to users, such as strong reproducibility and atomic upgrades and rollbacks.

  • Ansible’s View on IT Automation

    Michael DeHaan, creator of Ansible, introduces the general-purpose IT automation system. He describes the tool’s guiding principles: simplicity, ease of use and maximum security. The philosophy behind its community is also discussed, including the importance of Ansible’s plugin-based model. Michael uses a simple but common scenario to demonstrate Ansible.

  • Exploring the ENTIRE DevOps Toolchain for (Cloud) Teams

    When assessing technology that empowers a DevOps transformation, it’s easy to focus in on the headline capabilities (“configuration management!”) and miss out on the bigger picture. How can teams shipping cloud (or on-premises) applications use the full suite of DevOps technologies to simplify delivery and management at scale? This article classifies and explains key enabling technologies.

  • DevOps @ large investment bank

    This article is part of the “DevOps War Stories” series. In each issue we hear what DevOps brings to a different organisation, we learn what worked and what didn’t, and chart the challenges faced during adoption. This time a very personal story on introducing a DevOps mindset at a large bank. In particular how the automation of configuration and release management processes enabled collaboration.

  • Book Review: Vagrant up and running

    Mitchell Hashimoto released his book "Vagrant up and running" which covers everything from basic Vagrant usage to extending its functionality. In seven chapters he explains every aspect of Vagrant - from staring a default VM to extending it via plug-ins.

  • Managing Build Jobs for Continuous Delivery

    The number of jobs in a continuous integration tool can range from a few to several thousand, all performing various functions. There is an approach to manage these jobs in a more efficient manner.

  • 5 Configuration Management Best Practices

    There has been a lot of conversation going on around the configuration of applications, and how to manage it. This article explores things people can do from within their code to make their lives, and the lives of anyone else who has to administer or maintain their application, easier. These patterns have been used a number of times on ThoughtWorks projects, and they have proven their worth.

  • Improving the Performance of Automatic Configuration Management Processes by Encouraging Human Intervention

    In this case study, the pattern of automatic processes interlaced with human intervention provided bwin with an instrument to raise process efficiency in CM drastically. Furthermore, successes of the incorporation of human factors into change management was an increased visibility and appreciation of the context and importance of change amongst team members and stakeholders across the company.

  • Version Control for Multiple Agile Teams

    When several agile development teams work on the same codebase, how do we minimize chaos, and ensure there's a clean, releasable version at the end of every iteration? Here Henrik Kniberg outlines the scheme used in "Scrum and XP from the Trenches". This paper is not so much for version control experts as for the rest of us, who just want to learn simple and useful ways to collaborate.