A series of Ansible scripts to manage my infrastructure.
Go to file
Jacob Babor 44c96b0442 Rework zerotier role to prevent installing zerotier just for it to do nothing at all
This also neatly avoids things like rpm-ostree-based distros where i install zerotier in a container
2022-08-28 12:01:37 -05:00
.templates Fix template 2020-10-17 00:27:46 -05:00
contrib Remove old docker script 2022-06-23 16:37:55 -05:00
handlers Make the FQCN warning happy again 2022-06-16 23:45:29 -05:00
inventories Use an external DB for Gitlab 2022-08-04 18:31:08 -05:00
playbooks Avoid running our sshd role against rpm-ostree distros 2022-08-28 11:46:35 -05:00
roles Rework zerotier role to prevent installing zerotier just for it to do nothing at all 2022-08-28 12:01:37 -05:00
.ansible-lint Disable linting for command-instead-of-module, I need the extra functionality 2022-06-16 23:45:22 -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 a well-known vault password file location 2022-07-23 18:04:15 -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 Use a well-known vault password file location 2022-07-23 18:04:15 -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
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.