home.social

#ansible — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #ansible, aggregated by home.social.

  1. For those who are wondering why my projects are so silent, I moved to my own Forgejo instance at code.spoljarevic.sh

    From there I will continue my journey.

    Tho I didn’t have lots of time to work on them, and they will slightly change.

    Due to an upcoming server migration, new tools and my personal life, everything got slow.

    But I already finished some open issues on the Ansible Project and will go into testing after my vacation.

    It shall be finished this month or I’m no longer trusting myself.

    Next month will be nothing since I’m gonna focus on chess openings and the month after I’m working on a Knowledge Base (fork of hyprland wiki)

    After that, everything should go normal again.

    #ansible #archlinux #project #forgejo #server #ServerMigration #wiki #KnowledgeBase #chess #chessopenings

  2. For those who are wondering why my projects are so silent, I moved to my own Forgejo instance at code.spoljarevic.sh

    From there I will continue my journey.

    Tho I didn’t have lots of time to work on them, and they will slightly change.

    Due to an upcoming server migration, new tools and my personal life, everything got slow.

    But I already finished some open issues on the Ansible Project and will go into testing after my vacation.

    It shall be finished this month or I’m no longer trusting myself.

    Next month will be nothing since I’m gonna focus on chess openings and the month after I’m working on a Knowledge Base (fork of hyprland wiki)

    After that, everything should go normal again.

    #ansible #archlinux #project #forgejo #server #ServerMigration #wiki #KnowledgeBase #chess #chessopenings

  3. For those who are wondering why my projects are so silent, I moved to my own Forgejo instance at code.spoljarevic.sh

    From there I will continue my journey.

    Tho I didn’t have lots of time to work on them, and they will slightly change.

    Due to an upcoming server migration, new tools and my personal life, everything got slow.

    But I already finished some open issues on the Ansible Project and will go into testing after my vacation.

    It shall be finished this month or I’m no longer trusting myself.

    Next month will be nothing since I’m gonna focus on chess openings and the month after I’m working on a Knowledge Base (fork of hyprland wiki)

    After that, everything should go normal again.

  4. Well, at least maybe just maybe orgs can get a better grip on AI with products like what Ansible introduced.

    “Why would you use AI just to patch a machine?” he says. “We all know tokens are expensive. We know the best way to patch a machine — why call an AI to do that when you already have a playbook that’s been in use for ten years?”

    Yes, why would you use AI to patch a machine? I like how this is presented at least. We'll see how it works out. AI is here to stay in orgs for the forseeable future so IT departments need to look into ways to control these agents better.

    It may even make the folks over in your SOC a little bit happier.

    #ansible #redhat #ai #llm #automation

    networkworld.com/article/41700

  5. Well, at least maybe just maybe orgs can get a better grip on AI with products like what Ansible introduced.

    “Why would you use AI just to patch a machine?” he says. “We all know tokens are expensive. We know the best way to patch a machine — why call an AI to do that when you already have a playbook that’s been in use for ten years?”

    Yes, why would you use AI to patch a machine? I like how this is presented at least. We'll see how it works out. AI is here to stay in orgs for the forseeable future so IT departments need to look into ways to control these agents better.

    It may even make the folks over in your SOC a little bit happier.

    #ansible #redhat #ai #llm #automation

    networkworld.com/article/41700

  6. Well, at least maybe just maybe orgs can get a better grip on AI with products like what Ansible introduced.

    “Why would you use AI just to patch a machine?” he says. “We all know tokens are expensive. We know the best way to patch a machine — why call an AI to do that when you already have a playbook that’s been in use for ten years?”

    Yes, why would you use AI to patch a machine? I like how this is presented at least. We'll see how it works out. AI is here to stay in orgs for the forseeable future so IT departments need to look into ways to control these agents better.

    It may even make the folks over in your SOC a little bit happier.

    #ansible #redhat #ai #llm #automation

    networkworld.com/article/41700

  7. Well, at least maybe just maybe orgs can get a better grip on AI with products like what Ansible introduced.

    “Why would you use AI just to patch a machine?” he says. “We all know tokens are expensive. We know the best way to patch a machine — why call an AI to do that when you already have a playbook that’s been in use for ten years?”

    Yes, why would you use AI to patch a machine? I like how this is presented at least. We'll see how it works out. AI is here to stay in orgs for the forseeable future so IT departments need to look into ways to control these agents better.

    It may even make the folks over in your SOC a little bit happier.

    #ansible #redhat #ai #llm #automation

    networkworld.com/article/41700

  8. Well, at least maybe just maybe orgs can get a better grip on AI with products like what Ansible introduced.

    “Why would you use AI just to patch a machine?” he says. “We all know tokens are expensive. We know the best way to patch a machine — why call an AI to do that when you already have a playbook that’s been in use for ten years?”

    Yes, why would you use AI to patch a machine? I like how this is presented at least. We'll see how it works out. AI is here to stay in orgs for the forseeable future so IT departments need to look into ways to control these agents better.

    It may even make the folks over in your SOC a little bit happier.

    #ansible #redhat #ai #llm #automation

    networkworld.com/article/41700

  9. @violet
    There are many opinions and combinations possible, of course. I prefer simple, community backed, and solid foss blocks that interoperate. That converged to:
    * #debian for base OS
    * data on encrypted #zfs
    * #incus for VM and system containers management (formerly LXD)
    * #ansible for automation, with the debops collection

    Infrastructure for people, to solve our problems and at our scale, with all the tools under direct control of worker sysadmins

  10. 200 serveurs et une config à déployer... 😱

    Sans #Ansible, c'est une soirée perdue !
    Avec, c'est un playbook YAML, une commande et c'est fait.

    ✅ Architecture sans agent
    ✅ Idempotence native
    ✅ Inventaire dynamique
    ✅ Hautement compatible

    Moins de bruit, moins d'interventions manuelles... Et plus de disponibilité !

    Découvrez notre article :
    capensis.fr/ansible-le-gestion

    #SysAdmin #Automatisation #IaC #OpenSource #Linux

  11. Rebuilding my #homelab once more. I switched from #k3s to #talos quite a while ago. As it goes, my experiments left k8s in a ... well ... undefined state. Time to set it up all over again. Sending a huge thanks to Jochen from a few months ago for automating everything. #Talos + #Ansible + #Argo make for really nice experience and I got all my services back in no time, including data.

  12. Rebuilding my #homelab once more. I switched from #k3s to #talos quite a while ago. As it goes, my experiments left k8s in a ... well ... undefined state. Time to set it up all over again. Sending a huge thanks to Jochen from a few months ago for automating everything. #Talos + #Ansible + #Argo make for really nice experience and I got all my services back in no time, including data.

  13. Rebuilding my #homelab once more. I switched from #k3s to #talos quite a while ago. As it goes, my experiments left k8s in a ... well ... undefined state. Time to set it up all over again. Sending a huge thanks to Jochen from a few months ago for automating everything. #Talos + #Ansible + #Argo make for really nice experience and I got all my services back in no time, including data.

  14. Rebuilding my #homelab once more. I switched from #k3s to #talos quite a while ago. As it goes, my experiments left k8s in a ... well ... undefined state. Time to set it up all over again. Sending a huge thanks to Jochen from a few months ago for automating everything. #Talos + #Ansible + #Argo make for really nice experience and I got all my services back in no time, including data.

  15. Rebuilding my #homelab once more. I switched from #k3s to #talos quite a while ago. As it goes, my experiments left k8s in a ... well ... undefined state. Time to set it up all over again. Sending a huge thanks to Jochen from a few months ago for automating everything. #Talos + #Ansible + #Argo make for really nice experience and I got all my services back in no time, including data.

  16. Fresh gist: mitigating CVE-2026-31431 ("Copy Fail") on RHEL 8/9/10 with a tiny Ansible playbook.

    It blacklists algif_aead via a kernel boot arg (initcall_blacklist=algif_aead_init), reboots only when needed, and asserts the mitigation actually stuck after reboot. Idempotent & safe to re-run.

    codeberg.org/Larvitz/gists/src

    #Ansible #RHEL #Linux #InfoSec #SysAdmin #DevOps #CVE #CVE_2026_31431 #copyfail

  17. Мини-пайплайн на страже синтаксиса и секретов в Ansible

    Представим, что у нас есть репозиторий, где хранятся плейбуки и роли Ansible. Делался он долго, старательно и по правилам. И даже если мы перед коммитами проверяем его через линтер, чтобы не сломать хрупкую YAML красоту, и перепроверяем не забыли ли мы подчистить секреты с которыми проводили тесты, то рано или поздно подобную ошибку совершит кто-то другой. И вот, чтобы снизить такую вероятность и лишний раз не заниматься правками в Git, чтобы вычистить пароли или поправить форматирование, можно немного обезопасить репозиторий заранее.

    habr.com/ru/articles/1029976/

    #ansible #linter #dockerfile #docker_compose #github_actions #git

  18. New blog post: Ansible-Native Quadlets: Deploying a Mastodon Greeter Bot with containers.podman

    Hand-written Quadlet files are great for one host. For a small fleet, I want them in Ansible: templated config, registry login, Podman secrets, systemd handlers, SELinux labels, and repeatable deployment.

    The example: a tiny Mastodon welcome bot running as a Podman Quadlet-managed systemd service.

    blog.hofstede.it/ansible-nativ

    #Linux #Ansible #Podman #Quadlet #systemd #Mastodon #SelfHosting #RHEL

  19. This year's #SUSECON was very special for me: it was the very first time I contributed to the schedule. My session was also mentioned during the Demopalooza keynote! 🤯

    In my talk "TUTORIAL-1070 - #SUSE Multi-Linux Manager best practices from the field" I summarzied lessons learned from 10 years of using Spacewalk and Uyuni. It covered best practices from projects and automation possibilities - e.g. spacecmd and #Ansible. Also received valuable feedback - it was a blast! 🤩

  20. The Bullhorn #225 is out!

    This week's highlights include:
    - Ansible and the EU Cyber Resilience Act.
    - New Ansible-Core and Ansible Community Package releases.
    - 9 collection updates - check the newsletter for the full list.
    - Discussions around documenting breaking changes in collections.
    - The Ansible Community AI Policy Proposal.

    Read more: forum.ansible.com/t/the-bullho

  21. Pavel just released new version of vcs-diff-lint 🛠️ The tool (+ GitHub action) for differential code linting.

    The highlight: Newly with yamllint support!

    Bonus: Fedora's Forgejo instance integration experiment (infra ansible repo):
    forge.fedoraproject.org/infra/

  22. Управление SSH-доступом в 2026 году: от зоопарка с jump-host и Ansible к единой точке входа в инфраструктуру с Warpgate

    Привет! Меня зовут Амир Уразалин, я DevOps-инженер в KTS . В аутсорсинговой модели мы одновременно ведем несколько крупных проектов, каждый со своей инфраструктурой, окружениями и требованиями безопасности. При этом команда инженеров общая, а доступ к виртуальным машинам должен управляться централизованно, прозрачно и безопасно. По мере роста числа проектов и серверов управлять доступом становилось все сложнее, поэтому мы начали искать новое решение.

    habr.com/ru/articles/1020250/

    #devops #управление_доступом #itинфраструктура #инфраструктура #аутсорс #sso #warpgate #ansible #jumpсервер

  23. Next level in my Homelab: A storage cluster with linbit drbd. Should run on the same nodes as proxmox pve. And of course defined in some ansible scripts 🤣
    Currently, this is still running on a test cluster that I set up using OpenTofu on top of the current pve cluster.
    But there are still some "hickups"

    #homelab #linbit #drbd #proxmox #pve #ansible #OpenTofu #TerraForm

  24. My unbound servers are deployed. I can now remove the "ansible_host" variables from my inventory.

    #homelab #selfhosting #unbound #ansible

  25. Experimenting a bit with Ansible at the moment in the sense of seeing if I can convert my Bash-Scripts to Ansible Playbooks.

    Yesterday I did the first try by converting my sixes-converter script to a playbook.

    It works surprisingly well so I’m looking forward to how much I can actually make usable this way.
    If you’d like to get a look at it, you can see it here on my Codeberg Ansible Repo under the Development branch: codeberg.org/Spoljarevic/Ansib

    Let the madness beginn!

    #bash #ansible #scripts #playbook #converter #madness