davidlt/fedora-kickstarts
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
19322f31e0
fedora-kickstarts/fedora-cloud-base.ks

117 lines
4.1 KiB
Plaintext
Raw Normal View History

Minor inline docs updates Signed-off-by: Peter Robinson <pbrobinson@fedoraproject.org>
2017-03-02 15:42:13 +00:00
# This is a basic Fedora cloud spin designed to work in OpenStack and other
add cloud image kickstarts, pulled from the cloud-kickstart repo, we have different snippets per arch because they need different kernels
2013-10-26 13:41:43 +00:00
# private cloud environments. It's configured with cloud-init so it will
# take advantage of ec2-compatible metadata services for provisioning ssh
# keys. Cloud-init creates a user account named "fedora" with passwordless
# sudo access. The root password is empty and locked by default.
#
cloud-base: Document how to use ImageFactory locally
2015-04-22 20:46:43 +00:00
# This kickstart file is designed to be used with ImageFactory (in Koji).
#
# To do a local build, you'll need to install ImageFactory. See
# http://worknotes.readthedocs.org/en/latest/cloudimages.html for some notes.
#
# For a TDL file, I store one here:
Fix links to this example TDL file. Signed-off-by: Ralph Bean <rbean@redhat.com>
2017-07-07 19:58:34 +00:00
# https://pagure.io/fedora-atomic/raw/master/f/fedora-atomic-rawhide.tdl
cloud-base: Document how to use ImageFactory locally
2015-04-22 20:46:43 +00:00
# (Koji generates one internally...what we really want is Koji to publish it statically)
Clean up some unneeded whitespace.
2018-07-12 20:52:52 +00:00
#
cloud-base: Document how to use ImageFactory locally
2015-04-22 20:46:43 +00:00
# Once you have imagefactory and imagefactory-plugins installed, run:
Clean up some unneeded whitespace.
2018-07-12 20:52:52 +00:00
#
Fix links to this example TDL file. Signed-off-by: Ralph Bean <rbean@redhat.com>
2017-07-07 19:58:34 +00:00
# curl -O https://pagure.io/fedora-atomic/raw/master/f/fedora-atomic-rawhide.tdl
cloud-base: Document how to use ImageFactory locally
2015-04-22 20:46:43 +00:00
# tempfile=$(mktemp --suffix=.ks)
Small fix for local cloud image creation instruction ksflatten expects a "-c" option to point to the kickstart.
2015-04-27 04:10:55 +00:00
# ksflatten -v F22 -c fedora-cloud-base.ks > ${tempfile}
cloud-base: Document how to use ImageFactory locally
2015-04-22 20:46:43 +00:00
# imagefactory --debug base_image --file-parameter install_script ${tempfile} fedora-atomic-rawhide.tdl
#
add cloud image kickstarts, pulled from the cloud-kickstart repo, we have different snippets per arch because they need different kernels
2013-10-26 13:41:43 +00:00
docker, cloud: don't use cmdline for install mode cmdline makes it so that %post --erroronfail won't actually stop the installation in a way that imagefactory will detect the problem and fail the build. See [1] for more details. [1] https://github.com/rhinstaller/anaconda/issues/931
2017-01-19 20:46:44 +00:00
text # don't use cmdline -- https://github.com/rhinstaller/anaconda/issues/931
add cloud image kickstarts, pulled from the cloud-kickstart repo, we have different snippets per arch because they need different kernels
2013-10-26 13:41:43 +00:00
lang en_US.UTF-8
keyboard us
timezone --utc Etc/UTC
selinux --enforcing
CLOUD: fix up the kickstart to make the world happy
2014-05-30 13:30:17 +00:00
rootpw --lock --iscrypted locked
add cloud image kickstarts, pulled from the cloud-kickstart repo, we have different snippets per arch because they need different kernels
2013-10-26 13:41:43 +00:00
by popular demand, disable the iptables firewall entirely.
2013-11-18 17:15:19 +00:00
firewall --disabled
add cloud image kickstarts, pulled from the cloud-kickstart repo, we have different snippets per arch because they need different kernels
2013-10-26 13:41:43 +00:00
When building cloud images oz uses dracut to setup networking and it in turn makes a ifcfg-en<something> file with this config. We don't want to use this, we want to always use ifcfg-eth0 so it's the same on all images. So, we remove ifcfg-en* (They are different on each arch we make cloud images for, but en* gets them all). Additionally we were using some old udev tricks to get eth0, but this is error prone and already incorrect as systemd-udev has moved files around, so instead we just switch to net.ifnames=0 on the boot line, which should continue working.
2018-03-19 23:23:29 +00:00
# We pass net.ifnames=0 because we always want to use eth0 here on all the cloud images.
bootloader --timeout=1 --append="no_timer_check net.ifnames=0 console=tty1 console=ttyS0,115200n8"
add cloud image kickstarts, pulled from the cloud-kickstart repo, we have different snippets per arch because they need different kernels
2013-10-26 13:41:43 +00:00
drop rsyslog service from all cloud kickstarts it's no longer pulled in by cloud-init (since 2014...). None of these kickstarts has it in %packages, and it's not in any of the cloud environment or package groups in comps either. So it seems like no-one particularly wants rsyslog in the cloud images. From compose logs, it looks like trying to enable a non-existent service in anaconda in Fedora 24 and earlier wasn't a fatal error (anaconda more or less logged a warning and continued), but in Fedora 25 and later it does seem to be fatal. It at least causes one anaconda thread to crash, though the image compose completes. I think possibly at least the way anaconda's run in the Cloud compose process, the main thread manages to exit, but it seems pretty likely the thread crash will result in problems in the produced image. Needed on master and f25.
2016-08-24 18:11:01 +00:00
services --enabled=sshd,cloud-init,cloud-init-local,cloud-config,cloud-final
add cloud image kickstarts, pulled from the cloud-kickstart repo, we have different snippets per arch because they need different kernels
2013-10-26 13:41:43 +00:00
zerombr
clearpart --all
cloud/docker: move to autopart with the new no home/swap/boot options to enable generic architecture images Signed-off-by: Peter Robinson <pbrobinson@fedoraproject.org>
2017-05-15 16:30:43 +00:00
autopart --noboot --nohome --noswap --nolvm
add cloud image kickstarts, pulled from the cloud-kickstart repo, we have different snippets per arch because they need different kernels
2013-10-26 13:41:43 +00:00
%include fedora-repo.ks
reboot
cloud: rework package list, add comments This reworks the package list to add comments and remove some things that didn't need to be explicitly removed. - remove +systemd-udev -> already included by default - remove -biosdevname -> not included by default - remove -iprutils -> not included by default - remove -uboot-tools -> not included by default There are no packages added or removed from the built cloud image as part of this change. Just updating the input package list to be more meaningful. (cherry picked from commit 4a6850e465f0d17841a4794ac3ed67f0a30345f6)
2020-09-02 21:10:07 +00:00
##### begin package list #############################################
cloud: remove instLang hacks `%packages --instLangs=en` works as intended now. (cherry picked from commit 10573df5c2cb145488c408b42b1d84839b5f5c94)
2020-09-02 21:07:06 +00:00
%packages --instLangs=en
fedora-release-cloud in cloud images
2014-07-11 15:01:56 +00:00
cloud: rework package list, add comments This reworks the package list to add comments and remove some things that didn't need to be explicitly removed. - remove +systemd-udev -> already included by default - remove -biosdevname -> not included by default - remove -iprutils -> not included by default - remove -uboot-tools -> not included by default There are no packages added or removed from the built cloud image as part of this change. Just updating the input package list to be more meaningful. (cherry picked from commit 4a6850e465f0d17841a4794ac3ed67f0a30345f6)
2020-09-02 21:10:07 +00:00
# Include packages for the cloud-server-environment group
CLOUD: install the environment correctly
2014-09-11 23:41:58 +00:00
@^cloud-server-environment
add cloud image kickstarts, pulled from the cloud-kickstart repo, we have different snippets per arch because they need different kernels
2013-10-26 13:41:43 +00:00
cloud: rework package list, add comments This reworks the package list to add comments and remove some things that didn't need to be explicitly removed. - remove +systemd-udev -> already included by default - remove -biosdevname -> not included by default - remove -iprutils -> not included by default - remove -uboot-tools -> not included by default There are no packages added or removed from the built cloud image as part of this change. Just updating the input package list to be more meaningful. (cherry picked from commit 4a6850e465f0d17841a4794ac3ed67f0a30345f6)
2020-09-02 21:10:07 +00:00
# Don't include the kernel toplevel package since it pulls in
# kernel-modules. We're happy for now with kernel-core.
-kernel
kernel-core
fedora-cloud-base: Add which package back. After removing grub2 the which package gets removed. Let's add it back because it is generally useful and because it is needed for many vagrant utilities to work.
2016-05-04 18:15:07 +00:00
cloud: rework package list, add comments This reworks the package list to add comments and remove some things that didn't need to be explicitly removed. - remove +systemd-udev -> already included by default - remove -biosdevname -> not included by default - remove -iprutils -> not included by default - remove -uboot-tools -> not included by default There are no packages added or removed from the built cloud image as part of this change. Just updating the input package list to be more meaningful. (cherry picked from commit 4a6850e465f0d17841a4794ac3ed67f0a30345f6)
2020-09-02 21:10:07 +00:00
# Don't include dracut-config-rescue. It will have dracut generate a
# "rescue" entry in the grub menu, but that also means there is a
# rescue kernel and initramfs that get created, which (currently) add
# about another 40MiB to the /boot/ partition. Also the "rescue" mode
# is generally not useful in the cloud.
add cloud image kickstarts, pulled from the cloud-kickstart repo, we have different snippets per arch because they need different kernels
2013-10-26 13:41:43 +00:00
-dracut-config-rescue
cloud: rework package list, add comments This reworks the package list to add comments and remove some things that didn't need to be explicitly removed. - remove +systemd-udev -> already included by default - remove -biosdevname -> not included by default - remove -iprutils -> not included by default - remove -uboot-tools -> not included by default There are no packages added or removed from the built cloud image as part of this change. Just updating the input package list to be more meaningful. (cherry picked from commit 4a6850e465f0d17841a4794ac3ed67f0a30345f6)
2020-09-02 21:10:07 +00:00
# Plymouth provides a graphical boot animation. In the cloud we don't
# need a graphical boot animation. This also means anaconda won't put
# rhgb/quiet on kernel command line
atomic, cloud: remove rhgb by removing plymouth a59dfe5 caused us a few problems: - sed was breaking the symlink on atomic systems - /boot/grub2/grub.cfg is not the right file on a UEFI system - etc.. We'll solve this problem a different way by just not installing plymouth in our systems, which is another way [1] to make sure rhgb/quiet don't appear on your kernel command line. [1] https://github.com/rhinstaller/anaconda/blob/ee91db6fa3972668b05808b3c7de125a7edd581f/pyanaconda/payload/__init__.py#L722-L726
2017-05-24 05:41:20 +00:00
-plymouth
cloud: rework package list, add comments This reworks the package list to add comments and remove some things that didn't need to be explicitly removed. - remove +systemd-udev -> already included by default - remove -biosdevname -> not included by default - remove -iprutils -> not included by default - remove -uboot-tools -> not included by default There are no packages added or removed from the built cloud image as part of this change. Just updating the input package list to be more meaningful. (cherry picked from commit 4a6850e465f0d17841a4794ac3ed67f0a30345f6)
2020-09-02 21:10:07 +00:00
cloud: move firewalld remove to package list It works in the package list so let's remove it there so it never gets installed in the first place rather than the dnf erase hack we have now. (cherry picked from commit f4c7f67ece79b624af62ffc8fb777954e5592dfd)
2020-09-02 21:13:36 +00:00
# No need for firewalld for now. We don't have a firewall on by default.
-firewalld
Cloud edition prefers noswap for now. Discussions ongoing upstream in https://pagure.io/cloud-sig/issue/307 Signed-off-by: Chris Murphy <chrismurphy@fedoraproject.org>
2020-07-09 17:48:03 +00:00
# noswap on Cloud for now
-zram-generator-defaults
add cloud image kickstarts, pulled from the cloud-kickstart repo, we have different snippets per arch because they need different kernels
2013-10-26 13:41:43 +00:00
%end
cloud: rework package list, add comments This reworks the package list to add comments and remove some things that didn't need to be explicitly removed. - remove +systemd-udev -> already included by default - remove -biosdevname -> not included by default - remove -iprutils -> not included by default - remove -uboot-tools -> not included by default There are no packages added or removed from the built cloud image as part of this change. Just updating the input package list to be more meaningful. (cherry picked from commit 4a6850e465f0d17841a4794ac3ed67f0a30345f6)
2020-09-02 21:10:07 +00:00
##### end package list ###############################################
add cloud image kickstarts, pulled from the cloud-kickstart repo, we have different snippets per arch because they need different kernels
2013-10-26 13:41:43 +00:00
cloud: update comments and minor rework for kspost This should make things a little clearer. (cherry picked from commit 99f3ec5d72482f76a19bef54e1cd028fbbe8f69d)
2020-09-02 21:16:28 +00:00
##### begin kickstart post ###########################################
add cloud image kickstarts, pulled from the cloud-kickstart repo, we have different snippets per arch because they need different kernels
2013-10-26 13:41:43 +00:00
%post --erroronfail
cloud: update comments and minor rework for kspost This should make things a little clearer. (cherry picked from commit 99f3ec5d72482f76a19bef54e1cd028fbbe8f69d)
2020-09-02 21:16:28 +00:00
# linux-firmware is installed by default and is quite large. As of mid 2020:
# Total download size: 97 M
# Installed size: 268 M
# So far we've been fine shipping without it so let's continue.
# More discussion about this in #1234504.
adjust linux-firmware for cloud images
2015-09-23 06:16:18 +00:00
echo "Removing linux-firmware package."
rpm -e linux-firmware
add cloud image kickstarts, pulled from the cloud-kickstart repo, we have different snippets per arch because they need different kernels
2013-10-26 13:41:43 +00:00
cloud: update comments and minor rework for kspost This should make things a little clearer. (cherry picked from commit 99f3ec5d72482f76a19bef54e1cd028fbbe8f69d)
2020-09-02 21:16:28 +00:00
# See the systemd-random-seed.service man page that says:
# " It is recommended to remove the random seed from OS images intended
# for replication on multiple systems"
add cloud image kickstarts, pulled from the cloud-kickstart repo, we have different snippets per arch because they need different kernels
2013-10-26 13:41:43 +00:00
echo "Removing random-seed so it's not the same in every image."
all: Correct path to /var/lib/systemd/random-seed At least for Atomic Host, AFAICS it isn't actually in the final image; not entirely sure why. But we should be using the right path here anyways. https://bugzilla.redhat.com/show_bug.cgi?id=1424404
2017-02-17 20:05:13 +00:00
rm -f /var/lib/systemd/random-seed
add cloud image kickstarts, pulled from the cloud-kickstart repo, we have different snippets per arch because they need different kernels
2013-10-26 13:41:43 +00:00
cloud image import fedora GPG key for RPMs, as the livecd does
2013-12-06 17:16:02 +00:00
echo "Import RPM GPG key"
Unify obtaining 'relesever' Continuation of https://pagure.io/fedora-kickstarts/c/19a7b3b113d97db14d27f6a86db3c7479453a5ea?branch=master but across entire repository.
2019-07-17 08:49:05 +00:00
releasever=$(rpm --eval '%{fedora}')
use uname -i as it gives the arch used as the basearch by yum uname -m is incorrect
2013-12-12 10:12:29 +00:00
basearch=$(uname -i)
cloud image import fedora GPG key for RPMs, as the livecd does
2013-12-06 17:16:02 +00:00
rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
Revert "Use fstrim to zero out empty space rather than forcing it with dd" Nope -- still does not work This reverts commit 99c9224ef57a58ccc40bb23cb3b93eb314b2f94c.
2014-11-03 20:27:08 +00:00
echo "Zeroing out empty space."
# This forces the filesystem to reclaim space from deleted files
dd bs=1M if=/dev/zero of=/var/tmp/zeros || :
rm -f /var/tmp/zeros
echo "(Don't worry -- that out-of-space error was expected.)"
add cloud image kickstarts, pulled from the cloud-kickstart repo, we have different snippets per arch because they need different kernels
2013-10-26 13:41:43 +00:00
cloud: clean up networking configuration We're no longer using legacy network scripts to bring up networking. We're using NetworkManager and now in F33+ networkmanager will even default to writing out new configuration as NM keyfiles in /etc/NetworkManager/system-connections/. We don't need to lay down a networking config for eth0. Either cloud-init will do that for us or NetworkManager will default to DHCP anyway. We also don't need to populate /etc/hosts as that will get done on boot too with the same content we were writing there already. (cherry picked from commit 54d53e8439445e4340e86f3274bf3440158997cf)
2020-09-02 21:02:18 +00:00
# When we build the image a networking config file gets left behind.
# Let's clean it up.
echo "Cleanup leftover networking configuration"
rm -f /etc/NetworkManager/system-connections/*.nmconnection
Fixes trac #128 Removes extra ifcfg file.
2015-10-15 08:14:41 +00:00
cloud: update comments and minor rework for kspost This should make things a little clearer. (cherry picked from commit 99f3ec5d72482f76a19bef54e1cd028fbbe8f69d)
2020-09-02 21:16:28 +00:00
# Clear machine-id on pre generated images
truncate -s 0 /etc/machine-id
zero out resolv.conf during install Anaconda is writing an /etc/resolv.conf from the install environment. The system should start out with an empty file, otherwise cloud-init will try to use this information and may error: https://bugs.launchpad.net/cloud-init/+bug/1670052
2017-03-28 18:56:51 +00:00
add cloud image kickstarts, pulled from the cloud-kickstart repo, we have different snippets per arch because they need different kernels
2013-10-26 13:41:43 +00:00
%end
cloud: update comments and minor rework for kspost This should make things a little clearer. (cherry picked from commit 99f3ec5d72482f76a19bef54e1cd028fbbe8f69d)
2020-09-02 21:16:28 +00:00
##### end kickstart post ############################################
Reference in New Issue Copy Permalink