glusterfs setup on c1:
  * for h in c1 c2 c3; do ssh $h sudo mkdir /persist/glusterfs/compute; done
  * gluster peer probe c2
  * gluster peer probe c3
  * gluster volume create compute replica 3 c{1,2,3}:/persist/glusterfs/compute/brick1
  * gluster volume start compute
  * gluster volume bitrot compute enable

mysql credentials
  * Put secrets/mysql_root_password into a Nomad var named secrets/mysql.root_password

postgres credentials
  * Put secrets/postgres_password into a Nomad var named secrets/postgresql.postgres_password

adding a new gluster node to the compute volume, with c3 having failed:
(instructions from https://icicimov.github.io/blog/high-availability/Replacing-GlusterFS-failed-node/)
  * zippy: sudo mkdir /persist/glusterfs/compute -p
  * c1: gluster peer probe 192.168.1.2 (by IP because zippy resolved to a tailscale address)
  * c1: gluster volume replace-brick compute c3:/persist/glusterfs/compute/brick1 192.168.1.2:/persist/glusterfs/compute/brick1 commit force
  * c1: gluster volume heal compute full
  * c1: gluster peer detach c3

same to then later replace 192.168.1.2 with 192.168.1.73

replacing failed / reinstalled gluster volume (c1 in this case). all commands on c2:
  * gluster volume remove-brick compute replica 2 c1:/persist/glusterfs/compute/brick1 force
  * gluster peer detach c1
  * gluster peer probe 192.168.1.71 (not c1 because switching to IPs to avoid DNS/tailscale issues)
  * gluster volume add-brick compute replica 3 192.168.1.71:/persist/glusterfs/compute/brick1