Because I'm stupid, my next little project is simplifying not only #distrohopping but OS-hopping (in a very limited and specific way):

I'm attempting to build an #Ansible play to deploy #HAProxy with #acme (via acme.sh) identically across #Fedora #Debian #Ubuntu and #FreeBSD servers. Why? Why not?

Hunting down easter eggs & putting them all in a single basket? Hopefully you're not doing the same with your VMs - the new ProxLB v1.1.1 is out, now!

#ProxLB is a loadbalancer for #Proxmox clusters that balances guests across your nodes based on cpu, memory or (local) disk size. It also comes with additional features like:
* Affinity / anti-affinity rules
* Maintenance mode
* Node evacuation (based on best resource usage)
* Best node evaluation for CI/CD (e.g. #Ansible or #Terraform)

The #Ansible role for #BigBlueButton is now able to install and configure BBB 3.0.x with embedded #coturn, even on cloud VMs behind a NAT router or firewall.

https://github.com/ebbba-org/ansible-role-bigbluebutton/tree/bbb/3.0

The mini-rack #K3s cluster is complete. Refamiliarizing with #Ansible to get everything set up because I'm going to finally have my #homelab configuration documented and backed up, dammit.

Sometimes it feels like Ansible is a lot more friendly with home lab and self hosting than Terraform. A lot of things I want to do with Terraform do not have official providers, while Ansible does have a lot of official modules.

I'm not looking for a solution, just making an observation.

Ein paar Merge Requests für die Doku von ansible semaphore erstellt. Ich mag Semaphore, aber die Doku ist ausbaufähig
Mit all den offenen Doku Merge Requests, die der anderen und meiner, dürfte die Doku deutlich besser werden. Auch wenn es nicht meine Doku ist, freue ich mich, sollten alle MRs demnächst gemerged werden :)

What do you guys do about breaking home directories in #Linux.

I mean every desktop env after some time gets flaky and then you feel like you wanted a reset but you don't want a reset because it's a lot of work to reconfigure everything and you will probably forget about details.
I mean there's #nixos but despite me liking the idea I don't like the implementation

Are there highly mature #Ansible roles for like #gnome #kde or whatever?

How do you tackle this?

TIL: There is probably breaking change in Ansible 2.13 in ansible.builtin.env lookup concerning undefined variables.

According to https://docs.ansible.com/ansible/latest/collections/ansible/builtin/env_lookup.html

Old Ansible:
'{{ lookup("env", "CI_PIPELINE_IID") | default("local") }}'

New Ansible:
'{{ lookup("env", "CI_PIPELINE_IID", default="local") }}'

Older version in new Ansible returns empty string even when the variables is not defined.

Nice

Automating UFW Configuration with Ansible: Locking Down the Digital Fortress #Ansible #UFW #Firewall #Automation #Cybersecurity #ServerSecurity #DeadSwitch #OperationalSecurity #AnsiblePlaybook #NetworkSecurity #AutomationTools #AnsibleRoles #SystemAdministration #SecureServer #Encryption #AnsibleVault #PrivacyTools #SecurityAutomation

http://tomsitcafe.com/2025/04/16/automating-ufw-configuration-with-ansible-locking-down-the-digital-fortress/

EspritsCollaboratifs, la boite où je bosse, recrute une ou un adminSys en CDI, à Fontenay-sous-Bois dans l'est parisien, ou en télétravail : https://www.curebot.fr/recrutements/#jobs

Ansible Automation Platform 2.5: Zeit für den Umstieg!
Red Hat sagt endgültig Adieu zur rpm-Installation. In unserem Blogpost zeigen wir, wie du AAP 2.5 sauber containerisiert installierst – inkl. Platform Gateway und Ein-Server-Setup.
https://www.puzzle.ch/blog/2025/04/14/migrating-to-ansible-automation-platform-2-5

Wir begleiten dich seit den Tower-Tagen – von der Migration bis zum Betrieb auf OpenShift.
#Ansible #AutomationPlatform #InfrastructureAsCode

"However, since there has been no announcement from Red Hat regarding the deployment methods that are expected to be supported in the new [#ansible #AWX] release (I haven't received answers to my questions...), I can't make any promises at this point."

https://github.com/kurokobo/awx-on-k3s/issues/413#issuecomment-2804454871

The latest edition of the #Ansible Bullhorn is out, with an important introduction to changes coming in ansible-core that can impact both users and collection/content creators! Please read it and test your Ansible content to ensure it is compatible with these changes.
https://forum.ansible.com/t/the-bullhorn-181/41718

Today, #IPv6 to the rescue.

I broke DHCP for the legacy IP space on my pfSense router today but thanks to running dual stack I could reconnect using the IPv6 address and fix things. I was trying to move to using #Ansible for managing pfSense and somehow despite getting zero errors and Ansible reporting things as idempotent, things were unhappy.

I managed to get back into the router and deleted the new records, recreating them manually and everything is working again. No clue what I broke yet, but yay for IPv6.

Something I haven’t thought about in a while is #ansible and now I’m curious how the changes to the #python #gil being able to be disabled would effect threading.

Dear #Ansible #Kubernetes users,

I can tell Ansible to wait until a Kubernetes pod is running and ready using something like this:

- kubernetes.core.k8s_info:
api_version: v1
kind: Pod
namespace: gitlab
label_selectors:
- app=webservice
wait_condition:
status: "True"
type: Ready
wait: true
wait_sleep: 10
wait_timeout: 1800

However, I do not succeed in telling Ansible to wait until a pod was completed successfully. The following code works but detects a pod that is not yet running (PodInitializing) as well and proceeds.

- kubernetes.core.k8s_info:
[...]
wait_condition:
# no "reason" given here
status: "False"
type: Ready
[...]

As soon as I add a "reason" this task runs into a timeout and does no longer work. No matter what I use as the "reason". "Completed", "Succeeded", "Terminated", ...

The module documentation is rather vague on this...

https://docs.ansible.com/ansible/latest/collections/kubernetes/core/k8s_info_module.html