I will remove Internet2 support from MirrorManager in the next few weeks.
The main reason is, that the source for the Internet2 routing tables does not exist any more: http://routes.net.internet2.edu/
It changed a couple of years ago and it seems Fedora was one of the only users of that data. They fixed it for us, but the latest ticket I opened to access this information was closed with "This service was decomd".
I do not think that the removal of Internet2 support for our users will be noticed at all. Removing Internet2 will remove some complexity from the code and using ASN and GeoIP should still provide a reasonably close mirror for most of out users.
I will start to update the different components to not expose and rely on Internet2 information any more in the next couple of weeks.
Let me know if you see any major problems in removing Internet2 support from MirrorManager.
Adrian
On Mon, 2022-05-23 at 12:40 +0200, Adrian Reber wrote:
I will remove Internet2 support from MirrorManager in the next few weeks.
The main reason is, that the source for the Internet2 routing tables does not exist any more: http://routes.net.internet2.edu/
It changed a couple of years ago and it seems Fedora was one of the only users of that data. They fixed it for us, but the latest ticket I opened to access this information was closed with "This service was decomd".
I do not think that the removal of Internet2 support for our users will be noticed at all. Removing Internet2 will remove some complexity from the code and using ASN and GeoIP should still provide a reasonably close mirror for most of out users.
Sounds like a really good plan to me, especially around removing complexity in the mirror selection. I cannot think of any reason the removal should adversely affect users at this point since as you said, the routing information is not exactly available anymore.
I would be interested if there are any mirror admins that are using Internet2 that would be able to comment on the health of I2 in 2022.
I will start to update the different components to not expose and rely on Internet2 information any more in the next couple of weeks.
Let me know if you need/want any help testing or working on the removal. I'm happy to assist however it would be helpful.
--Neil
Let me know if you see any major problems in removing Internet2 support from MirrorManager.
Adrian _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro... Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
/me sheds a small tear. That was a clever hack in the days before ubiquitous 1Gb+ connections and when so many supporters were on Internet2. I agree it's no longer meaningful. Thanks for recognizing the bitrot and excising it! -Matt
On Mon, May 23, 2022 at 8:45 AM Neil Hanlon neil@resf.org wrote:
On Mon, 2022-05-23 at 12:40 +0200, Adrian Reber wrote:
I will remove Internet2 support from MirrorManager in the next few weeks.
The main reason is, that the source for the Internet2 routing tables does not exist any more: http://routes.net.internet2.edu/
It changed a couple of years ago and it seems Fedora was one of the only users of that data. They fixed it for us, but the latest ticket I opened to access this information was closed with "This service was decomd".
I do not think that the removal of Internet2 support for our users will be noticed at all. Removing Internet2 will remove some complexity from the code and using ASN and GeoIP should still provide a reasonably close mirror for most of out users.
Sounds like a really good plan to me, especially around removing complexity in the mirror selection. I cannot think of any reason the removal should adversely affect users at this point since as you said, the routing information is not exactly available anymore.
I would be interested if there are any mirror admins that are using Internet2 that would be able to comment on the health of I2 in 2022.
I will start to update the different components to not expose and rely on Internet2 information any more in the next couple of weeks.
Let me know if you need/want any help testing or working on the removal. I'm happy to assist however it would be helpful.
--Neil
Let me know if you see any major problems in removing Internet2 support from MirrorManager.
Adrian
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to
infrastructure-leave@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro... Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
infrastructure@lists.fedoraproject.org