lorax/share/composer/partitioned-disk.ks

# Lorax Composer partitioned disk 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 timezone
timezone  US/Eastern
# System bootloader configuration
bootloader --location=mbr

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

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

%packages
kernel
-dracut-config-rescue

grub2

# 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 partitioned disk 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 timezone`
			`timezone US/Eastern`
			`# System bootloader configuration`
			`bootloader --location=mbr`

			`%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`
Add lorax-composer and the composer kickstart templates 2018-05-03 16:14:11 +00:00			`%end`

			`%packages`
			`kernel`
			`-dracut-config-rescue`

			`grub2`

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`