salt/ansible
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
A series of Ansible scripts to manage my infrastructure.
838 Commits 3 Branches 0 Tags 4.6 MiB
Jinja 58.6%
Shell 41.4%
ed64d3a005
Go to file
Salt ed64d3a005 Set GRUB_RECORDFAIL_TIMEOUT 
https://ubuntuforums.org/showthread.php?t=2412153
Apparently this only happens on systems that have:
* UEFI on
* LVM
* Exactly one OS
For some reason, generator scripts will FORCE GRUB to bail to menu with a 30 second fucking timeout in this case
This is like the number one install method, too. What the fuck.
2020-08-25 03:28:04 -05:00
.templates Move template to .templates directory 2020-05-20 12:18:46 -05:00
inventory Add more explicit vars to tes3mp config 2020-08-23 23:30:53 -05:00
playbooks Add TES3MP server 2020-08-23 23:12:39 -05:00
roles Set GRUB_RECORDFAIL_TIMEOUT 2020-08-25 03:28:04 -05:00
.gitignore Remove build directory from gitignore 2020-02-26 18:56:29 -06:00
ansible-pull.cfg Move playbooks to subdir 2020-06-24 06:54:45 -05:00
ansible.cfg Move playbooks to subdir 2020-06-24 06:54:45 -05:00
localhost-deploy.sh Fix closing quote, rename sudoers config 2020-06-16 10:08:12 -05:00
provision.yml Switch to OnCalendar for ansible pull setups 2020-08-11 03:51:15 -05:00
README.md Polish up the README 2020-06-24 06:48:08 -05:00
reboot.yml Reboot machines in a less-destructive order 2020-08-23 01:15:18 -05:00
site.yml Only run influxdb on aws boxes 2020-08-10 06:24:22 -05:00

README.md

Salt's Ansible Scripts

A collection of Ansible scripts to manage all of my machines.

Quickstart

To quickly get a machine up and running, add it to the inventory, role it out, and ./provision.yml it. The playbook assures a sane running environment and then sets up ansible-pull on a timer that immediately triggers. Leave it be, come back 10 minutes later and polish it up as required.

Overview

The main playbook, site.yml, can be separated into more or less two parts:

  • The home machine half, tied together via Zerotier

  • The 9iron half, with public IPs and resolvable names

See inventory/hosts.yml for details on what machines have what roles and what configuration. I try my best to make self-explaning configuration, so everything should mostly make sense on a first read. If you have any questions, hit me up.

Your Roles are Trash

I know. Please file an issue.