From 09243c9986043d877c7282436d462bdeeaac0dbb Mon Sep 17 00:00:00 2001
From: Colin Walters <walters@verbum.org>
Date: Nov 10 2014 14:42:00 +0000
Subject: cloud-atomic: Re-shrink rootfs partitions


mattdm changed these previously because we hit an ENOSPC error during
qcow2 image creation, but that *really* happened because the Fedora
rel-eng create-cloud-images script hardcoded 3GB.

Now that we've shrunk the content down to ~850MB, drop the defaults:

- rootfs down to 2GB.  This is enough space for a replacement of
  all content, plus a bit of spare room for logging
- /boot to 200MB.  At present, kernel+initramfs is just 30MB,
  so this is still very conservative.

---

diff --git a/fedora-cloud-atomic.ks b/fedora-cloud-atomic.ks
index 37fb815..63106d1 100644
--- a/fedora-cloud-atomic.ks
+++ b/fedora-cloud-atomic.ks
@@ -24,10 +24,10 @@ services --enabled=network,sshd,rsyslog,cloud-init,cloud-init-local,cloud-config
 zerombr
 clearpart --all
 # Atomic differs from cloud - we want LVM
-part /boot --size=500 --fstype="ext4"
+part /boot --size=200 --fstype="ext4"
 part pv.01 --grow
 volgroup atomicos pv.01
-logvol / --size=5000 --fstype="xfs" --name=root --vgname=atomicos
+logvol / --size=2000 --fstype="xfs" --name=root --vgname=atomicos
 
 ostreesetup --nogpg --osname=fedora-atomic-host --remote=installmedia --url=http://compose-x86-02.phx2.fedoraproject.org/compose/atomic/ --ref=fedora-atomic/f21/x86_64/docker-host