lorax/share/composer/tar.ks

# Lorax Composer tar 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 (tar doesn't need a bootloader)
bootloader --location=none

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

# NOTE Do NOT add any other sections after %packages
%packages
# Packages requires to support this output format go here


# NOTE lorax-composer will add the blueprint packages below here, including the final %end
Add building an image, and the /compose route to start it This adds the ability to build a tar output image. The /compose and /compose/types API routes are now available. To start a build POST a JSON body to /compose, like this: {"recipe_name":"glusterfs", "compose_type":"tar", "branch":"master"} This will return a unique build id: { "build_id": "4d13abb6-aa4e-4c80-a671-0b867e6e77f6", "status": true } which will be used to keep track of the build status (routes for this do not exist yet). 2018-01-30 01:08:30 +00:00			`# Lorax Composer tar 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#1626120 2018-08-08 22:46:16 +00:00			`# NOTE: The root account is locked by default`
Add building an image, and the /compose route to start it This adds the ability to build a tar output image. The /compose and /compose/types API routes are now available. To start a build POST a JSON body to /compose, like this: {"recipe_name":"glusterfs", "compose_type":"tar", "branch":"master"} This will return a unique build id: { "build_id": "4d13abb6-aa4e-4c80-a671-0b867e6e77f6", "status": true } which will be used to keep track of the build status (routes for this do not exist yet). 2018-01-30 01:08:30 +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`
Move disklabel and UEFI support to compose.py Currently we are making MBR disk images for qcow2 and partitioned disk, so the UEFI packages aren't required at this point. Move the clearpart command into compose.py so that in the futute it can use clearpart --disklabel to create a GPT image, and add the required packages to the package set. 2018-08-08 15:44:01 +00:00			`# System bootloader configuration (tar doesn't need a bootloader)`
			`bootloader --location=none`
Add building an image, and the /compose route to start it This adds the ability to build a tar output image. The /compose and /compose/types API routes are now available. To start a build POST a JSON body to /compose, like this: {"recipe_name":"glusterfs", "compose_type":"tar", "branch":"master"} This will return a unique build id: { "build_id": "4d13abb6-aa4e-4c80-a671-0b867e6e77f6", "status": true } which will be used to keep track of the build status (routes for this do not exist yet). 2018-01-30 01:08:30 +00:00
			`%post`
			`# Remove random-seed`
			`rm /var/lib/systemd/random-seed`
			`%end`

			`# NOTE Do NOT add any other sections after %packages`
			`%packages`
			`# Packages requires to support this output format go here`


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#1626120 2018-08-08 22:46:16 +00:00			`# NOTE lorax-composer will add the blueprint packages below here, including the final %end`