From 623954ee2ffb0ee25413e1ec09879077797277c2 Mon Sep 17 00:00:00 2001 From: Colin Walters Date: Sun, 16 Jul 2017 06:36:11 -0400 Subject: [PATCH] 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. --- fedora-atomic.ks | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/fedora-atomic.ks b/fedora-atomic.ks index bde2b68..5ca800b 100644 --- a/fedora-atomic.ks +++ b/fedora-atomic.ks @@ -24,12 +24,20 @@ 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. +# # 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 # Pull from the ostree repo that was created during the compose