3rdparty/google: add script for making Google Compute Engine images

Change-Id: Ia52b8e6a30255ee7903cfb0834d4030b6774b1c8
Reviewed-on: https://review.haiku-os.org/c/haiku/+/5963
Reviewed-by: Alex von Gluck IV <kallisti5@unixzen.com>
Reviewed-by: Adrien Destugues <pulkomandy@pulkomandy.tk>
Tested-by: Commit checker robot <no-reply+buildbot@haiku-os.org>
This commit is contained in:
Alexander von Gluck IV 2022-12-23 15:20:13 -06:00 committed by Adrien Destugues
parent 8040281d80
commit 17889a8c70

59
3rdparty/cloud/sysprep-gce.sh vendored Executable file
View File

@ -0,0 +1,59 @@
#!/bin/bash
#
# Making a new Google Compute Engine image
# * Create a raw disk 4GiB image dd if=/dev/zero of=disk.raw bs=1M count=4096
# * Boot VM (qemu-system-x86_64 -cdrom (haiku-release.iso) -hda disk.raw -boot d --enable-kvm -m 4G
# * Partition new disk
# * 32 MiB EFI System Data. FAT32 named "ESP"
# * Rest of disk, Haiku, BFS, named "Haiku"
# * Install Haiku to it new disk
# * Allow installer to Reboot, *boot again from CD*
# * Setup EFI bootloader
# * mount "haiku esp", mount "ESP"
# * Copy all contents of "haiku esp" to "ESP"
# * unmount "haiku esp", unmount "ESP"
# * Mount new Haiku install. (should mount to /Haiku1)
# * Run this script (sysprep-gce.sh /Haiku1)
# * Manually copy over latest r1beta4 haiku, haiku_devel, haiku_data_translations, haiku_loader
# * Needed on r1b4 due to / permissions fix needed by sshd
# * Shutdown VM. DO NOT BOOT FROM NEW DISK!
# * Booting from new disk will cause SSH host keys to generate! (#18186)
# * Compress tar cvzf haiku-r1beta4-v20221222.tar.gz disk.raw
# * Upload to google cloud storage bucket for haiku.inc (ex: haiku-images/r1beta4/xxx)
# * Import image
# * compute engine -> images
# * create image
# * source: Cloud storage file -> haiku-images/r1beta4/xxx
# * name: haiku-r1beta4-x64-v20221222
# * family: haiku-r1beta4-x64
# * description: Haiku R1/Beta4 x86_64
if [ $# -ne 1 ]; then
echo "usage: $0 <HAIKU ROOTFS>"
echo " example: $0 /Haiku1"
return 1;
fi
SMOL_RELEASE="0.1.1-1"
TARGET_ROOTFS="$1"
echo "Preparing $TARGET_ROOTFS for Google Compute Engine..."
echo "WARNING: DO NOT DIRECTLY BOOT FROM THIS HAIKU INSTALL!"
echo ""
echo "Installing basic authentication stuff..."
# Installs gce_metadata_ssh tool for sshd. This lets you control the keys
# of the "user" user from GKE. ONLY "user" WORKS! We have no PAM for gce's os-login stuff
wget https://eu.hpkg.haiku-os.org/haikuports/r1beta4/x86_64/current/packages/smolcloudtools-$SMOL_RELEASE-x86_64.hpkg \
-O $TARGET_ROOTFS/system/packages/smolcloudtools-$SMOL_RELEASE-x86_64.hpkg
echo "Configuring ssh..."
# Configure SSHD (reminder, sshd sees "user" as root since it is UID 0)
echo "# For Google Compute Engine" >> $TARGET_ROOTFS/system/settings/ssh/sshd_config
echo "AuthorizedKeysCommand /bin/gce_metadata_ssh" >> $TARGET_ROOTFS/system/settings/ssh/sshd_config
echo "AuthorizedKeysCommandUser user" >> $TARGET_ROOTFS/system/settings/ssh/sshd_config
echo "PasswordAuthentication no" >> $TARGET_ROOTFS/system/settings/ssh/sshd_config
echo "PermitRootLogin without-password" >> $TARGET_ROOTFS/system/settings/ssh/sshd_config
unmount $TARGET_ROOTFS
echo "Complete! Please shutdown VM. DO NOT BOOT FROM NEW OS IMAGE!"