Releases: rucio/containers
Releases · rucio/containers
webui-34.1.0
What's Changed
Full Changelog: 34.6.0...webui-34.1.0
Rucio 34.6.0 minor release
Clarify which UI is the one being currently used in deprecation notice
Rucio 34.5.0 minor release
ui: add option to configure `RemoteIPProxyProtocol` directive In deployment scenarios where the Rucio UI sits behind a proxy ( a loadbalancer or another reverse proxy), the client information must be handled by the UI container's httpd process. This PR configures the `RemoteIPProxyProtocol` directive to enable the UI do to so
Rucio 34.4.3 patch release
Testing: Modify filename of requirements file; rucio#6767
Rucio 34.4.2 patch release
FTS: Remove [fts3] from fts3restconfig, on advice from FTS team; #320
Rucio 34.4.1 patch release
FTS: Add OAuth2=True in config; rucio#6774
Rucio 34.4.0.post1 release
This release is used to rebuild the containers for the fts-cron
scripts
Rucio 34.4.0 minor release
dev, ssh: update rclone to latest
Rucio 34.3.0 minor release
ui: fix trailing :80 inservername
Rucio 34.2.0 minor release
daemons/server: Add Grid CAs to the system trust The origin of the /etc/grid-security directory appears to be Globus. GFAL uses it transparently, but all other native system utilities and libraries do not. This commits adds the Grid CAs to the system trust at the time the container starts, when applicable. This will be important for the Rucio components that: * Connect directly to the RSEs (Automatix, Dark Reaper, Reaper) * Communicate with FTS (Cleaner, Poller, Submitter, and the Rucio servers) The /etc/grid-security directory does not exist by default; it has to be populated externally and mounted in the container with extraHostPathMounts.