For all the RHEL to Debian refugees, here are some Ansible roles. I made the jump when they killed CentOS:

https://github.com/liv-io/ansible-roles-debian

Luckily, it did not happen to me. I manage the "timezone" by default.

For anyone interested, I manage around 20+ Proxmox machines with these Ansible roles:

https://github.com/liv-io/ansible-roles-debian

Example playbook:

https://github.com/liv-io/ansible-playbooks-example/blob/mas...

This might help you on your start:

https://github.com/liv-io/ansible-roles-bsd

Looks like a nice resource, many thanks!

Seems like some folks are considering to create an alternative:

https://blog.centos.org/2020/12/future-is-centos-stream/#com...

https://join.slack.com/t/hpcng/shared_invite/zt-gy0st6mt-ijg...

Good luck, as it ain't that easy. Remember Whitebox Linux?

I'd recommend you to use Unbound and specify the named.root or (root.hints) file:

https://www.internic.net/domain/named.root

This Ansible role takes care of configuring it all (CentOS):

https://github.com/liv-io/ansible-roles-centos/tree/master/u...

I have it for FreeBSD and OpenBSD too:

https://github.com/liv-io/ansible-roles-bsd/tree/master/unbo...

Or have it all automated using Ansible: https://github.com/liv-io/ansible-roles-bsd

Including Prometheus monitoring and Loki logging (on Linux though and work in progress)

Thanks for that! I rolled my own ansible roles for my openbsd router.... will take a look.

Your response made me smile. Glad to see there are still reasonable folks out there. Working for a startup without a "resume-driven-development" CTO gave me the freedom to go "servermore" architecture with max flexibility.

For all the talk about resume driven development, I am hiring now, and will say that people who have solved their problems by learning more about Linux and such sound way more impressive than those who list out passing familiarity with a bunch of high level services. The first style of resume really stands out. The second is a dime a dozen.

To make an analogy, it's like hiring a carpenter based on the number of tools they have. NO. Show me your skill with a hammer and chisel, and I'll assume you can figure out the rest.

This could have been written by me. And for who ever doesn't have time to maintain roles, there is Ansible Galaxy or tons of roles in GitHub, including mine: https://github.com/liv-io

Arecibo? Makes me want to listen to Carbon Based Lifeforms: https://www.youtube.com/watch?v=ifiICunJ-ZA

@0xC45: as a fellow OpenBSD user you might find my Ansible roles useful.

I also run OpenBSD HA firewall clusters with trunking (aggr), VLANs at home and work:

- https://github.com/liv-io/ansible-roles-bsd/tree/master/host... # interface configuration

- https://github.com/liv-io/ansible-roles-bsd/tree/master/open... # firewall configuration

I've created an extended example for the firewall configuration: https://github.com/liv-io/ansible-playbooks-example/blob/mas...

https://github.com/liv-io/ansible-playbooks-example/blob/mas...