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'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

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

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

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

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

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

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

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

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

  17. But I had absolutely no problem with that, because all of the containers have been deployed as #Quadlets with #Ansible and persistent data was mapped to host paths, protected by #SELinux. Everything was just redeployed in a glimpse.

    I am so sorry, Docker, I am not going to turn back to you.

  18. Red Hat wrote an email explaining their move to restructure their certification program and how they are sorry because they have interrupted my plans to become a Red Hat Certified Architect.

    To become a RHCA before, you had to become a Red Hat Certified Engineer (Ansible + RHEL Admin) first.

    From that, you chose five other certifications from a list to learn and pass the exams.

    Now there is not one but different RHCAs by topics, such as "Cloud and Containers", "RHEL Linux Admin", "Automation", etc.

    I already passed two of the five exams (Specialist in Containers and Openshift Admin).

    They want me to decide which new path I'd like to follow or whether to follow the old model until the end of 2026. 🤔

    #RedHat #ITCertification #Learning #ansible #openshift #sysadmin #devops

  19. "The question isn't whether #AI will replace #DevOps engineers. It's whether you understand your systems well enough to know when it's wrong. It will be wrong. And it won't tell you." - Heinan Cabouly

    Companies in regulated industries such as #TDBank, #Vega and #EY are proceeding with caution with #AIagents for #InfrastructureasCode -- but proceeding nonetheless. And a new developer interface for IT automation might be taking shape...

    Get all the details, including #Ansible by #RedHat 's approach to this shift, in my latest writeup here: techtarget.com/searchitoperati

  20. One of the most useful Red Hat products I use daily is also one of the least-known: the Red Hat Offline Knowledge Portal (RHOKP).

    It is basically a self-hosted, locally searchable mirror of docs.redhat.com + the Red Hat Knowledgebase in a single container image.

    Perfect for:

    - air-gapped environments
    - customer networks with painful proxies
    - trains, planes, and terrible WiFi
    - anyone who wants docs that still work offline

    I wrote up how it works, why I think it matters, and how to run it locally with Podman:

    blog.hofstede.it/red-hat-offli

    #linux #redhat #ansible #openshift #rhokp #docs #devops

  21. Лучшие практики деплоя: Ansible, GitLab CI

    Ручной деплой через SSH и bash-скрипты – это практика, которая рано или поздно приводит к инцидентам. В этой статье разбираем, как построить предсказуемый Continuous Delivery с помощью Ansible и GitLab CI. Обсуждаем реальный кейс миграции, пишем плейбуки, настраиваем zero-downtime rolling update и автоматические откаты.

    habr.com/ru/companies/otus/art

    #Ansible #GitLab_CI #деплой #Continuous_Delivery #rolling_update #zerodowntime #автоматизация_деплоя #healthcheck #DevOpsпрактики

  22. Unser Dozent Sven Velt ist begeisterter #Ansible-Fan und gibt sein gesammeltes Wissen in #Schulungen an der Heinlein Akademie weiter.

    Warum sich #Admins im Konfigurationsmanagement mit Ansible fit machen sollten?

    Ansible ist ein mächtiges Tool, um IT-Infrastrukturen effizient und zuverlässig zu automatisieren, standardisierte Abläufe zu entwickeln und Best Practices für die Wartung und Skalierung moderner Umgebungen zu nutzen.

    Du willst mehr über Ansible lernen?

    👉 heinlein-support.de/schulung/k

  23. IT pros and #SysAdmins! Tired of late-night patching? Check out my new episode, GitOps for the Linux Administrator on The #ITGuyShow! Join me with #ChristianHernandez, a #Linux guy and #DevOps advocate, as we explore his journey from Solaris servers to #GitOps evangelism.

    Learn: The true meaning of GitOps, a new mindset, tools like #ansible, #terraform, and #ArgoCD! Perfect for "lazy" admins valuing efficiency! Enhance your skills and transform infrastructure management: podcast.itguyeric.com/10

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

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

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

  26. JILL 2019 – « L’automatisation avec Ansible et AWX» par Baptiste Ivol, @Linagora Canada - Baptiste Ivol de Linagora Canada a présenté sur Ansible et AWX.

    The AWX Project -- AWX for short -- is an open source community project, sponsored by Red Hat, that enables users to better c ... (la suite sur magicfab.ca/2019/09/jill-2019-)
    #Montreal #canada #Microblog #Ansible #jill #sfd2019 #sqil #awx #linagora