#285 update target size of Cloud images
Opened 6 years ago by kparal. Modified 2 years ago

Hello,

QA is trying to consolidate target sizes for all images built by Fedora into a single document that we can easily check, in a response to one of blocking images being oversize again [1]. The document of choice is this wiki page [2]. In a newly added column, the target size of each release-blocking image will be documented. (It can also contain target sizes of non-blocking images, but our major focus is on the blocking ones, of course). The target size will be a blocker for Fedora Final releases.

The target sizes for Cloud images are currently considered [3] as follows:

Cloud Base 700 MiB

We'd like you to think over whether this is still correct, decide on new numbers if needed, and then write it down into the document [2]. (If you decide to change it in the future, notifying us at the same time is very appreciated.)

We'd like to avoid the situation when the image goes oversize and the target size is simply bumped, because it adds delays to the release process. So please think ahead and choose a size that you really want to keep and block on it (You can of course also choose to have no=unlimited target size).

Thank you.

[1] https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/NEXM7VO27CYSMMKFOKWNGMTTWVF4MM43/
[2] https://fedoraproject.org/wiki/Releases/28/ReleaseBlocking
[3] https://fedoraproject.org/wiki/QA:Testcase_Mediakit_ISO_Size#Expected_Results


I think we could make this anywhere from 300 MiB to 600 MiB across the board as a warning that something's wrong.

Fedora-Cloud-Base-Rawhide-20210722.n.0.x86_64.raw.xz
content-length: 294046288
280 MiB

Fedora-Cloud-Base-Rawhide-20210722.n.0.x86_64.qcow2
content-length: 378929152
361 MiB

Fedora-Cloud-Base-Vagrant-Rawhide-20210722.n.0.x86_64.vagrant-libvirt.box
content-length: 369604900
352 MiB

Fedora-Cloud-Base-Vagrant-Rawhide-20210722.n.0.x86_64.vagrant-virtualbox.box
content-length: 379156480
361 MiB

aarch64 is in the same ballpark

Metadata Update from @chrismurphy:
- Issue assigned to chrismurphy

2 years ago

I'd like to know if we exceed 400MB, with our hard limit remaining 700MB.

I forget if we have separate soft and hard fail limits. @kparal @adamwill ?

not at present, no, all images specify a single size and the test is a hard fail on that.

Login to comment on this ticket.

Metadata