Difference between revisions of "RucioRSE"
From GridPP Wiki
(→Setup) |
(→Setup) |
||
Line 51: | Line 51: | ||
rucio-admin rse add-attribute --rse <RSE Name> --key <The attribute which needs to be added> --value <the value to be assigned to that attribute> | rucio-admin rse add-attribute --rse <RSE Name> --key <The attribute which needs to be added> --value <the value to be assigned to that attribute> | ||
Then the protocol can be added: | Then the protocol can be added: | ||
− | rucio-admin rse add-protocol --hostname <hostname> --scheme <scheme> --prefix <prefix> --domain-json <the above default as a string, or echo $(path to json | + | rucio-admin rse add-protocol --hostname <hostname> --scheme <scheme> --prefix <prefix> --domain-json <the above default as a string, or echo $(< path/to/jsonfile.json)> --impl <IMPL> --port <port> <RSE Name> |
Revision as of 09:52, 15 April 2021
Introduction
Setting up Rucio to recognise your RSE is the first step for integration.
Setup
To set up your RSE to join Rucio you will need to provide a Rucio admin with the following information:
Settings: ========= availability_delete: True <- This is default, change if needed availability_read: True <- This is default, change if needed availability_write: True <- This is default, change if needed credentials: None <- This is default, change if needed delete_protocol: 1 <- This is default, change if needed deterministic: True <- This is default, change if needed domain: [u'lan', u'wan'] <- This is default, change if needed lfn2pfn_algorithm: identity <- This is default, change if needed qos_class: None <- This is default, change if needed read_protocol: 1 <- This is default, change if needed rse: <Name of your RSE> rse_type: DISK <- This is default, change if needed sign_url: None <- This is default, change if needed staging_area: False <- This is default, change if needed third_party_copy_protocol: 1 <- This is default, change if needed verify_checksum: True <- This is default, change if needed volatile: False <- This is default, change if needed write_protocol: 1 <- This is default, change if needed Attributes: =========== fts: <The URL for your FTS service> istape: <is your RSE a tape storage? True/False> lfn2pfn_algorithm: identity <- This is default, change if needed pnn: <This is the same as your RSE name> Protocols: ========== domains: {u'wan': {u'read': 1, u'write': 1, u'third_party_copy': 1, u'delete': 1}, u'lan': {u'read': 0, u'write': 0, u'delete': 0}} <- change this if it is not your setting extended_attributes: <fill in as required> hostname: <your RSE host name> impl: <Your RSE impl> port: <Your port> prefix: <your RSE prefix> scheme: <Your RSE ftp Scheme>
IF your scheme is srm, then you will need to provide the folling inforamtion as well: web_service_path: <Your RSE web service path> space-token: <Your RSE space-token>
These settings will then be placed onto the Rucio instance via the Rucio admin using the following:
rucio-admin rse add <RSE Name>
Once this is done the following will need to be done for all attributes:
rucio-admin rse add-attribute --rse <RSE Name> --key <The attribute which needs to be added> --value <the value to be assigned to that attribute>
Then the protocol can be added:
rucio-admin rse add-protocol --hostname <hostname> --scheme <scheme> --prefix <prefix> --domain-json <the above default as a string, or echo $(< path/to/jsonfile.json)> --impl <IMPL> --port <port> <RSE Name>