cdist vs OpenDSC

cdist is a free, open-source configuration management system that applies a defined state to computers through shell scripts and cdist types. It is positioned as an alternative to Ansible, Chef, and Puppet. Types provide the extension mechanism, and the project says their results are idempotent, so outcomes do not depend on call order. cdist uses push mode: source computers connect to targets over SSH and apply configuration, without requiring a central server or an agent on the target. A target needs a POSIX-compatible shell and SSH server, while the source needs a POSIX-like shell, Python 3.5 or later, and an SSH client. The project lists a small core, standard types, and parallel execution. Installation is documented through Git or pip. Supported systems include Linux distributions, BSD systems, Mac OS X, and XenServer. Manuals are available in HTML and man-page formats, with community help through Matrix and IRC.

OpenDSC is a configuration management platform for Microsoft Desired State Configuration, intended for teams managing settings across infrastructure nodes. Its Local Configuration Manager monitors system state and can automatically correct configuration drift. For centralized management, the pull server registers nodes, distributes configurations, and provides compliance reporting through a web dashboard and REST API. Configurations can be versioned, assembled into composite deployments, and parameterized by region, environment, or node. Local file-based configurations support disconnected use as well as server-driven pulls. The resource library covers Windows administration, SQL Server, and file, JSON, XML, and archive tasks across Windows, Linux, and macOS. The Resource Development Kit provides .NET libraries and tools for developing custom resources. The pull server supports OpenID Connect providers, client-certificate mutual TLS, role-based access control, and retention policies. SQLite is supported for development, while production deployments can use SQL Server or PostgreSQL. The project is MIT licensed and self-hosted. Its roadmap lists native Linux and macOS LCM services, distribution packages, and official Docker deployment as planned work.