| |
@@ -1,12 +1,22 @@
|
| |
- # Fedora Atomic is a cloud-focused spin implementing the Project
|
| |
- # Atomic patterns. Note that this replicates the same tree which can
|
| |
- # now be installed on bare metal.
|
| |
+ # Fedora Atomic Host is the Fedora version of the "Atomic Host" pattern
|
| |
+ # from [Project Atomic](http://www.projectatomic.io/).
|
| |
|
| |
- # This image allocates most space to an LVM-managed thin pool
|
| |
- # dedicated for Docker containers, and uses docker-storage-setup to
|
| |
- # dynamically resize storage on boot.
|
| |
+ # This kickstart is used for cloud/virt images, and uses cloud-init
|
| |
+ # to bootstrap authentication, just like Fedora Cloud Base. (Also note the
|
| |
+ # fedora-atomic-vagrant.ks kickstart inherits from this).
|
| |
|
| |
- text
|
| |
+ # One very important thing to understand is that this image contains the same
|
| |
+ # OSTree commit as will be used on bare metal installations - Fedora Atomic Host
|
| |
+ # also has an ISO. One difference though is that cloud-init isn't enabled for
|
| |
+ # bare metal. When processing this kickstart then, Anaconda isn't actually
|
| |
+ # installing packages - it's just replicating a "pre-assembled" tree from
|
| |
+ # rpm-ostree.
|
| |
+
|
| |
+ # Basically, the `ostreesetup` verb replaces the traditional `%packages`
|
| |
+ # section. For example, `rpm-ostree status` can show you the same checksum and
|
| |
+ # version from an ISO install and this cloud image - it's the same bits.
|
| |
+
|
| |
+ text # don't use cmdline -- https://github.com/rhinstaller/anaconda/issues/931
|
| |
lang en_US.UTF-8
|
| |
keyboard us
|
| |
timezone --utc Etc/UTC
|
| |
@@ -14,45 +24,64 @@
|
| |
auth --useshadow --passalgo=sha512
|
| |
selinux --enforcing
|
| |
rootpw --lock --iscrypted locked
|
| |
- user --name=none
|
| |
|
| |
+ # Explicitly disable firewall since cloud providers generally provide
|
| |
+ # higher level firewall constructs (i.e. security groups).
|
| |
firewall --disabled
|
| |
|
| |
- bootloader --timeout=1 --append="no_timer_check console=tty1 console=ttyS0,115200n8"
|
| |
+ # console=ttyAMA0 and console=hvc0 as kernel boot parameter to see
|
| |
+ # kernel boot messages on serial console as well on aarch64 and
|
| |
+ # ppc64le respectively.
|
| |
+ # https://pagure.io/atomic-wg/issue/347
|
| |
+ bootloader --timeout=1 --append="no_timer_check console=tty1 console=ttyS0,115200n8 console=ttyAMA0 console=hvc0 net.ifnames=0"
|
| |
|
| |
network --bootproto=dhcp --device=link --activate --onboot=on
|
| |
services --enabled=sshd,cloud-init,cloud-init-local,cloud-config,cloud-final
|
| |
|
| |
zerombr
|
| |
clearpart --all
|
| |
- # Atomic differs from cloud - we want LVM
|
| |
- part /boot --size=300 --fstype="ext4"
|
| |
+ # Implement: https://pagure.io/atomic-wg/issue/281
|
| |
+ # The bare metal layout currently inherits from fedora server and is in
|
| |
+ # https://github.com/rhinstaller/anaconda/blob/master/pyanaconda/installclasses/fedora_atomic_host.py
|
| |
+ # However, the disk size is currently just 6GB for the cloud image (defined in pungi-fedora). So the
|
| |
+ # "15GB, rest unallocated" model doesn't make sense. The Vagrant box is 40GB (apparently a number of
|
| |
+ # Vagrant boxes come big and rely on thin provisioning).
|
| |
+ # In both cases, it's simplest to just fill all the disk space.
|
| |
+ #
|
| |
+ # Use reqpart to create hardware platform specific partitions
|
| |
+ # https://pagure.io/atomic-wg/issue/299
|
| |
+ reqpart --add-boot
|
| |
part pv.01 --grow
|
| |
volgroup atomicos pv.01
|
| |
- logvol / --size=3000 --fstype="xfs" --name=root --vgname=atomicos
|
| |
+ # Start from 3GB as we did before, since we just need a size. But we do --grow to fill all space.
|
| |
+ logvol / --size=3000 --grow --fstype="xfs" --name=root --vgname=atomicos
|
| |
|
| |
# Equivalent of %include fedora-repo.ks
|
| |
- ostreesetup --nogpg --osname=fedora-atomic --remote=fedora-atomic --url=https://kojipkgs.fedoraproject.org/compose/atomic/rawhide/ --ref=fedora-atomic/rawhide/x86_64/docker-host
|
| |
+ # Pull from the ostree repo that was created during the compose
|
| |
+ ostreesetup --nogpg --osname=fedora-atomic --remote=fedora-atomic --url=https://kojipkgs.fedoraproject.org/compose/atomic/repo/ --ref=fedora/rawhide/${basearch}/atomic-host
|
| |
|
| |
reboot
|
| |
|
| |
%post --erroronfail
|
| |
# See https://github.com/projectatomic/rpm-ostree/issues/42
|
| |
+ # Set the ostree repo to the location we want users to upgrade from
|
| |
+ # This location is where the compose gets synced to after the compose
|
| |
+ # is done.
|
| |
ostree remote delete fedora-atomic
|
| |
- ostree remote add --set=gpg-verify=false fedora-atomic 'https://dl.fedoraproject.org/pub/fedora/linux/atomic/rawhide/'
|
| |
+ ostree remote add --set=gpg-verify=true --set=gpgkeypath=/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-29-primary fedora-atomic 'https://kojipkgs.fedoraproject.org/atomic/repo/'
|
| |
|
| |
# older versions of livecd-tools do not follow "rootpw --lock" line above
|
| |
# https://bugzilla.redhat.com/show_bug.cgi?id=964299
|
| |
passwd -l root
|
| |
- # remove the user anaconda forces us to make
|
| |
- userdel -r none
|
| |
|
| |
# Work around https://bugzilla.redhat.com/show_bug.cgi?id=1193590
|
| |
cp /etc/skel/.bash* /var/roothome
|
| |
|
| |
# Configure docker-storage-setup to resize the partition table on boot
|
| |
- # https://github.com/projectatomic/docker-storage-setup/pull/25
|
| |
- echo 'GROWPART=true' > /etc/sysconfig/docker-storage-setup
|
| |
+ # and extend the root filesystem to fill it.
|
| |
+ # https://pagure.io/atomic-wg/issue/343
|
| |
+ echo 'GROWPART=true' >> /etc/sysconfig/docker-storage-setup
|
| |
+ echo 'ROOT_SIZE=+100%FREE' >> /etc/sysconfig/docker-storage-setup
|
| |
|
| |
echo -n "Getty fixes"
|
| |
# although we want console output going to the serial console, we don't
|
| |
@@ -68,12 +97,9 @@
|
| |
NOZEROCONF=yes
|
| |
EOF
|
| |
|
| |
- # For cloud images, 'eth0' _is_ the predictable device name, since
|
| |
- # we don't want to be tied to specific virtual (!) hardware
|
| |
- rm -f /etc/udev/rules.d/70*
|
| |
- ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules
|
| |
-
|
| |
- # simple eth0 config, again not hard-coded to the build hardware
|
| |
+ # Remove any persistent NIC rules generated by udev
|
| |
+ rm -vf /etc/udev/rules.d/*persistent-net*.rules
|
| |
+ # And ensure that we will do DHCP on eth0 on startup
|
| |
cat > /etc/sysconfig/network-scripts/ifcfg-eth0 << EOF
|
| |
DEVICE="eth0"
|
| |
BOOTPROTO="dhcp"
|
| |
@@ -82,24 +108,12 @@
|
| |
PERSISTENT_DHCLIENT="yes"
|
| |
EOF
|
| |
|
| |
- # generic localhost names
|
| |
- cat > /etc/hosts << EOF
|
| |
- 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
|
| |
- ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
|
| |
-
|
| |
- EOF
|
| |
- echo .
|
| |
-
|
| |
-
|
| |
# Because memory is scarce resource in most cloud/virt environments,
|
| |
# and because this impedes forensics, we are differing from the Fedora
|
| |
# default of having /tmp on tmpfs.
|
| |
echo "Disabling tmpfs for /tmp."
|
| |
systemctl mask tmp.mount
|
| |
|
| |
- # make sure firstboot doesn't start
|
| |
- echo "RUN_FIRSTBOOT=NO" > /etc/sysconfig/firstboot
|
| |
-
|
| |
# Uncomment this if you want to use cloud init but suppress the creation
|
| |
# of an "ec2-user" account. This will, in the absence of further config,
|
| |
# cause the ssh key from a metadata source to be put in the root account.
|
| |
@@ -124,6 +138,9 @@
|
| |
rm -f /var/tmp/zeros
|
| |
echo "(Don't worry -- that out-of-space error was expected.)"
|
| |
|
| |
+ # For trac ticket https://pagure.io/atomic-wg/issue/128
|
| |
+ rm -f /etc/sysconfig/network-scripts/ifcfg-ens3
|
| |
+
|
| |
echo "Adding Developer Mode GRUB2 menu item."
|
| |
/usr/libexec/atomic-devmode/bootentry add
|
| |
|
| |
@@ -131,4 +148,10 @@
|
| |
# fails due to RHBZ #1369794
|
| |
/sbin/chkconfig network off
|
| |
|
| |
+ # 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
|
| |
+ truncate -s 0 /etc/resolv.conf
|
| |
+
|
| |
%end
|
| |