lorax/share/composer/qcow2.ks

# Lorax Composer qcow2 output kickstart template

# Firewall configuration
firewall --enabled

# NOTE: The root account is locked by default
# Network information
network  --bootproto=dhcp --onboot=on --activate
# System keyboard
keyboard --xlayouts=us --vckeymap=us
# System language
lang en_US.UTF-8
# SELinux configuration
selinux --enforcing
# Installation logging level
logging --level=info
# Shutdown after installation
shutdown
# System bootloader configuration
bootloader --location=mbr
# Add platform specific partitions
reqpart --add-boot

%post
# Remove random-seed
rm /var/lib/systemd/random-seed

# Clear /etc/machine-id
rm /etc/machine-id
touch /etc/machine-id

# Remove the rescue kernel and image to save space
rm -f /boot/*-rescue*
%end

%packages
kernel
selinux-policy-targeted

# Make sure virt guest agents are installed
qemu-guest-agent
spice-vdagent

# NOTE lorax-composer will add the blueprint packages below here, including the final %end
Add lorax-composer and the composer kickstart templates 2018-05-03 16:14:11 +00:00			`# Lorax Composer qcow2 output kickstart template`

			`# Firewall configuration`
			`firewall --enabled`

Lock the root account, except on live-iso If we leave the root account w/o a password people will use it that way, leading to insecure images. Also if we use a default password. So lock the root account in the templates. Users will need to do one of these things: 1. Use [[customizations.user]] in their blueprint to configure root or another user. 2. Use [[customizations.sshkey]] to set a key for root 2. Install a package that configures a user at install time 3. Install a package that sets up a user at boot time (eg. cloud-init) This also drops the auth line from the kickstart templates, allowing it to use the default password algoritm instead of md5. Resolves: rhbz#1626122 2018-08-08 22:46:16 +00:00			`# NOTE: The root account is locked by default`
Add lorax-composer and the composer kickstart templates 2018-05-03 16:14:11 +00:00			`# Network information`
			`network --bootproto=dhcp --onboot=on --activate`
			`# System keyboard`
			`keyboard --xlayouts=us --vckeymap=us`
			`# System language`
			`lang en_US.UTF-8`
			`# SELinux configuration`
			`selinux --enforcing`
			`# Installation logging level`
			`logging --level=info`
			`# Shutdown after installation`
			`shutdown`
			`# System bootloader configuration`
			`bootloader --location=mbr`
Make the lorax-composer ks templates more generic Some platforms do not have grub2, and some require other partitions. Anaconda will add platform specific partitions if the 'reqpart' command is included, and it will add bootloader specific packages to the list if they are needed. Related: rhbz#1673744 2019-02-13 00:57:21 +00:00			`# Add platform specific partitions`
lorax-composer: Use reqpart --add-boot for partitioned disk templates Some platforms, like ppc64, require that the /boot partition be present. It doesn't hurt to have it there on other platforms so instead of trying to add per-arch kickstart templates just use reqpart --add-boot everywhere. Related: rhbz#1673744 2019-02-14 01:03:51 +00:00			`reqpart --add-boot`
Add lorax-composer and the composer kickstart templates 2018-05-03 16:14:11 +00:00
			`%post`
			`# Remove random-seed`
			`rm /var/lib/systemd/random-seed`
Replace /etc/machine-id with an empty file Since these images can be used to create multiple machines, they should not have a unique machine-id attached to them. Replace /etc/machine-id with an empty file so that it will be regenerated at boot time. (cherry picked from commit 6fab72d894cd0c59ff798502d5c30f814f1a4948) Related: rhbz#1628645 Related: rhbz#1628646 Related: rhbz#1628647 Related: rhbz#1628648 2018-10-05 18:27:28 +00:00
			`# Clear /etc/machine-id`
			`rm /etc/machine-id`
			`touch /etc/machine-id`
Remove exclusions from lorax-composer templates If a package is excluded in the template and later added by a blueprint or dependency, anaconda will fail to finish the installation. So remove the -dracut-config-rescue exclusion and instead remove the rescue artifacts in %post Related: rhbz#1673744 2019-02-19 00:52:49 +00:00
			`# Remove the rescue kernel and image to save space`
			`rm -f /boot/-rescue`
Add lorax-composer and the composer kickstart templates 2018-05-03 16:14:11 +00:00			`%end`

			`%packages`
			`kernel`
lorax-composer: Install selinux-policy-targeted in images This is required to ensure that SELinux is configured properly while building. It fixes the problem with building tar, and should be installed in the other image types for consistency. Resolves: rhbz#1645189 2018-11-27 21:56:00 +00:00			`selinux-policy-targeted`
Add lorax-composer and the composer kickstart templates 2018-05-03 16:14:11 +00:00
Add virt guest agents to the qcow2 compose (cherry picked from commit d5a1993640c5025d3781378f0000cd84374fa928) Resolves: rhbz#1628645 2018-09-28 19:25:21 +00:00			`# Make sure virt guest agents are installed`
			`qemu-guest-agent`
			`spice-vdagent`

Lock the root account, except on live-iso If we leave the root account w/o a password people will use it that way, leading to insecure images. Also if we use a default password. So lock the root account in the templates. Users will need to do one of these things: 1. Use [[customizations.user]] in their blueprint to configure root or another user. 2. Use [[customizations.sshkey]] to set a key for root 2. Install a package that configures a user at install time 3. Install a package that sets up a user at boot time (eg. cloud-init) This also drops the auth line from the kickstart templates, allowing it to use the default password algoritm instead of md5. Resolves: rhbz#1626122 2018-08-08 22:46:16 +00:00			`# NOTE lorax-composer will add the blueprint packages below here, including the final %end`