@vivekanandanks thanks for the interesting post. I want to suggest that the #configmanagememt analogy part (where #ansible sits, and so do several other widely used tools like #saltstack, #puppet, #chef, #cfengine) can be improved. The central premise of configuration management is that current state is dynamic, a moving target. Constantly pruning a growing tree might be a better analogy.
I love how #SaltStack stuff (mostly) "just works" on #Linux but on #Windows, "not so much". I mean, basic shit is mostly fine, but there's seemingly a lot of corner cases when you need to rely on #Jinja, particularly when it comes to how well Saltstack/Jinja/Python/Windows don't like to cooperate real well on things like file-path specification or trying to use content-blocks to prevent having mile-wide "shell" escapes

Ein neuer Monat, ein neuer #Uyuni-Artikel im #Linux-Magazin 🚀

Diesmal geht es darum, Systeme mit #SaltStack zentral zu konfigurieren. Neben States werden auch gängige CLI-Aufrufe und die Uyuni-spezifisches High States thematisiert.

👉🏻 https://www.linux-magazin.de/ausgaben/2026/05/patch-me-if-you-can/

👀 @redaktion

@lkanies @atpfm @siracusa @marcoarment I thought about why Marco and others might consider and then decide #configmanagememt is not needed… here’s where I think it shines normally, whether you use #cfengine or #puppet or #chef or #saltstack or others:

- scale / machine count / OS flavors (count of at least 150 in my experience to justify the investment, while all <100 minis are on the same OS)

- expressing diversity through machine roles and profiles (all of Marco’s machines are managed the same way)

- autonomous drift repair (probably the strongest need, but Marco seems happy doing it himself)

- DSL and wrappers/macros to express intent in an abstract way (but that requires a large investment in learning that DSL)

- dedicated infrastructure for extended functionality like monitoring outcomes and triggering actions (seems not strongly needed for those minis)

I've packaged prusa_exporter and deployed everything (prusa_exporter, prometheus, loki, grafana) on my home server with SaltStack now.

I'm loving it!

#prusa3d #3dprinting #grafana #prometheus #loki #saltstack

Comprehensive comparison of Ansible, Puppet, Chef, and SaltStack for configuration management. Explore architecture, performance, features, and ideal use cases to choose the right tool for your infrastructure automation needs.

#Ansible #Puppet #Chef #SaltStack #Configuration Management

https://dasroot.net/posts/2026/02/ansible-vs-puppet-vs-chef-vs-saltstack-configuration-management/

Ansible vs Puppet vs Chef vs SaltStack: Configuration Management Tool Comparison

Comprehensive comparison of Ansible, Puppet, Chef, and SaltStack for configuration management. Explore architecture, performance, features, and ideal use cases to choose the right tool for your infrastructure automation needs.

Technical news about AI, coding and all

  New Salt Releases: 3007.12 and 3006.20 are out! 🎉

Easily test and manage your Salt setups in a clean Docker container:

docker pull ghcr.io/cdalvaro/docker-salt-master:latest

🔧 Includes Salt API, production-ready config & more.
📚 Docs & usage examples.
💬 Feedback and PRs are welcome!

https://github.com/cdalvaro/docker-salt-master

Built for the community. Maintained with ❤️ by @cdalvaro

#SaltProject #SaltStack #DevOps #Docker #Containers #SaltAPI #Automation #IoT #Puppet

GitHub - cdalvaro/docker-salt-master: 🐳🧂 Dockerized Salt Master - Boost your @saltstack master service with the power of @docker

🐳🧂 Dockerized Salt Master - Boost your @saltstack master service with the power of @docker - cdalvaro/docker-salt-master

GitHub

New blog post: How I came to know John Cage in the mountains of Western NC and regularly stumble on ways his thinking has helped me navigate complexity.

https://www.sounding.com/2026/01/20/scale-is-step-by-step/

#JohnCage #BlackMountain #Complexity #Riak #SaltStack #DistributedDatabases #DistributedSystems #ComplexSystems #SystemsThinking

Scale is Step by Step

John Cage from poetry to databases

Today I figured out why my #saltstack pkg.installed states on #freebsd sometimes failed. Just used it in a wrong way 😇 , but still no clue why it worked sometimes and sometimes not , but now I have working version where I can set the version of the package which was not implemented and only worked accidentally. Task for tomorrow creating pull request.

Finally nailed down a #Saltstack state for installing #bookstack. The automated Ubuntu script just wasn't working well for me.

Looking forward to introducing the app at $DAYJOB.