101010.pl is one of the many independent Mastodon servers you can use to participate in the fediverse.
101010.pl czyli najstarszy polski serwer Mastodon. Posiadamy wpisy do 2048 znaków.

Server stats:

481
active users

#ansible

6 posts6 participants0 posts today

I've just published version 25.7.1 of 'kpfleming.systemd_networkd', my collection of Ansible roles for managing systemd-networkd configuration. New in this release are a half-dozen 'advanced' features in the 'network' role, along with a new 'bridge' role. Most of these changes originated from my recent project to switch to DHCPv6-PD on my home network, and also eliminate the standalone DHCPv4 servers I was using.

If you're an Ansible user and use systemd-networkd on your managed machines, take a look! Here's an example of a moderately-complex configuration:

github.com/kpfleming/ansible-s

I've got more complex ones if you're really interested 🙂

#Ansible #systemd #networking #systemd-networkd

A collection of Ansible roles for managing the configuration of systemd-networkd. - kpfleming/ansible-systemd-networkd
GitHubGitHub - kpfleming/ansible-systemd-networkd: A collection of Ansible roles for managing the configuration of systemd-networkd.A collection of Ansible roles for managing the configuration of systemd-networkd. - kpfleming/ansible-systemd-networkd

i want to play with something like woodpecker at some point, but now i have made some progress with the existing setup:

* the nvchecker triggerscript (checks for new releases):
* posts to vikunja now (mail+applescript+omnifocus too fragile)
* checks if the updated app is configured as playbook
* runs the matching playbook
* from post_tasks, a conditional webhook is triggered using ansible_play_hosts/ansible_play_hosts_all:
#ansible

#Linux #hivemind

TL;DR: How would you deploy a maintainable Linux build to 14 PCs?

I have a lab network of 14 PCs at $dayjob. I want them all to have the same Linux build/image, with the same apps - (probably) Plasma, VirtualBox, LibreOffice, Packet Tracer (so JRE as well) as the basics, plus various other tools.

If the users mess up the machine somehow, they need to be easily re-imaged. It would be nice if /home could optionally be preserved, but not essential.

I am currently the most Linux-savvy person in the team that will be looking after these PCs. I'm not there all the time, so this needs to be maintainable by techies who don't daily drive Arch.

I know #Ansible could be a good option, meaning I have some flexibility with which distro. (I am open to different distros for this.) #Nix or #NixOS could also work, but the learning curve for that could be pretty steep (for me - steeper for the rest of the team), plus its non-standard approach to Linux might be confusing for some.

I guess some solution using a PXE boot and then an auto-deployed script or definition file?

Hey #GetFediHired,
After some layoffs in my current company, I am looking for some #softwaredevelopment job, #remote only. I can work in the #EU or would be able to travel some weeks during the year.

I am fluent in #PHP, #Symfony, #Golang, #gRPC, #REST and #GraphQL #API, #Docker, #Ansible, Event Streaming and modern software development in general with experience of over 15 years in various roles - from senior engineer to CTO. I value good software architecture, tests, documentation in combination with valuable communication and discussions.

Find my CV here: codedge.de/cv

If that sounds like something, drop me a message or reply. Cheers!

code and society | codedgeCV
More from tH

First release:

I wrote an Ansible :ansible: connection-plugin to automate FreeBSD Jails :freebsd: via their host, by utilizing jls and jexec to run automation via a SSH connection to the FreeBSD host.

I released that on GitHub github.com/chofstede/ansible_j
And on my Codeberg: codeberg.org/Larvitz/ansible_j

Released under a BSD license.

This enables seamless automation of FreeBSD jails without needing a SSH connection to the Jails themselves.

Jemand der mir einen Tipp bezüglich #Ansible geben kann ich stehe gerade echt auf dem Schlauch.
Ich habe ein Modul gebaut das host facts ermittelt das funktioniert auch:
ansible -m myfacts hostname
Aber wie kann ich die neuen facts jetzt innerhalb meiner role nutzen?

Das hier zeigt sie nämlich nicht an:
- gather_facts:
fact_path: ./library/myfacts.py
- name: print facts
debug:
msg: "{{ ansible_facts }}"