home.social

#ansible — Public Fediverse posts

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

  1. CW: AI

    Out of curiosity, I have asked Claude to rewrite a tiny little SSH wrapper from Python to Go and Rust to check performance.

    Results:
    * Python = 20ms
    * Go = 3ms
    * Rust = 1.5ms

    It's totally useless if you have Mitogen because it opens the SSH connection once but if you don't, every single ms counts.

    #ssh #python #go #rust #ansible #ai

  2. CW: AI

    Out of curiosity, I have asked Claude to rewrite a tiny little SSH wrapper from Python to Go and Rust to check performance.

    Results:
    * Python = 20ms
    * Go = 3ms
    * Rust = 1.5ms

    It's totally useless if you have Mitogen because it opens the SSH connection once but if you don't, every single ms counts.

  3. CW: AI

    Out of curiosity, I have asked Claude to rewrite a tiny little SSH wrapper from Python to Go and Rust to check performance.

    Results:
    * Python = 20ms
    * Go = 3ms
    * Rust = 1.5ms

    It's totally useless if you have Mitogen because it opens the SSH connection once but if you don't, every single ms counts.

    #ssh #python #go #rust #ansible #ai

  4. CW: AI

    Out of curiosity, I have asked Claude to rewrite a tiny little SSH wrapper from Python to Go and Rust to check performance.

    Results:
    * Python = 20ms
    * Go = 3ms
    * Rust = 1.5ms

    It's totally useless if you have Mitogen because it opens the SSH connection once but if you don't, every single ms counts.

    #ssh #python #go #rust #ansible #ai

  5. CW: AI

    Out of curiosity, I have asked Claude to rewrite a tiny little SSH wrapper from Python to Go and Rust to check performance.

    Results:
    * Python = 20ms
    * Go = 3ms
    * Rust = 1.5ms

    It's totally useless if you have Mitogen because it opens the SSH connection once but if you don't, every single ms counts.

    #ssh #python #go #rust #ansible #ai

  6. I've tested Mitogen for Ansible. Now I can't tell Ansible is bad at loops anymore. It's bad at handling SSH connections by default. I feel like it runs at the speed of light now!

    mitogen.networkgenomics.com/an

    #ansible #mitogen #ssh #automation

  7. I have spent the last two days debugging why my SSH connection didn't go through The Bastion. I have automated everything with terraform so no human mistake. Network flows, user, private key, correct "from" list in the ingress key. In the end, the connection doesn't even reach the bastion. It silently dies in the wrapper in between. And of course, there is no explicit error that could have saved me hours of work. It's not lost because everything is automated now, but this is frustrating.

    When I checked the repo, there are multiple issues and pull requests to review now. So it's time to put my maintainer hat on and get things done!

    github.com/ovh/the-bastion-ans

    #ansible #bastion #ssh

  8. I have spent the last two days debugging why my SSH connection didn't go through The Bastion. I have automated everything with terraform so no human mistake. Network flows, user, private key, correct "from" list in the ingress key. In the end, the connection doesn't even reach the bastion. It silently dies in the wrapper in between. And of course, there is no explicit error that could have saved me hours of work. It's not lost because everything is automated now, but this is frustrating.

    When I checked the repo, there are multiple issues and pull requests to review now. So it's time to put my maintainer hat on and get things done!

    github.com/ovh/the-bastion-ans

  9. I have spent the last two days debugging why my SSH connection didn't go through The Bastion. I have automated everything with terraform so no human mistake. Network flows, user, private key, correct "from" list in the ingress key. In the end, the connection doesn't even reach the bastion. It silently dies in the wrapper in between. And of course, there is no explicit error that could have saved me hours of work. It's not lost because everything is automated now, but this is frustrating.

    When I checked the repo, there are multiple issues and pull requests to review now. So it's time to put my maintainer hat on and get things done!

    github.com/ovh/the-bastion-ans

    #ansible #bastion #ssh

  10. I have spent the last two days debugging why my SSH connection didn't go through The Bastion. I have automated everything with terraform so no human mistake. Network flows, user, private key, correct "from" list in the ingress key. In the end, the connection doesn't even reach the bastion. It silently dies in the wrapper in between. And of course, there is no explicit error that could have saved me hours of work. It's not lost because everything is automated now, but this is frustrating.

    When I checked the repo, there are multiple issues and pull requests to review now. So it's time to put my maintainer hat on and get things done!

    github.com/ovh/the-bastion-ans

    #ansible #bastion #ssh

  11. I have spent the last two days debugging why my SSH connection didn't go through The Bastion. I have automated everything with terraform so no human mistake. Network flows, user, private key, correct "from" list in the ingress key. In the end, the connection doesn't even reach the bastion. It silently dies in the wrapper in between. And of course, there is no explicit error that could have saved me hours of work. It's not lost because everything is automated now, but this is frustrating.

    When I checked the repo, there are multiple issues and pull requests to review now. So it's time to put my maintainer hat on and get things done!

    github.com/ovh/the-bastion-ans

    #ansible #bastion #ssh

  12. Infinito.Nexus 13.0: A Sovereign Cloud on Clearnet or Tor

    Infinito.Nexus 13.0 introduces a new choice in how organizations can operate their digital infrastructure. Until now, an Infinito.Nexus environment was primarily organized around public or private clearnet domains. Version 13.0 adds Tor onion services as a first-class deployment option. An organization can now build its application landscape on the conventional Internet, through Tor, or through a combination of both. This release includes: Tor as a first-class deployment axis Stable onion addresses generated during provisioning Tor-aware identity and Single Sign-On flows Optional parallel clearnet domains Cross-domain and cross-protocol SSO improvements Recovery tests based on real database dumps Mandatory health probes across containerized services Broader automated testing across Python, JavaScript, PHP and Ruby A consolidated and more secure CI deployment chain Together, these changes extend digital sovereignty beyond the question of who operates the servers. Infinito.Nexus 13.0 also begins addressing where services can be reached, which network infrastructure they depend on and how much an organization must disclose merely to exist online. […]

    blog.infinito.nexus/blog/2026/

  13. Infinito.Nexus 13.0: A Sovereign Cloud on Clearnet or Tor

    Infinito.Nexus 13.0 introduces a new choice in how organizations can operate their digital infrastructure. Until now, an Infinito.Nexus environment was primarily organized around public or private clearnet domains. Version 13.0 adds Tor onion services as a first-class deployment option. An organization can now build its application landscape on the conventional Internet, through Tor, or through a combination of both. This release includes: Tor as a first-class deployment axis Stable onion addresses generated during provisioning Tor-aware identity and Single Sign-On flows Optional parallel clearnet domains Cross-domain and cross-protocol SSO improvements Recovery tests based on real database dumps Mandatory health probes across containerized services Broader automated testing across Python, JavaScript, PHP and Ruby A consolidated and more secure CI deployment chain Together, these changes extend digital sovereignty beyond the question of who operates the servers. Infinito.Nexus 13.0 also begins addressing where services can be reached, which network infrastructure they depend on and how much an organization must disclose merely to exist online. […]

    blog.infinito.nexus/blog/2026/

  14. Infinito.Nexus 13.0: A Sovereign Cloud on Clearnet or Tor

    Infinito.Nexus 13.0 introduces a new choice in how organizations can operate their digital infrastructure. Until now, an Infinito.Nexus environment was primarily organized around public or private clearnet domains. Version 13.0 adds Tor onion services as a first-class deployment option. An organization can now build its application landscape on the conventional Internet, through Tor, or through a combination of both. This release includes: Tor as a first-class deployment axis Stable onion addresses generated during provisioning Tor-aware identity and Single Sign-On flows Optional parallel clearnet domains Cross-domain and cross-protocol SSO improvements Recovery tests based on real database dumps Mandatory health probes across containerized services Broader automated testing across Python, JavaScript, PHP and Ruby A consolidated and more secure CI deployment chain Together, these changes extend digital sovereignty beyond the question of who operates the servers. Infinito.Nexus 13.0 also begins addressing where services can be reached, which network infrastructure they depend on and how much an organization must disclose merely to exist online. […]

    blog.infinito.nexus/blog/2026/

  15. Infinito.Nexus 13.0: A Sovereign Cloud on Clearnet or Tor

    Infinito.Nexus 13.0 introduces a new choice in how organizations can operate their digital infrastructure. Until now, an Infinito.Nexus environment was primarily organized around public or private clearnet domains. Version 13.0 adds Tor onion services as a first-class deployment option. An organization can now build its application landscape on the conventional Internet, through Tor, or through a combination of both. This release includes: Tor as a first-class deployment axis Stable onion addresses generated during provisioning Tor-aware identity and Single Sign-On flows Optional parallel clearnet domains Cross-domain and cross-protocol SSO improvements Recovery tests based on real database dumps Mandatory health probes across containerized services Broader automated testing across Python, JavaScript, PHP and Ruby A consolidated and more secure CI deployment chain Together, these changes extend digital sovereignty beyond the question of who operates the servers. Infinito.Nexus 13.0 also begins addressing where services can be reached, which network infrastructure they depend on and how much an organization must disclose merely to exist online. […]

    blog.infinito.nexus/blog/2026/

  16. Infinito.Nexus 13.0: A Sovereign Cloud on Clearnet or Tor

    Infinito.Nexus 13.0 introduces a new choice in how organizations can operate their digital infrastructure. Until now, an Infinito.Nexus environment was primarily organized around public or private clearnet domains. Version 13.0 adds Tor onion services as a first-class deployment option. An organization can now build its application landscape on the conventional Internet, through Tor, or through a combination of both. This release includes: Tor as a first-class deployment axis Stable onion addresses generated during provisioning Tor-aware identity and Single Sign-On flows Optional parallel clearnet domains Cross-domain and cross-protocol SSO improvements Recovery tests based on real database dumps Mandatory health probes across containerized services Broader automated testing across Python, JavaScript, PHP and Ruby A consolidated and more secure CI deployment chain Together, these changes extend digital sovereignty beyond the question of who operates the servers. Infinito.Nexus 13.0 also begins addressing where services can be reached, which network infrastructure they depend on and how much an organization must disclose merely to exist online. […]

    blog.infinito.nexus/blog/2026/

  17. Automate OpenSCAP remediation on RHEL 9: run `oscap xccdf eval --results arf.xml`, then `oscap xccdf generate fix --fix-type ansible` to produce a playbook that applies all failed rule fixes, like file permissions. Save time, ensure consistency. #openscap #ansible #remediation

    valtersit.com/vault/remediate-

  18. Ansible is easy to install. A sane, reproducible development environment takes more thought.

    My downstream-first setup uses RHEL 10.2, Podman, VS Code Dev Containers, and Red Hat-packaged Ansible Development Tools, while keeping the boundaries between upstream projects, downstream products, development containers, and production Execution Environments explicit.

    blog.hofstede.it/sane-developm

    #Ansible #RHEL #Podman #devop #linux

  19. Основы Ansible — как автоматизировать конфигурации и деплой

    В статье — разбор основ Ansible: как писать идемпотентные плейбуки, не класть продакшен сухими прогонами и встроить Ansible в CI/CD. Разбираю структуру ролей, работу с динамическим инвентарём, секретами и типовые грабли новичков. Две наглядные схемы, реальный кейс из боевой практики и набор правил, которые делают автоматизацию предсказуемой и безопасной. Читать разбор

    habr.com/ru/companies/otus/art

    #Ansible #автоматизация_конфигураций #деплой #GitLab_CI #Jenkins #playbook #инфраструктура #ansiblevault #DevOpsпрактики

  20. 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

  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/

    #Ansible #YAML #Linter #CI #GitHubAction #FedoraInfra

  22. 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/

  23. 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/

    #Ansible #YAML #Linter #CI #GitHubAction #FedoraInfra

  24. 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/

    #Ansible #YAML #Linter #CI #GitHubAction #FedoraInfra

  25. 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/

    #Ansible #YAML #Linter #CI #GitHubAction #FedoraInfra

  26. Тестирование Ansible-ролей локально на macOS (Apple silicon) с помощью драйвера molecule-lima

    Разрабатываете Ansible роли на macOS с процессорами M1/M2/M3/M4? Тогда вы знаете проблему локального тестирования роли: molecule + vagrant + virtualbox не работает, molecule + vagrant + VMWare через "костыли", а Docker не подходит для тестирования системных компонентов. Я написал драйвер molecule-lima, который использует нативную виртуализацию macOS через Lima и полностью интегрируется со стандартным Molecule workflow. Драйвер реализован на Ansible playbooks, работает на macOS (ARM/Intel) и Linux, устанавливается одной командой pip install molecule-lima.

    habr.com/ru/articles/966276/

    #ansible #molecule #python3 #driver #plugin #lima #macos #apple_silicon #ansibleroles

  27. Архитектура приложения. Разбиваем приложение Ansible на модули (Inventory, Deployer)

    Привет, Хабр! Продолжу серию третьей статьей об эффективном использовании Ansible для развертывания больших инфраструктур в компаниях. В этом тексте я расскажу, какую архитектуру приложения на основе Ansible мы сформировали, и остановлюсь на модулях Deployer и Inventory.

    habr.com/ru/companies/pt/artic

    #ansible #ansible_inventory #standoff_365 #standoff #positive_technologies #цифровые_двойники #инфраструктура #инфраструктура_как_код

  28. Архитектура приложения. Разбиваем приложение Ansible на модули (Inventory, Deployer)

    Привет, Хабр! Продолжу серию третьей статьей об эффективном использовании Ansible для развертывания больших инфраструктур в компаниях. В этом тексте я расскажу, какую архитектуру приложения на основе Ansible мы сформировали, и остановлюсь на модулях Deployer и Inventory.

    habr.com/ru/companies/pt/artic

    #ansible #ansible_inventory #standoff_365 #standoff #positive_technologies #цифровые_двойники #инфраструктура #инфраструктура_как_код

  29. Архитектура приложения. Разбиваем приложение Ansible на модули (Inventory, Deployer)

    Привет, Хабр! Продолжу серию третьей статьей об эффективном использовании Ansible для развертывания больших инфраструктур в компаниях. В этом тексте я расскажу, какую архитектуру приложения на основе Ansible мы сформировали, и остановлюсь на модулях Deployer и Inventory.

    habr.com/ru/companies/pt/artic

    #ansible #ansible_inventory #standoff_365 #standoff #positive_technologies #цифровые_двойники #инфраструктура #инфраструктура_как_код

  30. Конфигуратор. Связываем хосты в единую инфраструктуру, используя функциональность Ansible inventory

    Привет, Хабр! Продолжу серию статей об эффективном использовании Ansible для развертывания больших инфраструктур компаний. В этот раз расскажу, как мы конфигурируем установку отдельных развертываемых хостов и их сервисов, а также как связываются сервисы между собой.

    habr.com/ru/companies/pt/artic

    #инфраструктура #ansible #standoff #цифровые_двойники #инфраструктура_как_код #ansible_inventory #standoff_365 #yaml #gitlab #конфигурация_сервера

  31. Конфигуратор. Связываем хосты в единую инфраструктуру, используя функциональность Ansible inventory

    Привет, Хабр! Продолжу серию статей об эффективном использовании Ansible для развертывания больших инфраструктур компаний. В этот раз расскажу, как мы конфигурируем установку отдельных развертываемых хостов и их сервисов, а также как связываются сервисы между собой.

    habr.com/ru/companies/pt/artic

    #инфраструктура #ansible #standoff #цифровые_двойники #инфраструктура_как_код #ansible_inventory #standoff_365 #yaml #gitlab #конфигурация_сервера

  32. Конфигуратор. Связываем хосты в единую инфраструктуру, используя функциональность Ansible inventory

    Привет, Хабр! Продолжу серию статей об эффективном использовании Ansible для развертывания больших инфраструктур компаний. В этот раз расскажу, как мы конфигурируем установку отдельных развертываемых хостов и их сервисов, а также как связываются сервисы между собой.

    habr.com/ru/companies/pt/artic

    #инфраструктура #ansible #standoff #цифровые_двойники #инфраструктура_как_код #ansible_inventory #standoff_365 #yaml #gitlab #конфигурация_сервера

  33. Ради разнообразия на одном маленьком проекте в 6 серверов запустил #semaphore для раскатки #ansible #playbooks. Не единым #Jenkins жив человек же 😀

    Прост, быстр и лёгок. 👍 Любителям #selfhosted решений могу предложить заценить.

  34. Less than 72 hours before the next great #production #cutover.

    We’ve done the #dryRun several times. We have documents, #playbooks (#Ansible and otherwise), and #pullrequests. (We had past pull requests that were specifically about making our current pull requests easier!) We have #troubleshooting scenarios queued up. We’ve got the work items on our #board. Not much left to do but #divide and #conquer.

    I hope the rest of the #enterprise is as well-#prepared as my #team are.

  35. I built an #alarmclock! Which is ironic cause I hate waking up 😂 It's a project I've been working on for quite some time and I used it to learn building #GUI apps in #python. It's built on #pySimpleGui and has tons of themes and fonts built in. I've built a custom #Raspberrypi image for it or you can self build with the included #ansible script. Custom song support, custom snooze, voice functionality, 12 hour or military time, alarm saving. You name it! Check it out!

    github.com/madeofpendletonwool