Are you in #tech and running your own #Fediverse instance? You might want to join an Activity Pub relay instance!

My relay at https://fedi-relay.gyptazy.com has currently 139 instances connected, mostly tech related sharing the same mindset and interests like #Linux, #BSD, #Ansible, #Proxmox, #Coding, and many more! You can easily join from your instance when using #Pleroma, #snac ( #snac2), #Mastodon and its forks 🙂

#fedi #fediworld #fedicommunity #community #FreeBSD #OpenBSD #NetBSD #homelab #Python #Debian #RockyLinux #Feditips

Are you in #tech and running your own #Fediverse instance? You might want to join an Activity Pub relay instance!

My relay at https://fedi-relay.gyptazy.com has currently 139 instances connected, mostly tech related sharing the same mindset and interests like #Linux, #BSD, #Ansible, #Proxmox, #Coding, and many more! You can easily join from your instance when using #Pleroma, #snac ( #snac2), #Mastodon and its forks 🙂

#fedi #fediworld #fedicommunity #community #FreeBSD #OpenBSD #NetBSD #homelab #Python #Debian #RockyLinux #Feditips

Big production migration finished last night, closing out 2 months of very fiddly well-tested Ops work, to move a critical business service off an ephemeral IP onto a new resilient load balanced setup with no single point of failure.

Thanks to #haproxy, #freebsd, and #ansible, nobody noticed except my 2 colleagues and me, as we baby-sat the production changes, and didn’t lose a single customer request in the process.

#sysAdmin #Niche #Ansible #Debian
Utiliser des paquetages de Debian unstable via Ansible : https://www.bortzmeyer.org/ansible-debian-unstable.html

I think the hardest thing for me to convey to students learning #ansible is one of the points in the Ansible best practices document:

"Generous use of whitespace to break things up, and use of comments (which start with ‘#’), is encouraged."

I even explain that the use of the large key on the keyboard with which an empty line is created is almost free of charge to use!

I think the hardest thing for me to convey to students learning #ansible is one of the points in the Ansible best practices document:

"Generous use of whitespace to break things up, and use of comments (which start with ‘#’), is encouraged."

I even explain that the use of the large key on the keyboard with which an empty line is created is almost free of charge to use!

#sysAdmin
Tiens, #Ansible (plus exactement son module apt), quand on lui demande d'installer un paquetage Debian, met par défaut qu'il veut uniquement la version stable (même si on a unstable, avec une faible priorité, dans la liste des sources).

Hey #Proxmox community! I would like to hear your thoughts on how you usually update your Proxmox nodes and clusters. How do you handle minor Proxmox and #Debian package upgrades with #APT?

What would you think about a new API endpoint that lets you run unattended upgrades with a simple call like:

/nodes/{node_name}/apt/upgrade

At the moment you need to use the node’s HTML5 console to perform upgrades. Other methods exist such as running unattended Debian upgrade scripts, using patch management tools like #Spacewalk or #QualvoSec, or automating the process with #Ansible over SSH. My idea is to have an API based solution that relies on Proxmox authentication and authorization. This would also allow third party tools such as #ProxLB to provide automated patch management and even handle guest rebalancing in a way that is similar to DRS without requiring direct SSH access.
I have already been running this approach on several internal clusters since the release of PVE 8 without issues. Now I am interested to hear if you would use unattended upgrades in general or if you are already running them today.

#Linux #OpenSource #PatchManagement #Security #DevOps #Automation #Ansible #PVE #PVE8 #PVE9

Hey #Proxmox community! I would like to hear your thoughts on how you usually update your Proxmox nodes and clusters. How do you handle minor Proxmox and #Debian package upgrades with #APT?

What would you think about a new API endpoint that lets you run unattended upgrades with a simple call like:

/nodes/{node_name}/apt/upgrade

At the moment you need to use the node’s HTML5 console to perform upgrades. Other methods exist such as running unattended Debian upgrade scripts, using patch management tools like #Spacewalk or #QualvoSec, or automating the process with #Ansible over SSH. My idea is to have an API based solution that relies on Proxmox authentication and authorization. This would also allow third party tools such as #ProxLB to provide automated patch management and even handle guest rebalancing in a way that is similar to DRS without requiring direct SSH access.
I have already been running this approach on several internal clusters since the release of PVE 8 without issues. Now I am interested to hear if you would use unattended upgrades in general or if you are already running them today.

#Linux #OpenSource #PatchManagement #Security #DevOps #Automation #Ansible #PVE #PVE8 #PVE9

A new BSDCan video has been posted:
Automating My FreeBSD Lab: From Setup to Daily Use with Ansible & Salt by Roller Angel
Automating My FreeBSD Lab: From Setup to Daily Use with Ansible & Salt
Abstract

https://youtu.be/yX0p_M8eykc

Managing multiple FreeBSD machines can be time-consuming, but automation makes it effortless. In this talk, I will demonstrate how I use Ansible to set up my FreeBSD lab and Salt to maintain and scale it across multiple machines—including how I configured a second FreeBSD laptop with just SSH access.

Attendees will see how automation enables:

Seamless FreeBSD system setup using Ansible.

Automated configuration management with Salt.

Effortless scaling to new machines, reducing manual setup to a few commands.

By the end of the talk, attendees will understand how to leverage Ansible and Salt to build a reproducible and maintainable FreeBSD infrastructure.
Intended Audience

FreeBSD users interested in automating system setup and maintenance.

System administrators managing multiple FreeBSD machines.

Anyone curious about Ansible and Salt for FreeBSD automation.

Attendees should have basic FreeBSD knowledge, but no prior experience with automation tools is required.

For more information, please visit:
https://www.bsdcan.org/2025/
- and -
https://www.bsdcan.org/2025/timetable/timetable-Automating-My-FreeBSD.html

#runbsd #freebsd #ansible

A new BSDCan video has been posted:
Automating My FreeBSD Lab: From Setup to Daily Use with Ansible & Salt by Roller Angel
Automating My FreeBSD Lab: From Setup to Daily Use with Ansible & Salt
Abstract

https://youtu.be/yX0p_M8eykc

Managing multiple FreeBSD machines can be time-consuming, but automation makes it effortless. In this talk, I will demonstrate how I use Ansible to set up my FreeBSD lab and Salt to maintain and scale it across multiple machines—including how I configured a second FreeBSD laptop with just SSH access.

Attendees will see how automation enables:

Seamless FreeBSD system setup using Ansible.

Automated configuration management with Salt.

Effortless scaling to new machines, reducing manual setup to a few commands.

By the end of the talk, attendees will understand how to leverage Ansible and Salt to build a reproducible and maintainable FreeBSD infrastructure.
Intended Audience

FreeBSD users interested in automating system setup and maintenance.

System administrators managing multiple FreeBSD machines.

Anyone curious about Ansible and Salt for FreeBSD automation.

Attendees should have basic FreeBSD knowledge, but no prior experience with automation tools is required.

For more information, please visit:
https://www.bsdcan.org/2025/
- and -
https://www.bsdcan.org/2025/timetable/timetable-Automating-My-FreeBSD.html

#runbsd #freebsd #ansible

I switch all of my domains and other public resources to being managed by Terraform. But because I'm a filthy pervert I've decided to manage Terraform with Ansible.

# Terraform #Ansible#Selfhosting

https://github.com/awfulwoman/infra/tree/main/ansible/roles/infra-public-resources

This summer I got to teach an #ansible workshop. I decided to write on getting set up for it, because it went pretty sideways at the beginning but ended up working out perfectly well.

My #SmartOS Live Demo Failure, and Success

https://blog.passwordclass.xyz/posts/2025-08-21-my-smartos-live-demo-failure-and-success/

This summer I got to teach an #ansible workshop. I decided to write on getting set up for it, because it went pretty sideways at the beginning but ended up working out perfectly well.

My #SmartOS Live Demo Failure, and Success

https://blog.passwordclass.xyz/posts/2025-08-21-my-smartos-live-demo-failure-and-success/

And a short blog pot about it :)

#proxmox #ansible #devops #automation #storage #nfs #iscsi #pbs #cifs #smb #cephfs #development

https://gyptazy.com/introducing-storage-management-for-proxmox-nodes-clusters-with-the-new-ansible-module-proxmox_storage/

And a short blog pot about it :)

#proxmox #ansible #devops #automation #storage #nfs #iscsi #pbs #cifs #smb #cephfs #development

https://gyptazy.com/introducing-storage-management-for-proxmox-nodes-clusters-with-the-new-ansible-module-proxmox_storage/

It just got merged… You can now easily manage storage in #Proxmox with #Ansible.

Simply add CephFS, NFS, iSCSI or Proxmox Backup Server to your cluster with a simple Ansible task :)

#proxmox #proxmoxve #ansible #opensource #contributing #foss #automation #devops

https://github.com/ansible-collections/community.proxmox/commit/c5d6adafe1f74befb0dc4d61c5a7cf92491272bf

It just got merged… You can now easily manage storage in #Proxmox with #Ansible.

Simply add CephFS, NFS, iSCSI or Proxmox Backup Server to your cluster with a simple Ansible task :)

#proxmox #proxmoxve #ansible #opensource #contributing #foss #automation #devops

https://github.com/ansible-collections/community.proxmox/commit/c5d6adafe1f74befb0dc4d61c5a7cf92491272bf

Just reworked my #Debian #ansible desktop playbook and adapted it for #Debian 13 Trixie.
Pretty smooth sailing overall 😎

https://github.com/jhx0/debian-desktop-playbook