Skip to content
Andre Sailer edited this page May 8, 2017 · 16 revisions

DMS

Important change: The values for registration and third party protocols have to be moved from Resources to Operation, and new lists are needed :

DataManagement/RegistrationProtocols # Comes from Resources/FileCatalogs
DataManagement/ThirdPartyProtocols # Comes from Resources/FileCatalogs
DataManagement/AccessProtocols
DataManagement/WriteProtocols

For the extensions, the Resource Helpers getRegistrationProtocols and getThirdPartyProtocols are replaced with methods (same name) in the DMSHelpers class

These lists can be overwritten at the level of a StorageElement, and they should be if it is a special case. For example, for LHCb, the OnlineRunDB storageElements needs to have "http" as WriteProtocols

RSS

There is a need to change the schema of the table SpaceTokenOccupancyCache (ResourceManagementDB).

  • Column Endpoint must be set to varchar(128)
ALTER TABLE SpaceTokenOccupancyCache MODIFY COLUMN `Endpoint` varchar(128) NOT NULL DEFAULT 'NULL';

Migration to GFAL2

The underlying library for protocol should now be GFAL2. In order for it to work, 2 environment variables need to be present: GFAL_CONFIG_DIR and GFAL_PLUGIN_DIR. They need to be both on the client and on the server part (bashrc). If installed via the LCGBundle, the paths should look like:

export GFAL_CONFIG_DIR=/opt/dirac/pro/Linux_x86_64_glibc-2.12/etc/gfal2.d
export GFAL_PLUGIN_DIR=/opt/dirac/pro/Linux_x86_64_glibc-2.12/lib/gfal2-plugins/

In order to actually use it, you need to change your CS: the PluginName of your SEs should be GFAL2_SRM2 instead of SRM2. Similar for GFAL2_XROOT.

CAUTION The low level gfal and gfal2 libraries are incompatible. In practice, this means that you have to migrate ALL your SEs at once. You cannot declare in the CS SEs with gfal based plugins, and others with gfal2 based plugins.

[TECHNOLOGY PREVIEW]

Support for stomp MQs

[TECHNOLOGY PREVIEW]

TS Metafilters: https://github.com/DIRACGrid/DIRAC/pull/3180

Clone this wiki locally