mas.to is one of the many independent Mastodon servers you can use to participate in the fediverse.
Hello! mas.to is a fast, up-to-date and fun Mastodon server.

Administered by:

Server stats:

12K
active users

#ansible

32 posts26 participants3 posts today

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?

Continued thread

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):
codeberg.org/johanneskastl/git

This part waits for the pod to be in Completed state:
codeberg.org/johanneskastl/git

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.

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

According to docs.ansible.com/ansible/lates

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.

docs.ansible.comansible.builtin.env lookup – Read the value of environment variables — Ansible Community Documentation

Что такое Ansible и как применяется в DWH-проектах? Сравнение Ansible с Puppet, Chef, SaltStack

В статье рассказываем, что такое Ansible и как инструмент может применяться в проектах DWH: от автоматического развертывания и настройки компонентов до восстановления после сбоев и централизованного управления параметрами. Сравниваем Ansible с другими инструментами для автоматизации управления инфраструктурой: Puppet, Chef, SaltStack.

habr.com/ru/articles/901778/

ХабрЧто такое Ansible и как применяется в DWH-проектах? Сравнение Ansible с Puppet, Chef, SaltStackСегодня бизнес-данные стали основой для принятия управленческих решений, а системы бизнес-аналитики и корпоративные хранилища данных (DWH) — ключевыми компонентами инфраструктуры по работе с данными....

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.

https://xkcd.com/1205/

xkcdIs It Worth the Time?
Continued thread

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!

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.

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

docs.ansible.com/ansible/lates

docs.ansible.comkubernetes.core.k8s_info module – Describe Kubernetes (K8s) objects — Ansible Community Documentation

🔍 Looking for #Linux #Containers for your CI/CD pipeline? #foundata built a collection of OCI images with

✅ functional systemd (not just a shim!)
✅ unprivileged execution support – perfect for tools like #Podman.

👉 Explore all Integration Test Target (ITT) container files on github.com/orgs/foundata/repos

💡 Also ideal for #Ansible #Molecule testing, see them in action with a collection: github.com/foundata/ansible-co