Just need to adjust the "'arches': ['aarch64', 'ppc64le', 's390x', 'x86_64']," line in the various pungi configs in https://pagure.io/pungi-fedora

Describe the issue
Currently cloud images in vmdk format are produced for all arches, but they make sense only for x86/x86_64. Please update compose configuration accordingly.

we started created the VMDKs because it saves a lot of bandwidth to upload a vmdk to amazon AWS versus a raw image. Since we upload to AWS for x86_64 and aarch64, we'd want to keep it for those two arches I think.

we started created the VMDKs because it saves a lot of bandwidth to upload a vmdk to amazon AWS versus a raw image. Since we upload to AWS for x86_64 and aarch64, we'd want to keep it for those two arches I think.

Where's that documented? Why is bandwidth a problem?

Why don't we have ppc64le and s390x images uploaded into IBM Cloud for POWER and Open Mainframe projects?

Why don't we have ppc64le and s390x images uploaded into IBM Cloud for POWER and Open Mainframe projects?

this is work in progress

we started created the VMDKs because it saves a lot of bandwidth to upload a vmdk to amazon AWS versus a raw image. Since we upload to AWS for x86_64 and aarch64, we'd want to keep it for those two arches I think.

Where's that documented? Why is bandwidth a problem?

IIUC uploading a raw image uploads the full size of the disk (non-sparse). Uploading the stream-optimized VMDK allows it to be uploaded sparse so you save a ton of bandwith and also time. I don't have any documentation for this. It's mostly advice lended from the previous CoreOS container linux team and also anecdotal evidence from executing the uploads and observing time/bandwidth savings. We could ask @sayanchowdhury from his fedimg development about this as well.

I'm not aware of any specific documentation on our end (probably AWS has some) but @dustymabe is right. We upload VMDKs because the sparseness improves upload time.

@dustymabe @sharkcz Are you okay with removing ppc64le and s390x since we only uploading the x86_64 and aarch64 images only? We can get back to them once the work is done.

works for me. It is worth noting that we are creating the vmdk images so that we can upload them to AWS but right now our migration to plume (away from fedimg) is in progress, so we're not actually using them yet.

yes, please remove the ppc64le/s390x vmdk images

From the releng meeting today:

#info mboddu will remove ppc64le and s390x cloud images since we only uploading the x86_64 and aarch64 images only

I will update the configs later today.

Fixed by https://pagure.io/pungi-fedora/pull-request/837

Closing as the PR is now merged.