Salt 0bfcd5ea2b Have Nagios ignore decom hosts
For HOSTS, mind. Services are still gonna need some love
Might honestly just have this operate off of host vars instead, lower the number of lookups, yaknow?
2022-02-23 16:44:42 -06:00
2020-10-17 00:27:46 -05:00
2021-08-01 21:39:36 -05:00
2020-12-20 05:02:17 -06:00
2022-02-23 16:02:33 -06:00
2022-02-23 16:44:42 -06:00
2021-09-24 21:11:03 -05:00
2021-10-27 20:51:40 -05:00
2021-09-14 19:06:46 -05:00
2022-02-13 11:05:25 -06:00

Salt's Ansible Repository

Useful for management across all of 9iron, thefuck, and desu.

Initialization

  • Clone
  • ansible-galaxy install -r requirements.yml

For quick bootstrapping of tools and libraries used in this repo, see rehashedsalt/ansible-env. I use that exact image for CI/CD.

Deployment

Linux Machines

Each Linux machine will require the following to be fulfilled for Ansible to access it:

  • The server has a user named ansible which:

    • Accepts the public key located in contrib/desu.pub; and

    • Has passwordless sudo capabilities as root

  • The server is running Ubuntu 20.04 or greater

To automate these host-local steps, use the script file contrib/bootstrap.sh.

Windows Machines

lol don't

All Machines

Adding a new server will require these:

  • The server is accessible from the Ansible host;

  • The server has been added to NetBox OR in inventory-hard

  • DNS records for the machine are set; and

From there, running the playbook site.yml should get the machine up to snuff.

Zerotier

A lot of my home-network side of things is connected together via ZeroTier; initial deployment/repairs may require specifying an ansible_host for the inventory item in question to connect to it locally. Subsequent plays will require connectivity to my home ZeroTier network.

Cloud-managed devices require no such workarounds.

Description
A series of Ansible scripts to manage my infrastructure.
Readme 5 MiB
Languages
Jinja 59.9%
Shell 40.1%