#687 vault.centos.org mirror for CentOS CI
Closed: Fixed with Explanation by mrc0mmand. Opened by mrc0mmand.

As mentioned in https://pagure.io/centos-infra/issue/680#comment-783663 having a mirror of the vault.centos.org repos could help with the load & stability. I'm not sure if we need everything, or just a subset - mainly source repos - since the other non-EOL stuff is already mirrored internally iirc.


I think https://pagure.io/centos-infra/issue/682 would likely be a solution for this ticket so I will close this in favour of that.

Feel free to reopen if I am mistaken

Metadata Update from @mobrien:
- Issue close_status updated to: Duplicate
- Issue status updated to: Closed (was: Open)

Metadata Update from @arrfab:
- Issue status updated to: Open (was: Closed)

Metadata Update from @arrfab:
- Issue tagged with: centos-ci-infra, centos-common-infra, feature-request, low-gain, low-trouble

I just had a look at this and while it would be possible, it would then rely on another "out of warranty" node in CI infra. So my question would be : since we moved the whole vault.centos.org setup to AWS Cloudfront, had you encountered any issue getting content from it ? (the DDoS issue we suffered from when you opened initial ticket is now gone)
Waiting for some feedback and eventually closing it , except if we really have ongoing issue (and using "out of warranty" node in ci infra needs also some "risk management" decision)

I just had a look at this and while it would be possible, it would then rely on another "out of warranty" node in CI infra. So my question would be : since we moved the whole vault.centos.org setup to AWS Cloudfront, had you encountered any issue getting content from it ? (the DDoS issue we suffered from when you opened initial ticket is now gone)
Waiting for some feedback and eventually closing it , except if we really have ongoing issue (and using "out of warranty" node in ci infra needs also some "risk management" decision)

Since the migration to cloudfront (and the following DDoS issue you promptly resolved) I haven't seen a single instance of the original issue, so I'm fine with closing this ticket, as it would indeed cause an unnecessary overhead (especially given the CI node wouldn't be under a warranty).

Thanks again for all the work on this!

Metadata Update from @mrc0mmand:
- Issue close_status updated to: Fixed with Explanation
- Issue status updated to: Closed (was: Open)

Log in to comment on this ticket.

Metadata