Comparison of open-source configuration management software

From Wikipedia, the free encyclopedia
Jump to: navigation, search

This is a comparison of notable free and open source configuration management software, suitable for tasks like server configuration, orchestration and infrastructure as code typically performed by a system administrator.

Basic properties[edit]

"Verify mode" refers to having an ability to determine whether a node is conformant with a guarantee of not modifying it, and typically involves the exclusive use of an internal language supporting read-only mode for all potentially system-modifying operations. "Mutual auth" refers to the client verifying the server and vice versa. "Agent" describes whether additional software daemons are required. Depending on the management software these agents are usually deployed on the target system or on one or many central "controller" servers.

Language License Mutual auth Encrypts Verify mode Agent-less Have a GUI First release Latest stable release
Ansible Python GPLv3+ Yes[1] Yes[2] Yes Yes Partial[3] (Free 30-day Trial) 2012-03-08 2017-04-12[4][5]
Bcfg2 Python BSD 2-clause[6] Yes[7] Yes[8] Yes[9] No Yes[10] 2004-08-11[11] 2015-06-11 1.3.6[11]
Capistrano Ruby MIT License Yes[2] 2005 2017-03-08 4.4.2
cdist Python GPLv3+ Yes[1] Yes[2] Yes 2010 2015-03-19 3.1.12
Chef Ruby, Erlang Apache 2.0 Yes[12] Yes[13] Yes[14][15] No Yes 2009-01-15 0.5.0 2016-03-07 12.8.1 (client),[16] 2016-02-04 12.4.1 (server)[17]
CFEngine C GPLv3[18] Yes[1] Yes[19] Yes[20][21] No 1993 2017-03-29 3.10.1
ISconf Python GPL[22] Yes[23] No[24] 1998 2006-08-13
Juju Python, Go[25] Affero General Public License Yes[1] Yes[8] No No Yes[26] 2010-09-17[27] 2017-03-16 1.2.1[28]
Local ConFiGuration system (LCFG) Perl GPL Partial[29] Partial[30] 1994 Weekly Releases
NOC Python BSD License 2.0 Yes[1] Yes[2] Yes Yes Yes 2012-03-08 2015-05-20 15.05.1[31]
OCS Inventory NG with GLPI Perl, PHP, C++ GPL No[32] Yes[8] No 2003 2014-07-13[33]
Open pc server integration (Opsi) Python, Java GPL No Yes[8] No 2004 2013-03-01 4.0.3
PIKT C GPLv2+[34] Yes[35] Yes[36] No 1998[37] 2007-09-10 1.19.0
Puppet C++ & Clojure from 4.0[38], Ruby before then Apache from 2.7.0, GPL before then Yes[39] Yes[8] Yes[40][41] No Yes[42] 2005-08-30[43] 2017-05-11 4.10.1[44]
Quattor Perl, Python Apache 2.0[45][46] Yes[47] Yes[48] 2005-04-01[49] 2017-03-03 17.2.0[50]
Radmind C BSD[51] Yes[52] Yes[53] No 2002-03-26[54] 2008-10-08 1.13.0[55]
Rex Perl Apache Yes[1] Yes[2] Yes 2010-11-05 0.9.0[56] 2015-09-04 1.3.3[57]
Rudder C and Scala GPLv3 and Aapche 2.0[58] Yes[1] Yes[8] Yes[59][60] No Yes 2011-10-31 2016-12-20 4.0.2[61]
SmartFrog Java LGPL Yes[62] Yes[62] No 2004-02-11 2009-01-26 3.16.004[63][64]
Salt[65] Python[66] Apache 2.0[67] Yes[68] Yes[68] Yes Both[69][70] Yes[71][72] 2011-03-17 0.6.0[73] 2016-06-08 2016.3.1[74]
Spacewalk Java (C, Perl, Python, PL/SQL) GPLv2 Yes Yes No 2008-06[75] 2016-11-29 2.6[76]
STAF C++ CPL[77] No[78][79] Partial[80] No 1998-02-16[81] 2012-12-16 3.4.16 [82]
Synctool[83] Python[84] GPLv2[85] Yes[86] Yes[2] Yes[87] Yes[88] 2003[89] 2014-06-15 6.1[90]
Language License Mutual auth Encrypts Verify mode Agent-less Have a GUI First release Latest stable release

Platform support[edit]

Note: This means platforms on which a recent version of the tool has actually been used successfully, not platforms where it should theoretically work since it is written in good portable C/C++ or an interpreted language. It should also be listed as a supported platform on the project's web site.

AIX *BSD HP-UX Linux OS X Solaris Windows Others
Ansible Yes Yes Yes Yes Yes Yes Yes (Need linux control machine) Yes[91]
Bcfg2 Partial[92] Yes[93] No Yes[94] Partial[95] Yes No No
CFEngine Yes Yes[93] Yes Yes No Yes Yes Yes[96]
cdist Yes Yes Yes No
Chef Yes[97] Yes Yes Yes Yes Yes Yes[98] Yes
ISconf Yes Yes Yes Yes Yes Yes No No
Juju Yes Yes[99]
Local ConFiGuration system (LCFG) No No No Partial[100] Partial[101] Partial[102] No No
OCS Inventory NG Yes Yes Yes Yes Yes Yes Yes No
Open pc server integration (Opsi) No No No Yes No No Yes No
PIKT Yes Yes Yes Yes Yes Yes No Yes[103]
Puppet Yes Yes Yes Yes Yes Yes Yes Yes
Quattor No No No Yes Partial[104] Yes No No
Radmind Yes Yes[93][105][106] No Yes Yes Yes Yes No
Rex Yes Yes Yes[107] Yes Yes[107] No
Rudder Yes Partial[108] No Yes Partial[108] Partial[109] Yes Yes[110]
SmartFrog No[111] No[111] Yes Yes Yes Yes Yes No[111]
Salt Yes Yes Partial[112] Yes[113] Yes Yes[114] Yes Partial[112]
Spacewalk No[115] No No Yes[116] No Yes[117] No No
STAF Yes[118] Yes[119] Yes[120] Yes[121] Yes[122] Yes[123] Yes[124] Yes[125]
Synctool Yes Yes Yes Yes Yes Yes No Yes[126]
AIX *BSD HP-UX Linux OS X Solaris Windows Others

Short descriptions[edit]

Not all tools have the same goal and the same feature set. To help distinguish between all of these software packages, here is a short description of each one.

Combines multi-node deployment, ad-hoc task execution, and configuration management in one package. Manages nodes over SSH and requires python (2.4 or later) to be installed on them.[127] Modules work over JSON and standard output and can be written in any language. Uses YAML to express reusable descriptions of systems.
Software to manage the configuration of a large number of computers using a central configuration model and the client–server paradigm. The system enables reconciliation between clients' state and the central configuration specification. Detailed reports provide a way to identify unmanaged configuration on hosts. Generators enable code or template based generation of configuration files from a central data repository.
Lightweight agent system. Manages configuration of a large number of computers using the client–server paradigm or stand-alone. Any client state which is different from the policy description is reverted to the desired state. Configuration state is specified via a declarative language.[128] CFEngine's paradigm is convergent "computer immunology".[129]
cdist is a zero dependency configuration management system: It requires only ssh on the target host, which is usually enabled on all Unix-like machines. Only the administration host needs to have Python 3.2 installed.
Chef is a configuration management tool written in Erlang,[130] and uses a pure Ruby DSL for writing configuration "recipes". These recipes contain resources that should be put into the declared state. Chef can be used as a client–server tool, or used in "solo" mode.[131]
Tool to execute commands and replicate files on all nodes. The nodes do not need to be up; the commands will be executed when they boot. The system has no central server so commands can be launched from any node and they will replicate to all nodes.
Juju concentrates on the notion of service, abstracting the notion of machine or server, and defines relations between those services that are automatically updated when two linked services observe a notable modification.
Local Configuration system (LCFG)
LCFG manages the configuration with a central description language in XML, specifying resources, aspects and profiles. Configuration is deployed using the client–server paradigm. Appropriate scripts on clients (called components) transcribe the resources into configuration files and restart services as needed.
Open PC server integration (Opsi)
Opsi is desktop management software for Windows clients based on Linux servers. It provides automatic software deployment (distribution), unattended installation of OS, patch management, hard- and software inventory, license management and software asset management, and administrative tasks for the configuration management.[132]
PIKT is foremost a monitoring system that also does configuration management. "PIKT consists of a sophisticated, feature-rich file preprocessor; an innovative scripting language with unique labor-saving features; a flexible, centrally directed process scheduler; a customizing file installer; a collection of powerful command-line extensions; and other useful tools."
Puppet consists of a custom declarative language to describe system configuration, distributed using the client–server paradigm (using XML-RPC protocol in older versions, with a recent switch to REST), and a library to realize the configuration. The resource abstraction layer enables administrators to describe the configuration in high-level terms, such as users, services and packages. Puppet will then ensure the server's state matches the description. There was brief support in Puppet for using a pure Ruby DSL as an alternative configuration language starting at version 2.6.0. However this feature was deprecated beginning with version 3.1.[128][131][133][134]
The quattor information model is based on the distinction between the desired state and the actual state. The desired state is registered in a fabric-wide configuration database, using a specially designed configuration language called Pan for expressing and validating configurations, composed out of reusable hierarchical building blocks called templates. Configurations are propagated to and cached on the managed nodes.
Radmind manages hosts configuration at the file system level. In a similar way to Tripwire (and other configuration management tools), it can detect external changes to managed configuration, and can optionally reverse the changes. Radmind does not have higher-level configuration element (services, packages) abstraction. A graphical interface is available (only) for OS X.
Rex is a remote execution system with integrated configuration management and software deployment capabilities. The admin provides configuration instructions via so-called Rexfiles. They are written in a small DSL but can also contain arbitrary Perl. It integrates well with an automated build system used in CI environments.
Rudder is an easy to use, web-driven, role-based solution for IT infrastructure Automation & Compliance. A lightweight agent installed on all managed hosts applies configuration and verifies it regularly, centralising reporting data to a main server. Pre-defined modules enable quick and simple configuration for many scenarios, and a web-based interface allows you to build extra modules.
Salt started out as a tool for remote server management. As its usage has grown, it has gained a number of extended features, including a more comprehensive mechanism for host configuration. This is a relatively new feature facilitated through the Salt States component. With the traction that Salt has gotten in the last bit, the support for more features and platforms might continue to grow.
Java-based tool to deploy and configure applications distributed across multiple machines. There is no central server; you can deploy a .SF configuration file to any node and have it distributed to peer nodes according to the distribution information contained inside the deployment descriptor itself.
Spacewalk is an open source Linux and Solaris systems management solution and is the upstream project for the source of Red Hat Network Satellite. Spacewalk works with RHEL, Fedora, and other RHEL derivative distributions like CentOS, Scientific Linux, etc. There are ongoing efforts on getting it packaged for inclusion in Fedora. Spacewalk provides systems inventory (hardware and software information, installation and updates of software, collection and distribution of custom software packages into manageable groups, provision systems, management and deployment of configuration files, system monitoring, virtual guest provisioning, starting/stopping/configuring virtual guests and delegating all of these actions to local or LDAP users and system entitlements).
The Software Testing Automation Framework (STAF) enables users to create cross-platform, distributed software test environments. STAF removes the tedium of building an automation infrastructure, thus enabling users to focus on building their automation solution. The STAF framework provides the foundation upon which to build higher level solutions, and provides a pluggable approach supported across a large variety of platforms and languages.
Synctool aims to be easy to understand, learn and use. It is written in Python and makes use of SSH (passwordless, with host based or key based authentication) and rsync. No specific language is needed to configure Synctool. Synctool has dry run capabilities that enable surgical precision.


  1. ^ a b c d e f g Key pair: uses public/private key pairs and key fingerprints for mutual authentication, like SSH.
  2. ^ a b c d e f Secure Shell: Uses the Secure Shell protocol for encryption.
  3. ^ Ansible, Inc. "Ansible Tower -". 
  4. ^ Ansible Community (November 1, 2016). "Index of Packages - Ansible". Red Hat, Inc. p. 1. Retrieved December 15, 2016. 
  5. ^ Ansible Community (November 1, 2016). "Index of /ansible/ansible-latest". Red Hat, Inc. p. 1. Retrieved December 15, 2016. 
  6. ^ /. "bcfg2/LICENSE at master · Bcfg2/bcfg2 · GitHub". Retrieved 2014-02-10. 
  7. ^ Certificate and Passwords: Uses SSL X.509 certificate and fingerprint for clients to authenticate server, and passwords for server to authenticate clients; clients should only share the same password if they are allowed access to each other's configuration data.
  8. ^ a b c d e f SSL: Uses the Secure Sockets Layer, Transport Layer Security (TLS) for encryption.
  9. ^ Full support for non-modifying determination of node compliance, including nodes not previously modified by a Bcfg2 configuration pass.
  10. ^
  11. ^ a b "Download – Bcfg2". Retrieved 2017-06-04. 
  12. ^ Per request signed headers and pre-shared keys.
  13. ^ Payload encryption via SSL if HTTPS proxy is configured.
  14. ^ Chef 10.14.0+ (called why-run mode)
  15. ^ "[#CHEF-13] Add -noop support - Opscode Open Source Ticket Tracking". Retrieved 2014-02-10. 
  16. ^ "Release Chef Client 12.8.1". 2017-03-10. Retrieved 2017-03-13. 
  17. ^ "Chef Server 12.4.1 Release Announcement". 2016-02-04. Retrieved 2017-03-13. 
  18. ^ "core/LICENSE at master · cfengine/core · GitHub". GitHub. 
  19. ^ Custom: Uses code specific to the software for this function.
  20. ^ Called dry-run, used to verify what would happen
  21. ^ "Quick Reference Guide for CFEngine 3 - CFEngine - Distributed Configuration Management". CFEngine. Retrieved 2014-02-10. 
  22. ^ "/trunk/LICENSE - ISconf - Trac". 1989-04-01. Retrieved 2014-02-10. 
  23. ^ HMAC: Uses HMAC signatures on all network traffic.
  24. ^ Improved security which would include an encrypted, mutually authenticated, peer-to-peer message bus is tracked here [1].
  25. ^ "Juju Source Code". 2015-06-19. Retrieved 2015-06-21. 
  26. ^ "Juju Gui". 2015-06-15. Retrieved 2015-06-21. 
  27. ^ "timeline : pyjuju". Retrieved 2014-02-10. 
  28. ^ "Juju Stable Releases : juju-core". Retrieved 2015-06-21. 
  29. ^ LCFG does not provide its own transport mechanism; it relies on an external program, most often Apache. Using Apache it should be possible to do mutual authentication in several ways; however the documentation at The Complete Guide to LCFG, Section 9.4: Authorization and Security, shows access control based on IP address ranges, implying that the client does not authenticate itself to the server via an SSL certificate; it also does not mention if the LCFG client checks the validity of the server's SSL certificate (such as via a per-site fingerprint distributed with the client, or a chain of trust to an accredited CA). It mentions that there can be a per-client password in the profile, but also states that "The contents of the LCFG profile should be considered public".
  30. ^ LCFG supports encrypted communications channels (SSL via Apache); however the documentation at The Complete Guide to LCFG, Section 9.4: Authorization and Security, states that "The contents of the LCFG profile should be considered public".
  31. ^ "NOC". 
  32. ^ Server authenticates to client, but client does not authenticate to server. See OCS Inventory NG Installation and Administration guide, page 114.
  33. ^ "2.1.2 stable published". OCS Inventory NG. Retrieved 2014-12-16. 
  34. ^ Robert Osterlund (2014-01-04). "PIKT Licensing". Retrieved 2014-02-10. 
  35. ^ PIKT uses shared secret keys for mutual authentication. "As an option, you can use secret key authentication to prove the master's identity to the slave. [...] If one managed to crack any system in the PIKT domain, one would have access to all common secrets. To solve this problem, you may use per-slave uid, gid, and private_key settings." - from Security Considerations.
  36. ^ "For file installs, file fetches (to diff against the central configuration), and command executions, you can optionally encrypt all such data traffic between master and slave." - from Security Considerations.
  37. ^ "Index of /pikt/dist". Retrieved 2014-02-10. 
  38. ^ "Evolving Puppet for the Next 10 Years". Luke Kanies. 2014-09-23. Retrieved 2017-05-26. 
  39. ^ Certificates: Uses SSL X.509 Certificates for mutual authentication. Can use any SSL Certificate Authority to manage the Public Key Infrastructure.
  40. ^ Using the --noop option
  41. ^ "puppet agent Man Page — Documentation — Puppet Labs". Retrieved 2014-02-10. 
  42. ^ "Puppet Management GUI Comparison". 
  43. ^ "Index of /puppet". Retrieved 2014-02-10. 
  44. ^ "Puppet 4.3 Release Notes — Documentation — Puppet Labs". Retrieved 2017-06-04. 
  45. ^ "EU DataGrid Software License (EUDatagrid) | Open Source Initiative". 1999-02-22. Retrieved 2014-02-10. 
  46. ^ "DataGrid Software License (do not change the page URL)". 2004-05-26. Retrieved 2014-02-10. 
  47. ^ "Client to server authentication and vice versa: on one hand, this allows to enforce access policies to sensitive data according to the client "name", on the other hand, clients are guaranteed to talk to the original server." - from Quattor Installation and User Guide: Version 1.1.x, page 70
  48. ^ "[...] secure information transfer, since data are encrypted: this prevents eavesdroppers from obtaining information in transit over the network." - from Quattor Installation and User Guide: Version 1.1.x, page 70
  49. ^ "Index of /quattorsw/software/quattor/release". Retrieved 2014-02-10. 
  50. ^ "Quattor - Quattor 17.2.0 released". 
  51. ^ "Research Systems Unix Group: beepage". Retrieved 2014-02-10. 
  52. ^ "SSL certificates can also be used to authenticate both the Radmind server and the managed clients, regardless of DNS or IP-address variation." - from Radmind: The Integration of Filesystem Integrity Checking with Filesystem Management
  53. ^ "For network security, Radmind supports SSL-encrypted links. This allows nodes on insecure networks to be updated securely." - from Radmind: The Integration of Filesystem Integrity Checking with Filesystem Management
  54. ^ "Radmind - Browse /radmind/radmind-0-6-0 at". 2006-02-10. Retrieved 2014-02-10. 
  55. ^ fitterhappier. "Radmind". 
  56. ^ "Release 0.9.0 · krimdomu/Rex · GitHub". GitHub. 
  57. ^ "Rex/ChangeLog at master · RexOps/Rex · GitHub". GitHub. 
  58. ^ "Rudder FAQ". 
  59. ^ Using the Audit mode
  60. ^ "Policy Mode (Audit/Enforce) - Rudder 4.0 - User Manual". Retrieved 2017-01-17. 
  61. ^ "Rudder 4.0 Release Notes". 
  62. ^ a b See Using the new SmartFrog Security
  63. ^
  64. ^ The release the Smartfrog pushes from its own site is 3.17.014 of 2009-09-04
  65. ^ Salt is an open source tool to manage your infrastructure. Easy enough to get running in minutes and fast enough to manage tens of thousands of servers
  66. ^ "Installation". 
  67. ^ "SaltStack community". SaltStack. 
  68. ^ a b "SaltStack community". SaltStack. 
  69. ^ "Salt SSH". 
  70. ^ "SaltStack Enterprise". SaltStack. 
  71. ^ "saltstack/halite". GitHub. 
  72. ^ "tinyclues/saltpad". GitHub. 
  73. ^ "SaltStack community". SaltStack. 
  74. ^ "Salt 2016.3.1 Release Notes". 
  75. ^ "SpacewalkFaq – spacewalk". 
  76. ^ "ReleaseNotes26 – spacewalk". 
  77. ^ "Software Testing Automation Framework (STAF)". 
  78. ^ Network Trust: Trusts the network, like rsh.
  79. ^ User-only Auth: User authenticates to server via password, but uses Network Trust to authenticate user to server, like telnet.
  80. ^ There is a feature request for a Secure TCP/IP Connection Provider, and one of the developers stated on 2007-04-05 that "You will need to download the source code for OpenSSL and point the build files at it. Other than that, it should just work.", so it looks like there may be working encryption if you build from scratch instead of using the prebuilt binaries. It is unclear what if any authentication building against OpenSSL would give STAF.
  81. ^ "Software Testing Automation Framework (STAF)". 
  82. ^ "Software Testing Automation Framework (STAF)". 
  83. ^ Synctool aims to be easy to understand and use. It's built in Python and uses SSH and Rsync.
  84. ^ "synctool documentation". 
  85. ^ "synctool/LICENSE at master · walterdejong/synctool · GitHub". GitHub. 
  86. ^ Secure Shell: Uses the Secure Shell protocol for authentication.
  87. ^ Synctool performs a dry-run by default, and only modifies things when invoked with '--fix'.
  88. ^ "synctool documentation". 
  89. ^ "synctool documentation". 
  90. ^ "Release v2014.7 · saltstack/salt · GitHub". GitHub. 
  91. ^ Installation: Control Machine Requirements, retrieved May 12, 2015  Can manage any machine with Python 2.4 or later and sshd. Control machine can be any non-Windows machine with Python 2.6 or 2.7 installed. This includes Red Hat, Debian, CentOS, OS X, any of the BSDs, and so on.
  92. ^ Encap, RPM, and POSIX file support only
  93. ^ a b c FreeBSD
  94. ^ Debian, Ubuntu; Gentoo; RPM-based distributions (CentOS, Mandrake, Red Hat, RHEL, SLES, SuSE)
  95. ^ POSIX File, Launchd, and MacPorts Support only
  96. ^ Unix
  97. ^ Opscode and IBM Join Forces to Bring Open Source Cloud Automation to the Enterprise, 2013-04-25 
  98. ^ Install the chef-client on Microsoft Windows, retrieved 2017-03-15 
  99. ^ Windows workloads using juju, retrieved November 25, 2015 
  100. ^ "Recent versions run on Fedora Core (3, 5, 6). Various people have ported some of the LCFG core to other Linux distributions, such as Debian, but these ports have not been incorporated"
  101. ^ "There has been an experimental port to OS X, which does work and includes some Mac-specific components. However, this is not production quality and the lack of uniform packaging system under OS X means that automatic management of installed software is likely to be difficult."
  102. ^ "LCFG core has been ported back to Solaris and we are using this in production, although the software has not been packaged for distribution, and is not so well supported"
  103. ^ Digital Unix; IRIX
  104. ^ "quattor". 
  105. ^ NetBSD
  106. ^ OpenBSD
  107. ^ a b "Rex installation instructions". Retrieved 2014-07-19. 
  108. ^ a b Multiple users have successfully built and run the agent on FreeBSD, but no official package is available currently
  109. ^ "rudder-packages/rudder-agent/other at master · cfengineers-net/rudder-packages · GitHub". GitHub. 
  110. ^ Android
  111. ^ a b c Written in Java, so should in theory work on this platform if there is the appropriate JVM version available for it; however it has not been tested on the platform, which should be considered unsupported.
  112. ^ a b Will run anywhere Python runs, but handlers for different platforms are untested.
  113. ^ "SaltStack community". SaltStack. 
  114. ^ Salt was added to the OpenCSW package repository in September of 2012 in version 0.10.2 of Salt
  115. ^ "BrainBox – spacewalk". 
  116. ^ "spacewalk". 
  117. ^ "ManagingSolarisSystems – spacewalk". 
  118. ^ 4.3.3+ (Power 32); 5.1+ (Power 32/64)
  119. ^ FreeBSD 4.10 (x86-32); FreeBSD 6.1+ (x86-32)
  120. ^ 11.00+ (PA-RISC 32, IA-64)
  121. ^ (x86-32, x86-64, IA-64, PPC 64, zSeries 32/64)
  122. ^ [2]10.2+ (?)
  123. ^ 2.6+ (Sparc 32); 10+ (x86-32, x86-64)
  124. ^ 95, 98, Me, NT4, 2000, XP, 2003, Vista (x86-32), 7 (x86-32), 7 (x86-64); 2003, Vista (x86-64); 2004 (IA-64)
  125. ^ OS/400 5.2+ (iSeries 32); z/OS Unix 1.4+
  126. ^ Synctool runs on any platform that supports SSH, Rsync and Python.
  127. ^ "Getting Started | AnsibleWorks". 2013-09-25. 
  128. ^ a b
  129. ^
  130. ^ "Chef Github repository". 
  131. ^ a b Alan Sharp-Paul. "Puppet vs. Chef - The Battle Wages On". 
  132. ^
  133. ^ "Puppet & Ruby DSL - Puppet Labs". Puppet Labs. 
  134. ^ "Puppet 3.0 — 3.4 Release Notes".