lustrequota: Use github mirror for fetching lustre source code

[Martin-Rehr]

git access (port 9418) to git://git.whamcloud.com/fs/lustre-release.git has been blocked for over two weeks now[1], therefore we have to switch to the github mirror[2]
[1]

$> > nmap -p 9418 git.whamcloud.com
Starting Nmap 7.97 ( https://nmap.org ) at 2025-08-26 16:57 +0200
Nmap scan report for git.whamcloud.com (104.21.48.246)
Host is up (0.0055s latency).
Other addresses for git.whamcloud.com (not scanned): 2606:4700:3030::ac43:8af5 2606:4700:3031::6815:30f6 172.67.138.245

PORT STATE SERVICE
9418/tcp filtered git

Nmap done: 1 IP address (1 host up) scanned in 0.76 seconds

[2] https://github.com/lustre/lustre-release

[jonasbardino]

Please remove these TODOs if cleanup has been handled with the rm below.

[jonasbardino]

I didn't follow recent lustre announcements but don't have any issues with using github sources if that is the new official channel.
If we only need releases they are also available at https://github.com/lustre/lustre-release/tags

[jonasbardino]

I think rebasing with master should fix the CI build checks now that PR #126 is merged, btw.

[Martin-Rehr]

I didn't follow recent lustre announcements but don't have any issues with using github sources if that is the new official channel. If we only need releases they are also available at https://github.com/lustre/lustre-release/tags

The official git repo is still git.whamcloud.com, I haven't managed to find any explanation why they blocked the git port.

[Martin-Rehr]

I think rebasing with master should fix the CI build checks now that PR #126 is merged, btw.

?

[jonasbardino]

I didn't follow recent lustre announcements but don't have any issues with using github sources if that is the new official channel. If we only need releases they are also available at https://github.com/lustre/lustre-release/tags

The official git repo is still git.whamcloud.com, I haven't managed to find any explanation why they blocked the git port.

Alright, could be something to search on whatever announce mailing lists or explicitly ask about. Yet, going to the corresponding http URL hits a CloudFlare "are you human check", so one could imagine that their main git repo is/was overloaded from bots.

[jonasbardino]

I think rebasing with master should fix the CI build checks now that PR #126 is merged, btw.

?

The github action checks failed on rocky8 as you can see e.g. at https://github.com/ucphhpc/docker-migrid/actions/runs/17243837109 .
The fix for that issue is in the repo now so when you rebased this branch to the current master branch it also made the checks succeed here.

[Martin-Rehr]

I didn't follow recent lustre announcements but don't have any issues with using github sources if that is the new official channel. If we only need releases they are also available at https://github.com/lustre/lustre-release/tags

The official git repo is still git.whamcloud.com, I haven't managed to find any explanation why they blocked the git port.

Alright, could be something to search on whatever announce mailing lists or explicitly ask about. Yet, going to the corresponding http URL hits a CloudFlare "are you human check", so one could imagine that their main git repo is/was overloaded from bots.

Yep, that is also what @hhhappe and I are guessing but neither of us has been able to find any official announcement.