From ca4d6f43e103b2e926cfc1226dbf75c6bed19a26 Mon Sep 17 00:00:00 2001 From: Colin Walters Date: Sep 13 2017 17:40:06 +0000 Subject: atomichost: Update partitioning for new model See https://pagure.io/atomic-wg/issue/281 This causes us to match the productimg setup. At some point hopefully we can use `autopart` and not duplicate it. --- diff --git a/fedora-atomic.ks b/fedora-atomic.ks index c7f3622..1bd2984 100644 --- a/fedora-atomic.ks +++ b/fedora-atomic.ks @@ -24,11 +24,21 @@ services --enabled=sshd,cloud-init,cloud-init-local,cloud-config,cloud-final zerombr clearpart --all -# Atomic differs from cloud - we want LVM +# Implement: https://pagure.io/atomic-wg/issue/281 +# The bare metal layout default is in http://pkgs.fedoraproject.org/cgit/rpms/fedora-productimg-atomic.git +# 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. +# +# For /boot, we currently diverge from the Fedora default of 1GB here since it really feels like a huge +# waste of space with the 6GB layout. At some point we could investigate dropping the /boot partition, see +# https://github.com/ostreedev/ostree/pull/215 and https://github.com/ostreedev/ostree/pull/268 part /boot --size=300 --fstype="ext4" 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 # Pull from the ostree repo that was created during the compose