From 08243564f393cab9a8ab553c9a7164b5bdf012ce Mon Sep 17 00:00:00 2001
From: Adam Williamson <awilliam@redhat.com>
Date: Wed, 20 Mar 2024 09:10:53 -0700
Subject: [PATCH] cloud: set Google root size to 10 GB and EC2 back to 5 GB

It's the *Google* image that's required to have a 10 GB root
for performance reasons, not the EC2 image, as the comment says,
but the change was inadvertently applied to the EC2 image not
the Google one. This means our Google image is slow and our EC2
images are failing to be published as AMIs.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
---
 teams/cloud/cloud.xml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/teams/cloud/cloud.xml b/teams/cloud/cloud.xml
index c3d84bc..a5a30f9 100644
--- a/teams/cloud/cloud.xml
+++ b/teams/cloud/cloud.xml
@@ -57,8 +57,7 @@
 		      rootfs_label="fedora"
 		      >
 			<bootloader name="grub2" timeout="0"/>
-			<!-- GCP engineers have told us the disk images have bad performance if they are anything less than 10G -->
-			<size unit="G">10</size>
+			<size unit="G">5</size>
 			<systemdisk>
 				<volume name="@root=root"/>
 				<volume name="home" parent="/"/>
@@ -78,7 +77,8 @@
 		      rootfs_label="fedora"
 		      >
 			<bootloader name="grub2" timeout="0"/>
-			<size unit="G">5</size>
+			<!-- GCP engineers have told us the disk images have bad performance if they are anything less than 10G -->
+			<size unit="G">10</size>
 			<systemdisk>
 				<volume name="@root=root"/>
 				<volume name="home" parent="/"/>