Pelican v7.4.0 — Pelican Platform

Release

Highlights

[Client] Introduced pelican object get and pelican object put to specify a get or put rather than just running pelican object copy. #259
[Client] Fixed issue where the stash_plugin file-transfer plugin was not reporting proper upload bytes. #510
[Client] Fixed issue with progress bars not outputting properly with debug logs for recursive uploads/downloads #402
[Client] Fixed issue where stash_plugin was not working with environment variable-based configuration #508
[Client] pelican object copy now doesn’t rely on topology for PUTs, it gets the endpoint by querying the director #504

[Director] Introduced GeoIP Overrides that allow a director to pin IP ranges to a particular lat/long. #496
[Registry] Introduced web-ui for registry that allows users to register their namespace through web interface. #264
[Director] Added federation discovery endpoint to director. #417
[General] Added topology components to Prometheus health metrics. #494
[Cache] Added Admin approval to caches before they can advertise to director #439
[Registry] Added support to use CILogon to login to registry UI #355
[Registry] Deprecated Federation.NamespaceUrl which will be removed in the next major release #388
[General] Web-ui now outputs more detailed error messages if login fails #424
[Origin] Basic S3 origin functionality has been restored #592
[Cache] Fixed issue where caches were logging sensitive information #604
[Origin] Boolean flag added to starting origins indicating if they are writable or not (default is true) #507

Fix duplicated director file transfer tests
Added three Prometheus metrics recording number of test file transfers the director issues:
- pelican_director_total_ftx_test_suite: total number of test suite the director issued, which means how many times the director started a new test go routine to an origin
- pelican_director_active_ftx_test_suite: the number of active test suite running per origin, which should be 1, meaning only one active test go routine is running per origin. This will be a good indicator of whether the director is doing wild things.
- pelican_director_total_ftx_test_runs: the total number of test file transfer runs per origin. i.e. How many tests in total were ran per origin. We run A test per 15s (by default) per origin, so this is also a good indicator of whether the origin is up or whether the director is going crazy. It comes with label status and report_status with value Success and Failure indicating if the transfer itself was successful and the reporting to the origin was successful.

Fix the issue where Pelican won't exit main process if error group goroutine returns error, unless an error returns in the main goroutine
Fix the panic at the director when a cache advertise itself to the director, as we didn't have the case for cache when doing version compatibility check
Improve logging at program exit to be consistent.
Improve cache error group, remove duplicated exit handler that root.go already had.