Comparison of open-source configuration management software explained

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

"Verify mode" (also called dry run) 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. Although "Agent-less" = "No" is colored red and might seem to be a negative, in fact having an agent can be considered quite advantageous to many. Consider the impact if an agent-less tool loses connectivity to a node while making critical changes—leaving the node in an indeterminate state that compromises its (production?) functionality.

LanguageLicenseMutual auth.EncryptionVerify modeAgent-less GUIFirst releaseLatest stable release
AnsiblePythonGPLv3+[1] 2012-03-082023-11-11 2.15.4[2]
Bcfg2PythonBSD 2-clause[3] [4] 2004-08-11[5] 2015-06-11 1.3.6
CapistranoRubyMIT License20052022-08-07 3.17.1
cdistPythonGPLv3+20102021-08-24 6.9.8[6]
ChefRuby, ErlangApache 2.0[7] 2009-01-15 0.5.02023-01-05 18.1.0 (client),[8] 15.4.0 (server)[9]
CFEngineC[10] GPLv3[11] [12] [13] [14] [15] [16] [17] 19932024-07-22 3.24.0,[18] 2024-06-21 3.21.5,[19] 2024-06-21 3.18.8,[20]
ISconfPythonGPL[21] [22] 19982006-08-13 4.2.8.233
JujuPython, Go[23] AGPL[24] 2010-09-17[25] 2024-02-15 3.4.0[26]
Local ConFiGuration system (LCFG)PerlGPL[27] [28] 1994Weekly Releases
PythonBSD License 2.02012-03-08 2015-05-20 15.05.1[29]
OCS Inventory NG with GLPIPerl, PHP, C++GPL[30] 20032014-07-13[31]
Open pc server integration (Opsi)Python, JavaGPL20042013-03-01 4.0.3
PIKTCGPLv2+[32] [33] [34] 1998[35] 2007-09-10 1.19.0
PuppetRuby, C++ & Clojure (server-side also Ruby before 4.0[36])Apache since 2.7.0, GPL before then[37] [38] 2005-08-30[39] 2024-04 8.6.0, 7.30.0 (client),[40] 2024-04 8.6.0, 7.17.0 (server)[41]
QuattorPerl, PythonApache 2.0[42] [43] [44] [45] 2005-04-01[46] 2023-08-14 23.6.0[47]
RadmindCBSD[48] [49] [50] 2002-03-26[51] 2008-10-08 1.13.0[52]
PerlApache2010-11-05 0.9.0[53] 2021-07-05 1.13.4[54]
RudderC, Scala and RustGPLv3 and Apache 2.0[55] [56] 2011-10-312023-07-21 7.3.4 [57]
SmartFrogJavaApache 2.0[58] [59] 2004-02-112012-03-13 3.18.016[60]
Salt[61] Python[62] Apache 2.0[63] [64] Both[65] [66] [67] [68] 2011-03-17 0.6.0[69] 2023-05-05 v3006.1[70]
SpacewalkJava (C, Perl, Python, PL/SQL)GPLv22008-06[71] 2019-01-14 2.9[72]
STAFC++CPL[73] [74] 1998-02-16[75] 2012-12-16 3.4.16 [76]
Synctool[77] Python[78] GPLv2[79] [80] 2003[81] 2019-08-11 6.3[82]
UyuniJava, Python, PL/SQL (Perl)GPLv2/Apache 2.0Both2018-06[83] 31-01-2024 2024.01[84]
LanguageLicenseMutual authEncryptsVerify modeAgent-lessHave a GUIFirst releaseLatest stable release

Platform support

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-UXLinuxOS XSolarisWindowsOthers
Ansible (excluding controller)[85]
Bcfg2
CFEngine (enterprise version only)
cdist
Chef
ISconf
Juju
Local ConFiGuration system (LCFG)
Open pc server integration (Opsi)
PIKT
Puppet
Quattor[86]
Radmind
Rex[87]
Rudder[88]
SmartFrog
Salt[89] [90]
Spacewalk[91] [92] [93]
STAF[94]
Synctool
Uyuni
AIX
  • BSD
HP-UXLinuxOS XSolarisWindowsOthers

Short descriptions

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.

Ansible
  • Combines multi-node deployment, ad-hoc task execution, and configuration management in one package. Manages nodes over SSH and requires python (2.6+ or 3.5+) to be installed on them.[95] Modules work over JSON and standard output and can be written in any language. Uses YAML to express reusable descriptions of systems.
    Bcfg2
  • 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.
    CFEngine
  • 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.[96] CFEngine's paradigm is convergent "computer immunology".[97]
    cdist
  • 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
  • Chef is a configuration management tool written in Erlang,[98] 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.[99]
    ISconf
  • 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
  • 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.[100]
    PIKT
  • 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
  • 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.[96] [99] [101] [102]
    Quattor
  • 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
  • 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
  • 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.
    Salt
  • 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.
    SmartFrog
  • 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
  • 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). As of May 2020, Spacewalk is now EOL with users having moved to either Uyuni or Foreman/Katello.
    STAF
  • 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
  • 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. Synctool depends on Python2 which is now EOL and there are no current plans to migrate it to Python3.

    See also

    Notes and References

    1. Web site: AWX Project FAQ - Ansible.com. Red Hat, Inc.. ansible.com.
    2. Web site: Ansible community changelogs . docs.ansible.com . Red Hat, Inc. . 1. 2022-04-26.
    3. Web site: bcfg2/LICENSE at master · Bcfg2/bcfg2 · GitHub . Github.com . 2014-02-10.
    4. Web site: Bcfg2 Web Reporting System — Bcfg2 1.3.6 documentation.
    5. Web site: Download – Bcfg2 . bcfg2.org . 2017-06-04.
    6. Web site: cdist 6.9.8 has been released.
    7. Web site: [#CHEF-13] Add -noop support - Opscode Open Source Ticket Tracking |publisher=Tickets.opscode.com |access-date=2014-02-10 |archive-url=https://web.archive.org/web/20140226055656/https://tickets.opscode.com/browse/CHEF-13 |archive-date=2014-02-26 |url-status=dead ].
    8. Web site: Chef Infra Client 18.1.0 Released! - Chef Release Announcements - Chef Questions. 5 January 2023 . 2023-01-26.
    9. Web site: Chef Infra Server 15.4.0 Released! - Chef Release Announcements - Chef Questions. 5 January 2023 . 2023-01-26.
    10. Web site: CFEngine Source Code . 26 May 2020 . Northern.tech AS..
    11. Web site: core/License at master · cfengine/core · GitHub. GitHub. 26 May 2020.
    12. TLS: Uses TLS. Web site: tls_min_version in common control. Northern.tech . 2018-11-30.
    13. Web site: --dry-run option for cf-agent. Northern.tech . 2022-01-14.
    14. Web site: dryrun option in agent control. Northern.tech . 2018-11-30.
    15. Web site: --simulate option for cf-agent. Northern.tech . 2022-01-14.
    16. Web site: Common promise attribute action_policy warn or nop. Northern.tech . 2022-01-14.
    17. Web site: CFEngine Enterprise Mission Portal. Northern.tech AS..
    18. Web site: CFEngine 3.24.0 released. Northern.tech AS..
    19. Web site: CFEngine 3.21.5 released . Northern.tech AS..
    20. Web site: CFEngine 3.18.8 released . Northern.tech AS..
    21. Web site: /trunk/LICENSE - ISconf - Trac . Trac.t7a.org . 1989-04-01 . 2014-02-10 . https://archive.today/20130415235717/http://trac.t7a.org/isconf/browser/trunk/LICENSE . 2013-04-15 . dead .
    22. Improved security which would include an encrypted, mutually authenticated, peer-to-peer message bus is tracked here Web site: #39 (Implement TCP mesh) - ISconf - Trac . 2007-04-17 . dead . https://archive.today/20120716131832/http://trac.t7a.org/isconf/ticket/39 . 2012-07-16 . .
    23. Web site: Juju Source Code . github.com . 2015-06-19 . 2015-06-21.
    24. Web site: Juju Gui . jujucharms.com . 2015-06-15 . 2015-06-21 . https://web.archive.org/web/20150621233749/https://demo.jujucharms.com/trusty/juju-gui/ . 2015-06-21 . dead .
    25. Web site: timeline : pyjuju . Launchpad.net . 2014-02-10.
    26. Web site: GitHub . github.com . 2022-03-21.
    27. 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".
    28. 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".
    29. Web site: NOC. nocproject.org.
    30. Server authenticates to client, but client does not authenticate to server. See OCS Inventory NG Installation and Administration guide, page 114.
    31. Web site: 2.1.2 stable published . OCS Inventory NG . 2014-12-16.
    32. Web site: Robert Osterlund . PIKT Licensing . Pikt.org . 2014-01-04 . 2014-02-10.
    33. 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.
    34. "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.
    35. Web site: Index of /pikt/dist . Pikt.org . 2014-02-10.
    36. Web site: Evolving Puppet for the Next 10 Years . Luke Kanies . 2014-09-23 . 2017-05-26.
    37. Web site: puppet agent Man Page — Documentation — Puppet Labs . Docs.puppetlabs.com . 2014-02-10 . https://web.archive.org/web/20130707135331/http://docs.puppetlabs.com/man/agent.html . 2013-07-07 . dead .
    38. Web site: Puppet Management GUI Comparison. olindata.com. 2015-01-12. https://web.archive.org/web/20150117063953/http://www.olindata.com/blog/2014/01/puppet-management-gui-comparison. 2015-01-17. dead.
    39. Web site: Index of /puppet . Puppetlabs.com . 2014-02-10.
    40. Web site: Puppet release notes . 2024-05-06.
    41. Web site: Puppet Server: Release Notes . 2024-05-06.
    42. Web site: EU DataGrid Software License (EUDatagrid) | Open Source Initiative . Opensource.org . 1999-02-22 . 2014-02-10.
    43. Web site: DataGrid Software License (do not change the page URL) . Eu-datagrid.web.cern.ch . 2004-05-26 . 2014-02-10.
    44. "Client to server authentication and vice versa: on one hand, this allows to enforce access policiesto sensitive data according to the client "name", on the other hand, clients are guaranteed to talk tothe original server." - from Quattor Installation and User Guide: Version 1.1.x, page 70
    45. "[...] 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
    46. Web site: Index of /quattorsw/software/quattor/release . Quattorsw.web.cern.ch . 2014-02-10 . https://web.archive.org/web/20140318090836/http://quattorsw.web.cern.ch/quattorsw/software/quattor/release/ . 2014-03-18 . dead .
    47. Web site: Quattor 23.6.0 released. quattor.org.
    48. Web site: Research Systems Unix Group: beepage . Rsug.itd.umich.edu . 2014-02-10 . https://web.archive.org/web/20150210155103/http://rsug.itd.umich.edu/software/copyright.html . 2015-02-10 . dead .
    49. "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
    50. "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
    51. Web site: Radmind - Browse /radmind/radmind-0-6-0 at . Sourceforge.net . 2006-02-10 . 2014-02-10.
    52. Web site: Radmind. fitterhappier. sourceforge.net.
    53. Web site: Release 0.9.0 · krimdomu/Rex · GitHub. GitHub.
    54. Web site: Rex/ChangeLog at master · RexOps/Rex · GitHub. GitHub.
    55. Web site: Rudder FAQ. rudder.io.
    56. Web site: Policy Mode (Audit/Enforce) - Rudder 4.0 - User Manual . rudder-project.org . 2017-01-17.
    57. Web site: Change logs for Rudder 7.3 :: Rudder Documentation. rudder.io.
    58. Web site: SmartFrog / SVN / Commit [r8898]]. 2017-05-16. Sourceforge.
    59. See Using the new SmartFrog Security
    60. Web site: SmartFrog - Browse /development/smartfrog-3.18.016 at SourceForge.net . 2022-04-27.
    61. http://saltstack.org/ Salt
    62. Web site: Installation. saltstack.com.
    63. Web site: SaltStack community. SaltStack.
    64. Web site: SaltStack community. SaltStack.
    65. Web site: Salt SSH. saltstack.com.
    66. Web site: SaltStack Enterprise. SaltStack.
    67. Web site: erwindon/SaltGU. GitHub. 20 May 2021.
    68. Web site: vRealize Automation SaltStack Config. vmware.com.
    69. Web site: SaltStack community. SaltStack.
    70. Web site: Salt Releases. saltstack.com.
    71. Web site: SpacewalkFaq – spacewalk. fedorahosted.org.
    72. Web site: spacewalkproject/spacewalk . fedorahosted.org -->. GitHub. en. 2018-10-18.
    73. Web site: Software Testing Automation Framework (STAF). sourceforge.net.
    74. 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.
    75. Web site: Software Testing Automation Framework (STAF). sourceforge.net.
    76. Web site: Software Testing Automation Framework (STAF). sourceforge.net.
    77. http://www.heiho.net/synctool/ Synctool
    78. Web site: synctool documentation. heiho.net.
    79. Web site: synctool/LICENSE at master · walterdejong/synctool · GitHub. GitHub.
    80. Web site: synctool documentation. walterdejong.github.io.
    81. Web site: synctool documentation. heiho.net.
    82. Web site: Synctool releases. GitHub.
    83. Web site: Uyuni: Forking Spacewalk with Salt and Containers. 26 May 2018 .
    84. Web site: "Uyuni 2024.01 is released" . 2024-02-01 . Uyuni . en.
    85. 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.
    86. Web site: quattor. sourceforge.net.
    87. Web site: Rex installation instructions. 2014-07-19.
    88. Web site: rudder-packages/rudder-agent/other at master · cfengineers-net/rudder-packages · GitHub. GitHub.
    89. Web site: SaltStack community. SaltStack.
    90. http://docs.saltstack.org/en/latest/topics/installation/solaris.html Salt was added to the OpenCSW package repository in September of 2012 in version 0.10.2 of Salt
    91. Web site: BrainBox – spacewalk. fedorahosted.org.
    92. Web site: spacewalk. fedorahosted.org.
    93. Web site: ManagingSolarisSystems – spacewalk. fedorahosted.org.
    94. http://sourceforge.net/tracker/index.php?func=detail&aid=1458480&group_id=33142&atid=407383
    95. Web site: Installation — Ansible Documentation. 2018-01-29.
    96. Web site: CFEngine vs Puppet: Detailed Comparison | UpGuard.
    97. Burgess . Mark . Computer Immunology . Systems Administration Conference . December 1998 . Boston, Massachusetts.
    98. Web site: Chef Github repository. . 21 May 2021.
    99. Web site: Puppet vs. Chef - The Battle Wages On. Alan Sharp-Paul. upguard.com.
    100. Web site: opsi features . 2009-02-22 . https://web.archive.org/web/20090130033052/http://www.opsi.org/features/ . 2009-01-30 . dead .
    101. Web site: Puppet & Ruby DSL - Puppet Labs. Puppet Labs.
    102. Web site: Puppet 3.0 — 3.4 Release Notes. puppetlabs.com. 2013-05-23. https://web.archive.org/web/20130513170449/http://docs.puppetlabs.com/puppet/3/reference/whats_new.html#ruby-dsl-is-deprecated. 2013-05-13. dead.

    This article is licensed under the GNU Free Documentation License. It uses material from the Wikipedia article "Comparison of open-source configuration management software".

    Except where otherwise indicated, Everything.Explained.Today is © Copyright 2009-2024, A B Cryer, All Rights Reserved. Cookie policy.