A series of Ansible scripts to manage my infrastructure.
Go to file
Salt 3701ed678f Repoint Octoprint to the wlan0 interface of the pi
This is so we don't have to wait for ZT to start up every time the pi flips its shit
2022-05-19 17:31:24 -05:00
.templates Fix template 2020-10-17 00:27:46 -05:00
contrib Add a little contrib script to set up ara 2022-04-23 11:23:36 -05:00
handlers Move handlers to global handlers 2020-12-20 05:02:17 -06:00
inventories Adjust Zerotier repo settings for Ubuntu 22.04 2022-05-10 06:22:05 -05:00
playbooks Repoint Octoprint to the wlan0 interface of the pi 2022-05-19 17:31:24 -05:00
roles Add some fancy schmancy unicode to our monitoring alert scripts 2022-05-02 15:46:41 -05:00
.ansible-lint Add some more exceptions to the linter 2022-03-24 11:57:26 -05:00
.gitignore Install Galaxy roles to their own directory so I don't have to maintain a long gitignore 2021-09-18 16:13:20 -05:00
.gitlab-ci.yml Use ara during gitlab ci plays 2022-04-23 11:10:49 -05:00
.gitmodules Add checks for the R720's thermal monitors, also add those thermal monitors 2022-01-10 22:14:07 -06:00
ansible.cfg Remove unparsed_is_failed from ansible.cfg 2022-04-29 16:50:10 -05:00
pull.yml Create dedicated ansible-pull playbook with basic maintenance tasks, use it 2021-09-22 07:43:28 -05:00
README.md Add a little contrib script to set up ara 2022-04-23 11:23:36 -05:00
reboot-home.yml Reconfigure reboot-home.yml 2021-09-14 19:06:46 -05:00
reboot-prod.yml Polish up those reboot playbooks 2021-08-25 12:20:47 -05:00
requirements.yml Add avahi to the management network 2022-02-13 13:03:41 -06:00
site.yml Revert a ton of the changes I just made because they were based on a false premise 2022-04-18 11:44:42 -05: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.

I use ara to record Ansible plays. If your environment has it installed, source the script in contrib/ara.sh to configure your environment properly.

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.