salt/ansible
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
A series of Ansible scripts to manage my infrastructure.
1,282 Commits 4 Branches 0 Tags 4.9 MiB
Jinja 59.9%
Shell 40.1%
7a98174297
Go to file
Salt 7a98174297 Do not recursively own Ansible user home 
This works around a bug with a recursive symlink in the sshd role. With that symlink, ansible-pull fails as it recurses through its own repo infinitely.
2021-03-11 09:19:55 -06:00
.templates Fix template 2020-10-17 00:27:46 -05:00
contrib Working on basics 2020-10-17 00:21:57 -05:00
handlers Move handlers to global handlers 2020-12-20 05:02:17 -06:00
inventory Add netbox DB 2021-03-10 13:29:59 -06:00
inventory-localhost Add k8s configuration scripts 2021-02-28 23:33:31 -06:00
playbooks Allow DB Pi to listen on ZT 2021-03-11 09:11:48 -06:00
roles Do not recursively own Ansible user home 2021-03-11 09:19:55 -06:00
.gitignore Add gitignore entry for cache 2021-02-11 13:16:21 -06:00
.gitmodules Move fedi1 over, add Pleroma role 2021-01-25 22:19:31 -06:00
ansible.cfg Working on basics 2020-10-17 00:21:57 -05:00
README.md Add note to README about zt 2021-02-19 02:15:43 -06:00
reboot-home.yml Add pi-storage-1 to reboot script 2021-02-26 09:22:27 -06:00
reboot-prod.yml Rework reboot scripts 2021-02-23 04:11:07 -06:00
site.yml Add SSHD role, tighten things down 2021-03-11 08:04:57 -06:00

README.md

Salt's Ansible Repository

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

TODO

  • Figure out a good monitoring solution that doesn't suck ass

  • Port over configs for Nextcloud on web1.9iron.club

Initialization

Clone the repo, cd in. Done.

Deployment

Adding a new server will require the following be fulfilled:

  • The server is accessible from the Ansible host;

  • 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 added to inventory/hosts.yml in an appropriate place;

  • DNS records for the machine are set; and

  • The server is running Ubuntu 20.04 or greater

From there, running the playbook site.yml should get the machine up to snuff. To automate the host-local steps, use the script file contrib/bootstrap.sh.

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.

Ad-Hoc Commands

The inventory is configured to allow for ad-hoc commands with very little fuss. For example:

ansible -m shell -a 'systemctl is-failed ansible-pull.service' all

These commands must be run from the root of the repo.

Ansible Galaxy

Several of the roles in this repository are sourced from Ansible Galaxy. They're mirrored here for both easy compatibility with ansible-pull and in case the sources go down. Despite this, they're still managed in roles/requirements.yml for ease of management, source tracking, and updating. Any forks or deviations from these sources should be thoroughly documented.

Should you need to reinitialize them, the following command (run from the root of the repo) will initialize all Galaxy assets:

ansible-galaxy install -r roles/requirements.yml