We, a.k.a. JP-KEK-CRC-02 (1), will turn two protocols off, such as SRM and GridFTP, as scheduled below.
*1 https://goc.egi.eu/portal/index.php?Page_Type=Site&id=268
December 2024:
Firstly, we will turn off the GridFTP protocol for all transfer nodes.
If you now access srm://kek2-se01.cc.kek.jp:8444/srm/managerv2?SFN=/ilc/path/to/file, SRM returns the GridFTP Transfer URL (TURL) like gsiftp://data-transfer-node.cc.kek.jp:2811/ilc/path/to/file by default.
SRM will then return HTTPS TURL like https://data-transfer-node.cc.kek.jp/ilc/path/to/file by default from the date above, December 2024. You can test how this affects you with gfal2 client utilities like:
gfal-xxx --definition "SRM PLUGIN:TURL_3RD_PARTY_PROTOCOLS=https" srm://kek2-se01.cc.kek.jp:8444/srm/managerv2?SFN=/ilc/path/to/file
Which returns you an HTTPS TURL like:
https://data-transfer-node.cc.kek.jp/ilc/path/to/file.
March 2025:
Secondly, we will turn off the SRM protocol after dropping the GridFTP protocol off.
This means we will shut all frontend nodes (SRM-responder) behind the hostname kek2-se01.cc.kek.jp, i.e. kek2-storm01-frontend-1.cc.kek.jp and kek2-storm01-frontend-2.cc.kek.jp.
In other words, the HTTPS transfer protocol will be the only way to access the data on the storage element, i.e., https://ilc-webdav.cc.kek.jp/ilc/path/to/file or davs://ilc-webdav.cc.kek.jp/ilc/path/to/file from the date above, March 2025.
Kind regards,
Go Iwai, KEK/CRC
Answers in advance to expected questions:
1. Regarding X.509 to OIDC token authNZ migration, which may differ from this matter. I would take another opportunity to work on this.
2. Regarding the WLCG Tape REST API, we do not yet plan to provide the API for accessing the tape backend.
3. Regarding the SE migration, we do not or will not migrate to other implementations. We will stay working with StoRM before and after the migration.
