#132 Fedora AMIs should use corresponding s3 mirrors
Opened 3 years ago by voltagex. Modified 2 years ago

Currently, Fedora AMIs on Amazon EC2 are still using the mirror list. This results in slow download speeds for dnf and a sub-par experience

https://lists.stg.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/thread/IK4RCCC7W5PRFJG5GPTQUUU6DOMYT34N/ is the best list of these mirrors I could find.

Changing this would require either
changing the template that builds the AMIs for each region
making the mirrorlist service smart enough to detect requests from AWS and send them to the correct region


The mirror service is actually smart enough. We used to have EC2 mirrors, but it was very, very slow to sync to them, and I'm told not enough people were using them to make it worthwhile. If we can demonstrate that they'd really be useful, maybe we can change that.

I guess part of the problem is that, for example, X-based games are very unlikely to be wanted in the cloud, but we don't have a smart way of just syncing the likely stuff to S3, resulting in a lot of waste.

The rpm-ostree update system used by Atomic is designed to work with object store systems like S3, and should also be able to use S3 with minimal change. And that is a subset, so I think maybe that's a good place to start.

So those hosts aren't used any more? One of the issues I found was it was really hard to find accurate information about the state of the Fedora AMIs.

Replying to [comment:2 voltagex]:

So those hosts aren't used any more? One of the issues I found was it was really hard to find accurate information about the state of the Fedora AMIs.

The S3 mirrors are used for EPEL but not Fedora OS, I think. And I'm not sure they're in all regions.

I agree there's definitely a gap in information. (Honestly, help wanted.)

I think we definitely do want to mirror container images into EC2, as part of https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service

(Rationale — that's a selected subset of Fedora content which is likely to be useful and relevant in EC2, which is hard to do with the package collection.)

there are plans to mirror content in s3 again which should solve this issue: https://pagure.io/fedora-infrastructure/issue/6022

Metadata Update from @dustymabe:
- Issue tagged with: infra, waiting

2 years ago

Login to comment on this ticket.

Metadata