Globus v4 to v5: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
= | The Globus file transfer tool which we are using on our servers is evolving. On December 18th 2023, the version 4 will reach its end of life. This affects in particular users of shared endpoints (named shared collections in Globus version 5). You may have received a message from Globus containing the following information: | ||
{{Warning|title=Message sent by Globus|content= | |||
GCS Version 4 will be discontinued on December 18, 2023. If you have not yet migrated your Globus Connect Server v4 deployment or updated your applications to support Globus Connect Server v5, we urge you to do so now. | |||
The original announcement was made in July 2023: https://www.globus.org/blog/globus-connect-server-v4-will-be-deprecated-july-31-2023}} | |||
= Timeline = | |||
Deadline for GCSv4 operation - December 18, 2023 | Deadline for GCSv4 operation - December 18, 2023 | ||
Deadline for migration - December 8, 2023 (Site-specific) | Deadline for migration - December 8, 2023 (Site-specific) | ||
= Affected systems = | |||
* | * Cedar: The endpoint computecanada#cedar-dtn (version 4) will be decommissioned and the endpoint computecanada#cedar-globus (version 5) will be used instead | ||
* | * Béluga: The endpoint computecanada#beluga-dtn will be migrated from version 4 to version 5 | ||
* Graham, Narval: Their respective endpoints already use version 5 | |||
* Niagara: The endpoint will be upgraded to version 5. No action required from user as Globus shared endpoints are not allowed. | |||
== | = Details = | ||
== Cedar == | |||
For Cedar, the endpoint computecanada#cedar-dtn uses version 4 of Globus and will be discontinued on December 15th 2023. Before this date, you need to recreate your shared endpoints using the endpoint computecanada#cedar-globus, which uses version 5. | |||
== | == Béluga == | ||
For Béluga, the existing Globus v4 endpoint will be upgraded to Globus v5 during the scheduled maintenance on November 28th. Most shared endpoints, which use the Compute Canada identity provider, will be migrated automatically. However, some endpoints were created using third party identity providers and will need to be recreated. | |||
Revision as of 13:41, 14 November 2023
The Globus file transfer tool which we are using on our servers is evolving. On December 18th 2023, the version 4 will reach its end of life. This affects in particular users of shared endpoints (named shared collections in Globus version 5). You may have received a message from Globus containing the following information:
GCS Version 4 will be discontinued on December 18, 2023. If you have not yet migrated your Globus Connect Server v4 deployment or updated your applications to support Globus Connect Server v5, we urge you to do so now. The original announcement was made in July 2023: https://www.globus.org/blog/globus-connect-server-v4-will-be-deprecated-july-31-2023
Timeline[edit]
Deadline for GCSv4 operation - December 18, 2023 Deadline for migration - December 8, 2023 (Site-specific)
Affected systems[edit]
- Cedar: The endpoint computecanada#cedar-dtn (version 4) will be decommissioned and the endpoint computecanada#cedar-globus (version 5) will be used instead
- Béluga: The endpoint computecanada#beluga-dtn will be migrated from version 4 to version 5
- Graham, Narval: Their respective endpoints already use version 5
- Niagara: The endpoint will be upgraded to version 5. No action required from user as Globus shared endpoints are not allowed.
Details[edit]
Cedar[edit]
For Cedar, the endpoint computecanada#cedar-dtn uses version 4 of Globus and will be discontinued on December 15th 2023. Before this date, you need to recreate your shared endpoints using the endpoint computecanada#cedar-globus, which uses version 5.
Béluga[edit]
For Béluga, the existing Globus v4 endpoint will be upgraded to Globus v5 during the scheduled maintenance on November 28th. Most shared endpoints, which use the Compute Canada identity provider, will be migrated automatically. However, some endpoints were created using third party identity providers and will need to be recreated.