On 05.06.2024 17:05, Adrian Reber via Mirror-admin wrote:
On Wed, Jun 05, 2024 at 07:57:34AM -0700, Kevin Fenzi wrote:
On Wed, Jun 05, 2024 at 11:04:19AM GMT, Adrian Reber via Mirror-admin wrote:
On Tue, Jun 04, 2024 at 12:40:35PM -0700, Kevin Fenzi wrote:
On Mon, Jun 03, 2024 at 12:05:17PM GMT, Jason L Tibbitts III wrote:
>>>> Aurelien Bompard abompard@fedoraproject.org writes:
There's been a very big mirrormanager update, if you're experiencing other troubles please report them here or on https://pagure.io/fedora-infrastructure/ and I'll have a look at them asap.
So after reading about report_mirror still being expected to work, I wonder if the information I had previously received about it no longer being useful has been superseded.
quick-fedora-mirror used to have code that would duplicate the functionality of report_mirror, but it was disabled because I was told that there was no point in running and in fact it was harmful to do so due to additional server load, and that I should simply rely on the crawler to keep things updated.
Are things different now? Should I restore that code and start using it? It simply built a payload in the expected format and call curl.
My understanding was that it was not useful for public mirrors, but was still useful for private mirrors, since private mirrors cannot be crawled to see if they are up to date or not.
However, I am unsure what exactly we do with that information.
I'll defer to one of the folks working on the code here...
It was disabled for non-private mirrors as it does not provide really correct results. For private mirrors it is currently the only way to let MirrorManager know which directories the private mirror has.
Ah yes, it does need to know which directories the private mirror has.
I wonder if we couldn't add this to the web interface? when you setup your private mirror, just add the directories there and adjust them over time if they change? Just a thought...
For high level directories that sounds doable, but if you are excluding certain arches it might be a lot of work to add everything to the web interface. Especially with a new release every 6 months it would need to be updated. Supporting regex would be a way around this.
Is there perhaps an opportunity to amend mirrormanager to instead of just doing via web ui, to expose a more full featured API that allows mirrors to manage their mirror content/state remotely?
I've had an idea for a while to add a REST-ish API to manage mirror content, as it would be extraordinarily useful for several projects that need to be able to manipulate site/host metadata.
--Neil
One private mirror using a caching system asked in a ticket to turn on "always up to date" for his mirror. That is something we could open to private mirrors, but also not useful if you want to exclude certain things.
Adrian
-- _______________________________________________ Mirror-admin mailing list -- mirror-admin@lists.fedoraproject.org To unsubscribe send an email to mirror-admin-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/mirror-admin@lists.fedoraproje... Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue