FuzzyBot: Importing a new version from external source

2025-03-07T11:14:35Z

Importing a new version from external source

Ny side

Before running the playbook, you need to create a file <code>local-vars.yml</code> (this file is ignored by git) containing values the ansible playbook will use during the setup. Use your favourite editor to create the file, and fill it with the following data:
internet_interface: "eno1" # Interface name that has internet access

# DHCP server configuration
dhcpd_interface: "enx7cc2c6469631" # Interface name for local netboot network
dhcpd_subnet_network: "192.168.100.0" # Network address for local network
dhcpd_subnet_netmask: "255.255.252.0" # Network netmask for local network
dhcpd_pool_start: "192.168.100.50" # DHCP IP pool start address
dhcpd_pool_end: "192.168.103.250" # DHCP IP pool end address
dhcpd_option_routers: "192.168.100.1" # Gateway for local network (your netboot host!)
dhcpd_option_domainnameservers: "1.1.1.1,1.0.0.1" # DNS servers to push to clients
dhcpd_option_nextserver: "192.168.100.1" # Netboot PXE server (your netboot host!)

# Full name, username and cleartext password of your desired non-root
# user to be created during preseed. This is going to be the user that
# is automatically logged in as the kiosk user.
preseed_user_fullname: ""
preseed_username: ""
preseed_user_password: ""

# Username and password that will be configured in ProFTP and that ShredOS will
# use to upload PDF reports # after shredding of disks.
proftpd_shredos_user: "someuser"
proftpd_shredos_pass: "somepass"

# A list of donors of laptops. IMPORTANT: Use only lowercase and uppalphanumeric
# (a-z, A-Z, 0-9), no spaces! Each donor will get their own ShredOS netboot menu
# choice, and their own ShredOS logs directory.
donors:
- "bigcompany"
- "district123"
Now you should be able to run the playbook that will perform all the necessary configuration tasks. This might take a little while.
<code>ansible-playbook netboot-host-setup.yml -D</code>
It's probably a good idea to reboot your netboot host again after this (assuming all went well), to make sure services start at boot (DHCP server, ProFTPd, Apt-cacher-ng). You can check with e.g.:
systemctl status proftpd.service
systemctl status isc-dhcp-server.service
systemctl status apt-cacher-ng.service
You should now be able to use this host in the local network where you are performing the Skolelinux installations. This host should be the only DHCP server in the network, and the gateway IP must match what is being pushed by this host over DHCP.

Translations:Skolelinux-netboot-en-test/15/en - Sideversjonshistorikk

FuzzyBot: Importing a new version from external source