Skip to content

Conversation

@sbraz
Copy link
Contributor

@sbraz sbraz commented Feb 1, 2024

@jonathanspw does this look OK? I'm not a fan of the invalid DNS records for the names but I don't really have a better idea right now.

Our anycast IP is routed to 4 different locations. This is a follow-up to 02c8629.

@sbraz sbraz mentioned this pull request Feb 1, 2024
@jonathanspw
Copy link
Member

This looks perfect.

Long term I think being able to list multiple locations per mirror would solve the potential of having to use invalid names that you did here (but is the best solution right now).

I'm not 100% sure how the system will react to multiple mirrors listing a common ASN - once an ASN match is hit I don't recall if there is any further logic on them in the case of multiple matches. I believe we've had another recent "issue" with this. Going to hold off on merging this until I can revisit that and make sure this won't cause any issues for your users.

@jonathanspw
Copy link
Member

All of the file names need to end in .yml to be picked up by the system. It's why the existing single-mirror isn't showing up on the list.

@sbraz sbraz force-pushed the ovhcloud_mirror branch 2 times, most recently from 46714da to 1770a73 Compare February 2, 2024 12:54
Our anycast IP is routed to 4 different locations.
This is a follow-up to 02c8629.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants