det.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon Server des Unterhaltungsfernsehen Ehrenfeld zum dezentralen Diskurs.

Administered by:

Server stats:

2.3K
active users

#ansible

13 posts12 participants0 posts today

I have this cunning plan, @feld may be able to sanity check this one for me.

I have accumulated a few not-on-disk ssh-keys (see my recent posts about Secretive and Yubikeys).

I do have a configuration script (#ansible) which sends out all my ssh-keys to the hosts. I do not have faith that it will not override local changes not committed to ansible. I may lose local changes/access.

My idea: deploy my not-on-disk public ssh keys to ~/.ssh/authorized_keys2 - that file is currently not in use.

"The new Data Tagging feature expands provenance tracking on variables to nearly every source. This allows for much more descriptive error messaging, as the entire chain of execution can be consulted to include contextual information about what was happening when an error occurred- in many cases including display of the offending source lines with column markers.

#ansible #wip

github.com/nitzmahone/ansible-

github.com/ansible/ansible/pul

Ansible community documentation. Contribute to nitzmahone/ansible-documentation development by creating an account on GitHub.
GitHubansible-documentation/docs/docsite/rst/porting_guides/porting_guide_core_2.19.rst at core_data_tagging · nitzmahone/ansible-documentationAnsible community documentation. Contribute to nitzmahone/ansible-documentation development by creating an account on GitHub.

Hello, hachyderm! we've been working hard on building up our ansible runbooks and improving hachyderm's overall resilience. Recently, we've been focusing on is database resilience.

We're getting close to retiring our original database server (finally!) and preparing to move to a fully ansible-managed set of databases servers, primary and replica on new hardware. We'll send another announcement when we do the cut over. The team has done excellent work to make this highly automated, quick, and painless! :blobfoxscience:

Done:

✅ author ansible roles for managing postgresql, pgbackrest (backups), pgbouncer, and primary/replica failover
✅ decide to continue with pgbouncer and *not* use pgcat
✅ rotate database passwords
✅ order new replica database hardware
✅ order new future primary database hardware

To do soon:

🟨 rebuild replica database with ansible scripts
🟨 prepare primary database with ansible scripts
🟨 start replicating to new database replica
🟨 cut over to new database server 🎉

We're also planning on open-sourcing our ansible roles in the coming weeks - just a little housekeeping & tidying up before we do!

#Ansible's decision to use Jinja in values only, and not render the YAML itself through Jinja (like Salt does) might make some things a bit more clean, but it also makes a _lot_ of things significantly more difficult. 😩