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>
This commit is contained in:
parent
319e5e8153
commit
08243564f3
@ -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="/"/>
|
||||
|
Loading…
Reference in New Issue
Block a user