Taste Test, by Matt Jaynes, is a book that uses a simple scenario to compare Ansible, SaltStack, Chef and Puppet. On the recently released 2nd edition it adds new chapters on Docker, the communities around the tools, and how they fare on security. InfoQ took this opportunity to talk with Matt to know more about his thoughts on the tools and his approach to configuration management when consulting.
Configuration management tools are a hot topic on the DevOps community and IT organizations in general. InfoQ reached out to users of each of the major tools (Ansible, CFEngine, Chef, Puppet and SaltStack) to ask them about their experiences. Why did they choose a given tool? How was the tool introduced in the organization? These are some of the questions they answered.
How should organizations plan for a cloud environment and optimize it for efficiency at scale? InfoQ reached out to 3 leading cloud practitioners to uncover practical advice on this topic. Each panelist has dealt with the sometimes-messy transition from on-premises to cloud, and coached organizations through their journey.
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.
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 will arise.
The article introduces NixOS, a Linux distribution, and Nix, a package manager. These provide a declarative approach to configuration management, such as strong reproducibility and atomic upgrades.
Michael DeHaan, creator of Ansible, introduces the IT automation system, its guiding goals and the philosophy behind its community. Michael uses a simple but common scenario to demonstrate Ansible.
Once the cultural DevOps transformation is under way, how can teams shipping cloud (or on-premises) applications use the full suite of DevOps technologies to simplify delivery and management at scale? 4
This article shows how to do requirement development in agile environments, covering concepts and offering examples of how an agile team could run CMMI for Development targeted at level 3.
InfoQ interviewed Capers Jones about advancements and events in software engineering and the effects that they have had on our society.
In this article we hear 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.
In this article we focus on the practical steps a software delivery professional should take in implementing an end-to-end software delivery process.