Orig issue: https://pagure.io/fedora-infrastructure/issue/9920
From that issue:
We run Fedora CI on AWS and we run of course all our infra on Fedora (dogfooding FTW). Seems all generated AWS images are built with MBR partition table, what imposes a limit of 2TB as maximal drive size. We would benefit from larger drives, due to some of the tests can consume a lot of disk space (like rpminspect). We would like to ask if it would make sense to generate the images with GPT partition table instead, which would make cloud images from Fedora also usable for such greedy use cases as we have. Volume constraints are described for example here: https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/volume_constraints.html
CC: @mvadkert
A related issue: #309
I don't see a problem with moving to GPT, especially now that we can just do hybrid BIOS+UEFI images for all cloud providers now, since AWS now supports it according to @davdunc.
Metadata Update from @ngompa: - Issue tagged with: AWS, Azure, GCP
Metadata Update from @ngompa: - Issue untagged with: Azure, GCP
Metadata Update from @ngompa: - Issue tagged with: meeting
It was agreed in the 2021-05-25 meeting that @davdunc will do this:
* Move Fedora cloud images to GPT (Eighth_Doctor, 16:24:55) * LINK: https://pagure.io/cloud-sig/issue/330 (Eighth_Doctor, 16:25:01) * LINK: https://pagure.io/cloud-sig/issue/309 (Eighth_Doctor, 16:26:16) * AGREED: Fedora Cloud images will move to GPT and be configured as hybrid BIOS+UEFI images (Eighth_Doctor, 16:30:57) * ACTION: davdunc will work on a Change proposal for switching to GPT with hybrid BIOS+UEFI (Eighth_Doctor, 16:32:17)
The pre-requisite Change has been proposed: https://fedoraproject.org/wiki/Changes/InstallGPTwithKickstart
Metadata Update from @ngompa: - Issue untagged with: meeting - Issue assigned to davdunc
I think this is completed - we didn't require the GPT change we expected. Brian Lane walked us through it and the change was unnecessary. The change proposal with withdrawn. Please reopen if I am not correct.
Metadata Update from @davdunc: - Issue close_status updated to: invalid - Issue status updated to: Closed (was: Open)
Metadata Update from @ngompa: - Issue status updated to: Open (was: Closed)
Metadata Update from @ngompa: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Closed with the correct status. :)
Login to comment on this ticket.