em/ansible-void
1
0
Fork 0
mirror of https://github.com/gjkcz/ansible-void.git synced 2024-11-01 00:45:59 +01:00
Code Issues Releases Activity
Ansible files for managing classroom machines at GJK.
4 Commits 1 Branch 0 Tags 3 MiB
Shell 100%
b39bc3b0b1
Go to file
Emil Miler b39bc3b0b1 Simpler service handling
2023-05-01 18:18:57 +02:00
files Add sound support with PipeWire 2023-05-01 18:15:29 +02:00
group_vars Initial commit 2023-04-29 19:51:14 +02:00
ansible.cfg Initial commit 2023-04-29 19:51:14 +02:00
hosts Initial commit 2023-04-29 19:51:14 +02:00
readme.md Add readme 2023-04-29 21:03:43 +02:00
reboot.yaml Initial commit 2023-04-29 19:51:14 +02:00
setup.yaml Simpler service handling 2023-05-01 18:18:57 +02:00
shudown.yaml Initial commit 2023-04-29 19:51:14 +02:00

readme.md

Ansible files for managing classroom machines at GJK.

There are two classrooms, POV and POM. All machines are running Void Linux with Gnome in dual-boot with Windows.

GDM configuration can be found at https://help.gnome.org/admin/system-admin-guide/stable/index.html.en.

New client installation

There are several differences in the hardware. System installation is usually done in EFI, though MBR still exists on older machines in POV.

  • Install Void
  • Update xbps
  • Install python3
  • Import your SSH key to /root/.ssh/authorized_keys

Void has sshd enabled by default as well as having prohibit-password set for root. Post-installation setup can be automated using a script or USB keyboard injector.

Running a playbook

ansible-playbook setup.yaml
ansible-playbook -l teachers setup.yaml
ansible-playbook --key-file ~/.ssh/keys/gjk-ansible setup.yaml

SSH configuration

You should setup your ssh to avoid unnecessary settings when running a playbook, for example:

Host VU* MU*
	User root
	IdentityFile ~/.ssh/keys/gjk-ansible
	StrictHostKeyChecking no
	UserKnownHostsFile=/dev/null