ansible/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:

```bash
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
```
Working on basics 2020-10-17 00:21:57 -05:00			`# Salt's Ansible Repository`

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

Add introspective TODO 2020-11-01 05:00:27 -06:00			`## TODO`

Get rid of Netdata Christ this thing is awful 2021-02-11 13:16:36 -06:00			`* Figure out a good monitoring solution that doesn't suck ass`
Add introspective TODO 2020-11-01 05:00:27 -06:00
Update README 2021-01-18 06:58:45 -06:00			`* Port over configs for Nextcloud on web1.9iron.club`

Add init instructions to README 2020-10-28 22:42:11 -05:00			`## Initialization`

Update README 2020-11-07 00:47:18 -06:00			Clone the repo, `cd` in. Done.
Add init instructions to README 2020-10-28 22:42:11 -05:00
Working on basics 2020-10-17 00:21:57 -05:00			`## 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`

Mandate that DNS be set up as part of machine deployment Machines should NOT have the ability to modify DNS of their own volition. Like wtf past me 2020-10-17 01:19:55 -05:00			* The server is added to `inventory/hosts.yml` in an appropriate place;

			`* DNS records for the machine are set; and`
Working on basics 2020-10-17 00:21:57 -05:00
Correct OS requirements in README The only dependency is python-is-python3 2020-12-28 12:58:07 -06:00			`* The server is running Ubuntu 20.04 or greater`
Working on basics 2020-10-17 00:21:57 -05:00
			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`.
Update README 2020-11-07 00:47:18 -06:00
Add note to README about zt 2021-02-19 02:15:43 -06:00			`## 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.`

Add note in README about ad-hoc commands Just because I keep forgetting the syntax lol 2021-01-22 21:14:17 -06:00			`## Ad-Hoc Commands`

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

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

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

Update README 2020-11-07 00:47:18 -06:00			`## 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`
			```