On one of the terminals I use (Blink on iOS) I can't discern yellow on white, which is why I configure this in #Ansible
export ANSIBLE_COLOR_CHANGED="dark gray"
It looks a bit unusual because it's not yellow, but it helps me.
On one of the terminals I use (Blink on iOS) I can't discern yellow on white, which is why I configure this in #Ansible
export ANSIBLE_COLOR_CHANGED="dark gray"
It looks a bit unusual because it's not yellow, but it helps me.
Hi all. I'm hating to be writing this post, but here we are.
A little while ago, I was laid off from my SRE job at a government contractor.
If anyone is looking for an SRE with:
- #Linux experience (a lot)
- #BSD experience (some)
- Plan 9 and Haiku experience (a little)
- Experience with a large #Ansible codebase
- Experience managing thousands of servers
- Experience with bare metal and VM management
and who isn't afraid of code - I'm your person!
I try to live my life by moving slow and fixing things - I'd be especially interested in roles around labor organization, #climate action or with a socially conscious #coop if anyone from those communities is looking.
Boosts welcome!
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)
OK, I managed to improve lots of things in those setups and make the setup more reliable (even in case it takes really really long for everything to be up).
https://codeberg.org/johanneskastl/gitlab_on_k3s_vagrant_libvirt_ansible
Now with four branches, one for Gitlab installed via helm chart and one using the Gitlab Operator.
And each of them with and without a Gitlab Runner being installed into the cluster.
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
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.
EDIT: To be fair, I have been asked for examples, so here is at least one (I could list a few more, but no need).
https://bitwarden.com/help/ansible-integration/
https://registry.terraform.io/search/providers?q=bitwarden
The #s390x open source software team at IBM confirms the latest versions of various software packages run well on #Linux on #IBMZ & #LinuxONE
In March 2025 validation was maintained for over 30 projects, including #Ansible, #Apache Tomcat, & #Erlang
Plus, community CI was added for segyio, and Rust's linux_syscall project now publishes s390x releases on crates.io
Full report + how your project can apply for a s390x VM: https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/elizabeth-k-joseph1/2025/04/18/linuxone-open-source-report-march-2025
I'm currently also working on the #powerdns (authoritative) podman plugin impelementation and blocky (#DNS caching) because every good home network needs those things.
I also wrote a pretty opinionated CA #Ansible role that automatically creates and deploys server certificates to all my hosts.
I mean when I automate psql I will have to support TLS out of the box as well, right?
Isn't anybody into those things? I love to have another maintainer for my MMN collection.
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?
OK, I found a way that seems to work in all phases:
- the migrations pod is not yet started (PodInitializing)
- the migrations pod is running
- the migrations pod has been Completed
This part waits for the pod to exist (no matter its state):
https://codeberg.org/johanneskastl/gitlab_on_k3s_vagrant_libvirt_ansible/src/branch/main/ansible/playbook-gitlab_installation.yml#L170
This part waits for the pod to be in Completed state:
https://codeberg.org/johanneskastl/gitlab_on_k3s_vagrant_libvirt_ansible/src/branch/main/ansible/playbook-gitlab_installation.yml#L184
I did not use the module's wait functionality as I could not get it to work the way I want. So I used what I often use: Ansble's `until` together with a `json_query` filter.
Crypto.com is hiring DevOps Engineer – DevOps Security
#golang #python #cryptocurrency #ansible #aws #azure #cicd #docker #kubernetes #redis #awss3 #terraform #securityengineer
Shenzhen, China
Full-time
Crypto.com
Job details https://jobsfordevelopers.com/jobs/devops-engineer-devops-security-at-crypto-com-feb-17-2025-9b30e2?utm_source=mastodon.world&utm_medium=social&utm_campaign=posting
#jobalert #jobsearch #hiring
Now that the Debian netboot/preseed is sorted, my next task was to write an Ansible playbook to rebuild the master nodes, doing the careful step of removing the node, removing from etcd, reinstalling, then re-introducing the node.
About 15 minutes in I realised that this task is actually taking longer than if I just ran this by hand. Sometimes you just have to know when to stop. How often is this process going to run? This is why I used to have XKCD 1205 as a printout on my desk.
Fifth and (it really seems) last round for the #NixOS #Ansible bubble:
Thanks to @nebucatnetzer I tried installing ansible "the other way round". Rather than trying to install Ansible and have a customized python3 (with hvac and kubernetes modules etc.) as a "build input" I have tried the other way round: Adding ansible and ansible-core to the python package:
```
(pkgs.python3.withPackages (python-pkgs: [
python-pkgs.ansible
python-pkgs.ansible-core
python-pkgs.hvac
python-pkgs.kubernetes
]))
```
A short test was successful, tasks delegated to localhost found the kubernetes module and could successfully do things! Hooray!
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
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
"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.