salt/ansible
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
A series of Ansible scripts to manage my infrastructure.
1,792 Commits 3 Branches 0 Tags 4.6 MiB
Jinja 58.6%
Shell 41.4%
0bfcd5ea2b
Go to file
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
.templates Fix template 2020-10-17 00:27:46 -05:00
contrib Move requirements.yml to root 2021-08-01 21:39:36 -05:00
handlers Move handlers to global handlers 2020-12-20 05:02:17 -06:00
inventory Filter decoms out of the inventory 2022-02-23 16:31:08 -06:00
inventory-hard Overhaul DNS names for machines 2021-10-15 19:03:55 -05:00
playbooks Remove Scanner configuration 2022-02-23 16:02:33 -06:00
roles Have Nagios ignore decom hosts 2022-02-23 16:44:42 -06:00
.ansible-lint Reconfigure lint 2021-09-24 21:11:03 -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 Remove the debug flags on the home play 2022-02-15 17:12:44 -06: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 Spin off more forks during execution to increase run speed 2022-02-15 15:09:21 -06:00
pull.yml Create dedicated ansible-pull playbook with basic maintenance tasks, use it 2021-09-22 07:43:28 -05:00
README.md More readme polish 2021-10-27 20:51:40 -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 Add ZT management-only network 2022-02-13 11:05:25 -06:00

README.md

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.