IT Infrastructure
The IT Infrastructure at TinkerMill consists of a few desktops, laptops and printers distributed throughout the facility for use by members. There are a few dedicated machine side PC's for interfacing with pieces of equipment such as the Laser cutter, the ShopBot and 3D printers. In addition we have a small hypervised server infrastructure for local monitoring and backup functions.
Objective
Improve and maintain the performance and reliability of the compute equipment and network through the use of sound best practices and tapping into the experience and expertise of members interested in helping out.
Goals
To provide both a Production environment for running the day-to-day operational needs and Development/Test environment for members to experiment in.
Contact us
We host a weekly team meeting on Tuesday nights at 8PM This is a good time to meet some of the members who handle the care and feeding. It is also a good place to verbalize requests. We keep a running lists of the TODO's where tinkermill.org members have update access. Operating 100% on volunteerism we are always looking for those interested in helping out. Whether you're interested in software development, system administration or network configuration.
If you can't make the weekly meeting you can reach us on slack #network channel
Links
Notes
Clonezilla Backups
Some notes from experience:
- Do a couple of test restores.
- On Windows boxes you may need to do a boot repair on after a clonezilla restore. Not a big deal, but scary at first when the box doesn't boot after a restore.
- When some RHEL/CentOS boxes restore to a different hard drive, it may end up horribly broken because the GUID/UUID of the HDD device changed, which required a rebuild instead of a restore.
- YMMV, and test, test, test.
Procedure:
- Boot from Clonezilla USB or disc (you may need to enable or select in BIOS/Boot screen)
- At the boot screen, select the default "Clonezilla live(Default settings, VGA 800x600)" boot mode.
- At the "Choose language" screen, select the default "en_US.UTF-8 English" language.
- At the "Configuring console-data" screen, select the default "Don't touch keymap" policy.
- At the "Start Clonezilla" screen, select the default "Start_Clonezilla" mode.
- At the first "Clonezilla - Opensource Clone System (OCS)" screen, select the default "device-image" mode.
- At the "Mount Clonezilla image directory" screen, select the "nfs_server" mode.
- At the "Network config" screen, select the default "dhcp" mode.
- At the "NFS version" screen, select the "nfs4 NFS v4" version.
- At the first "Mount NFS server" screen, enter "10.2.0.18" for the IP address.
- At the second "Mount NFS server" screen, select the default "/partimag/" directory.
- At the Press "Enter" to continue prompt, press Enter.
- At the second "Clonezilla - Opensource Clone System (OCS)" screen, select the default "Beginner" mode.
- At the "Clonezilla - Opensource Clone System (OCS): Select mode" screen, select the default "savedisk" mode.
- At the first "Clonezilla - Opensource Clone System (OCS) | Mode: savedisk" screen, append the hostname to the image name. Ex: -bigroompublicpc
- At the second "Clonezilla - Opensource Clone System (OCS) | Mode: savedisk" screen, select all disks.
- At the first "Clonezilla advanced extra parameters | Mode: savedisk" screen, select the default "-sfsck" option.
- At the second "Clonezilla advanced extra parameters | Mode: savedisk" screen, select the default "Yes, check the saved image" option.
- At the third "Clonezilla advanced extra parameters | Mode: savedisk" screen, select the default "-senc" option.
- At the "Mode: savedisk" screen, select the default "-p choose" action.
- At the Press "Enter" to continue prompt, press Enter.
- At the "Are you sure you want to continue (y/n)" prompt, select y.
- Monitor the "Partclone" process for each disk.
- At the Press "Enter" to continue prompt, press Enter.
- At the "Choose mode" screen, select the "reboot" mode.
- At the "Please remove the live-medium" prompt, remove the boot media and then press Enter.
VMHOST2
If you rebuild VMHOST2 then you may need to configure GRUB2 so that it uses GRUB_TIMEOUT_STYLE=hidden.
To do this, as root add GRUB_TIMEOUT_STYLE=hidden to /etc/default/grub, then run update-grub.
Otherwise the system may appear to wait indefinitely at the GRUB prompt for no reason. We think this may be due to the system thinking it sees key presses.
