Differential D1762 Diff 5970 proxmox/terraform/init-template.md

Changeset View

Standalone View

proxmox/terraform/init-template.md

This file was added.

				In the following documentation, we will explain the necessary steps
				needed to initialize a template vm.

				Expectations:

				- hypervisor: orsay (could be beaubourg, hypervisor3)
				- \`/usr/bin/qm\` available from the hypervisor

				Prepare vm template
				===================

				Connect to hypervisor orsay (\`ssh orsay\`)

				And then as root, retrieve openstack images:

				```
				mkdir debian-10
				wget -O debian-10/debian-10-openstack-amd64.qcow2 \
				https://cdimage.debian.org/cdimage/openstack/current/debian-10.0.1-20190708-openstack-amd64.qcow2
				wget -O debian-10/debian-10-openstack-amd64.qcow2.index \
				https://cdimage.debian.org/cdimage/openstack/current/debian-10.0.1-20190708-openstack-amd64.qcow2.index
				mkdir debian-9
				wget -O debian-9/debian-9-openstack-amd64.qcow2 \
				https://cloud.debian.org/images/cloud/OpenStack/current-9/debian-9-openstack-amd64.qcow2
				wget -O debian-9/debian-9-openstack-amd64.qcow2.index \
				https://cloud.debian.org/images/cloud/OpenStack/current-9/debian-9-openstack-amd64.qcow2.index
				```

				Note:

				- Not presented here but you should check the hashes of what you
				retrieved from the internet

				Create vm
				---------

				```
				chmod +x init-template.sh
				./init-template.sh 9
				```

				This created a basic vm with basic login/pass as root/test so we can
				connect to it.

				Note: Implementation wise, this uses an openstack debian image,
				cloud-init ready.

				Check image is working
				----------------------

				The rationale is to:

				- boot the vm
				- check some basic information (kernel, distribution, connection,
				release, etc...).
				- adapt slightly the vms (dns resolver, ip, upgrade, etc...)

				### Start vm

				```
				qm start 9000
				```

				### Checks

				Login through the console web-ui:

				- accessible from <https://orsay.internal.softwareheritage.org:8006/>
				- View \`datacenter\`
				- unfold the hypervisor \`orsay\` menu
				- select the vm \`9000\`
				- click the \`console\` menu.
				- log in as root/test password

				Checks:

				- kernel linux version
				- debian release

				### Adaptations

				Update grub's timeout to 0 for a faster boot (as root):
				```
				sed -i s'/GRUB_TIMEOUT = 5/GRUB_TIMEOUT = 0/' etc/default/grub
				update-grub
				```
				ardumontAuthorUnsubmitted Done Inline Actions This is no longer needed as this is done in cloud-init. ardumont: This is no longer needed as this is done in cloud-init.

				Then, add some expected defaults:
				```
				apt update
				apt upgrade -y
				apt install -y puppet
				systemctl disable puppet.service
				mkdir -p /etc/facter/facts.d
				echo location=sesi_rocquencourt_staging > /etc/facter/facts.d/location.txt
				ardumontAuthorUnsubmitted Done Inline Actions This will be exploited by puppet to set things up location-wise. ardumont: This will be exploited by puppet to set things up location-wise.

				```
				- etc...

				### Remove cloud-init setup from vm

				```
				# stop vm
				qm stop 9000
				# remove cloud-init setup
				qm set 9000 --delete ciuser,cipassword,ipconfig0,nameserver
				```

				Template the image
				------------------

				When the vm is ready, we can use it as a base template for future
				clones:

				```
				qm template 9000
				```

				Clone image
				===========

				This is a tryout referenced here to demonstrate the shortcoming. That\'s
				not necesary to do this as this will be taken care of by proxmox.

				Sadly full clone only works:

				```
				qm clone 9000 666 --name debian-10-tryout --full true
				```

				As in: Fully clone from template \"9000\", the new vm with id \"666\"
				dubbed \"buster-tryout\".

				Note (partial clone does not work):

				```
				root@orsay:/home/ardumont/proxmox# qm clone 9000 666 --name buster-tryout
				Linked clone feature is not supported for drive 'virtio0'
				```

				Note:

				- tested with all drives: ide, sata, scsi, virtio
				- only thing that worked was without a disk (but then no more os...)

				source
				======

				<https://orsay.internal.softwareheritage.org:8006/pve-docs/chapter-qm.html#qm_cloud_init>