Rucio - Revision history

Admin: /* Make a rucio request on T2B as a user */

2025-08-12T11:36:12Z

Make a rucio request on T2B as a user

← Older revision		Revision as of 11:36, 12 August 2025
Line 28:		Line 28:
	- in rucio, a transfer is called a rule. In order to create a rule:		- in rucio, a transfer is called a rule. In order to create a rule:
	<pre>		<pre>
	rucio add~~-rule~~ cms:/CMS/DATA/SET/NAME 1 T2_MY_SITE		rucio rule add cms:/CMS/DATA/SET/NAME 1 T2_MY_SITE
	rucio add~~-rule~~ cms:/CMS/DATA/SET/NAME#BLOCK-NAME 1 T2_MY_SITE		rucio rule add cms:/CMS/DATA/SET/NAME#BLOCK-NAME 1 T2_MY_SITE
	</pre>		</pre>

Line 87:		Line 87:
	</pre>		</pre>
	More info [https://twiki.cern.ch/twiki/bin/view/CMSPublic/RucioUserDocsRules here]		More info [https://twiki.cern.ch/twiki/bin/view/CMSPublic/RucioUserDocsRules here]


	=== Information for the T2B admins ===		=== Information for the T2B admins ===

Admin at 13:50, 1 February 2023

2023-02-01T13:50:37Z

← Older revision		Revision as of 13:50, 1 February 2023
Line 1:		Line 1:
			== Rucio instructions at T2B ==

			=== Introduction ===

	Rucio web requests are handled via https://cms-rucio-webui.cern.ch/r2d2/request		Rucio web requests are handled via https://cms-rucio-webui.cern.ch/r2d2/request

Line 9:		Line 13:
	scope: in our case the scope is cms.		scope: in our case the scope is cms.
	</pre>		</pre>

	~~If you want to make a request (rule in rucio), follow the following tuturial.~~



	~~This are basic instructions on rucio.~~

	Find the full info on: https://twiki.cern.ch/twiki/bin/view/CMSPublic/Rucio		Find the full info on: https://twiki.cern.ch/twiki/bin/view/CMSPublic/Rucio

	~~- You need to be~~ on ~~sl7 for the commands to work~~		=== Make a rucio request on T2B as a user ===

	- initialise the env:		- initialise the env:
Line 34:		Line 32:
	</pre>		</pre>

			- if there is a lot of data, add <pre>--asynchronous</pre>

	- ~~if there is~~ a ~~lot of data~~, ~~add <pre>--asynchronous</pre>~~		- as a user, rules need to be approved by the admins. This is done with 2 extra modifiers:
	~~- users can also request~~ rules~~, who are then~~ to be approved by the admins. This is done with 2 extra modifiers:
	<pre>--ask-approval</pre> and <pre>--lifetime (in seconds; for reference, 30 days is 2592000 seconds)</pre>		<pre>--ask-approval</pre> and <pre>--lifetime (in seconds; for reference, 30 days is 2592000 seconds)</pre>

	- check your rules:		==== Summary to request a rule as a user ====
			<pre>
			rucio add-rule cms:/CMS/DATA/SET/NAME 1 T2_BE_IIHE --asynchronous --ask-approval --lifetime 7776000
			(3 months)
			</pre>

			- now wait for the admins to approve your rule (usually within the day)

			==== Getting more info about your request ====
			- you can check your rules:
	<pre>		<pre>
	rucio list-rules --account $RUCIO_ACCOUNT List all the rules you have and their state		rucio list-rules --account $RUCIO_ACCOUNT List all the rules you have and their state
Line 80:		Line 87:
	</pre>		</pre>
	More info [https://twiki.cern.ch/twiki/bin/view/CMSPublic/RucioUserDocsRules here]		More info [https://twiki.cern.ch/twiki/bin/view/CMSPublic/RucioUserDocsRules here]


			=== Information for the T2B admins ===

	- requests can also be done for users, but I have not tested this.		- requests can also be done for users, but I have not tested this.

Admin at 15:23, 26 January 2021

2021-01-26T15:23:11Z

← Older revision		Revision as of 15:23, 26 January 2021
Line 107:		Line 107:
	source_for_used_space: rucio		source_for_used_space: rucio
	tier: 2		tier: 2
			</pre>

			You can see the data stored on a T2 by issuing the following command:
			<pre>
			rucio list-rse-usage T2_BE_IIHE --show-accounts
	</pre>		</pre>

Admin at 10:02, 21 January 2021

2021-01-21T10:02:50Z

← Older revision		Revision as of 10:02, 21 January 2021
Line 1:		Line 1:
	Rucio web requests are handled via https://cms-rucio-webui.cern.ch/r2d2/request		Rucio web requests are handled via https://cms-rucio-webui.cern.ch/r2d2/request

			Some Rucio vocabulary:
			<pre>
			RSE: Rucio Storage Element. In our case this is T2_BE_IIHE (and not the name of the se)
			DID: Data identyfier; is used to represent any set of file, dataset or container identifier. Data identifiers are unique over time. So they are never reused.
			rule: a data transfer. This includes DID, RSE and possible end time when the files are deleted again.
			lock: a tranfereed file
			scope: in our case the scope is cms.
			</pre>

	If you want to make a request (rule in rucio), follow the following tuturial.		If you want to make a request (rule in rucio), follow the following tuturial.

Admin at 09:51, 21 January 2021

2021-01-21T09:51:07Z

@@ Line 25: / Line 25: @@
 rucio add-rule cms:/CMS/DATA/SET/NAME#BLOCK-NAME 1 T2_MY_SITE
 </pre>
 - if there is a lot of data, add <pre>--asynchronous</pre>
 - users can also request rules, who are then to be approved by the admins. This is done with 2 extra modifiers:
@@ Line 33: / Line 35: @@
 rucio list-rules --account $RUCIO_ACCOUNT List all the rules you have and their state
 rucio rule-info [RULE_HASH] monitor the progress of your rule and any transfers it may have initiated
 </pre>
 More info [https://twiki.cern.ch/twiki/bin/view/CMSPublic/RucioUserDocsRules here]

Admin at 15:21, 20 January 2021

2021-01-20T15:21:50Z

← Older revision		Revision as of 15:21, 20 January 2021
Line 1:		Line 1:
			Rucio web requests are handled via https://cms-rucio-webui.cern.ch/r2d2/request


			If you want to make a request (rule in rucio), follow the following tuturial.



	This are basic instructions on rucio.		This are basic instructions on rucio.

Admin at 10:48, 20 January 2021

2021-01-20T10:48:16Z

← Older revision		Revision as of 10:48, 20 January 2021
Line 36:		Line 36:

	- datasets can be grouped into containers. This can be handy if several datasets are needed for a specific analysis. All of then can then also be removed together if the analysis is finished. This is done via rucio containers. More info [https://twiki.cern.ch/twiki/bin/view/CMSPublic/RucioUserDocsContainers here].		- datasets can be grouped into containers. This can be handy if several datasets are needed for a specific analysis. All of then can then also be removed together if the analysis is finished. This is done via rucio containers. More info [https://twiki.cern.ch/twiki/bin/view/CMSPublic/RucioUserDocsContainers here].


			At the moment of writing this document, these were the settings for our site:
			<pre>
			rucio list-rse-attributes T2_BE_IIHE
			T2_BE_IIHE: True
			cms_type: real
			country: BE
			ddm_quota: 3355000000000000
			fts: https://fts3-cms.cern.ch:8446
			lfn2pfn_algorithm: cmstfc
			pnn: T2_BE_IIHE
			quota_approvers: odevroed,rougny,srugovac
			reaper: True
			region: C
			rule_approvers: odevroed,rougny,srugovac
			source_for_total_space: static
			source_for_used_space: rucio
			tier: 2
			</pre>

Admin: Created page with "This are basic instructions on rucio. Find the full info on: https://twiki.cern.ch/twiki/bin/view/CMSPublic/Rucio - You need to be on sl7 for the commands to work - initia..."

2021-01-20T10:20:29Z

Created page with "This are basic instructions on rucio. Find the full info on: https://twiki.cern.ch/twiki/bin/view/CMSPublic/Rucio - You need to be on sl7 for the commands to work - initia..."

New page

This are basic instructions on rucio.

Find the full info on: https://twiki.cern.ch/twiki/bin/view/CMSPublic/Rucio

- You need to be on sl7 for the commands to work

- initialise the env:
<pre>
source /cvmfs/cms.cern.ch/cmsset_default.sh
source /cvmfs/cms.cern.ch/rucio/setup-py3.sh
voms-proxy-init -voms cms -rfc -valid 192:00
export RUCIO_ACCOUNT=`whoami`
</pre>

- in rucio, a transfer is called a rule. In order to create a rule:
<pre>
rucio add-rule cms:/CMS/DATA/SET/NAME 1 T2_MY_SITE
rucio add-rule cms:/CMS/DATA/SET/NAME#BLOCK-NAME 1 T2_MY_SITE
</pre>
- if there is a lot of data, add <pre>--asynchronous</pre>
- users can also request rules, who are then to be approved by the admins. This is done with 2 extra modifiers:
<pre>--ask-approval</pre> and <pre>--lifetime (in seconds; for reference, 30 days is 2592000 seconds)</pre>

- check your rules:
<pre>
rucio list-rules --account $RUCIO_ACCOUNT List all the rules you have and their state
rucio rule-info [RULE_HASH] monitor the progress of your rule and any transfers it may have initiated
</pre>
More info [https://twiki.cern.ch/twiki/bin/view/CMSPublic/RucioUserDocsRules here]

- requests can also be done for users, but I have not tested this.

- users can also be given [https://twiki.cern.ch/twiki/bin/view/CMSPublic/RucioSiteDocsQuotas quota’s]

- datasets can be grouped into containers. This can be handy if several datasets are needed for a specific analysis. All of then can then also be removed together if the analysis is finished. This is done via rucio containers. More info [https://twiki.cern.ch/twiki/bin/view/CMSPublic/RucioUserDocsContainers here].