Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -106,3 +106,41 @@
106	106	The format of a Swift url to submit to FTS is ##swifts:~/~/ + storage name + container name + (folder name(s)) + object name##.
107	107
108	108	For example, ##swifts:~/~/swift.bsc.es/testcontainer/data.txt## locates the data.txt file in container testcontainer in the BSC object store.
	109	+
	110	+=== Submit a Swift-to-Swift transfer ===
	111	+
	112	+We give instructions in this manual for Swift-to-Swift data transfer only, because the current available Fenix archival repositories are Swift object stores. For other types of storage, users may refer to the official FTS guide [[FTS3 Documentation - CERN>>url:https://fts3-docs.web.cern.ch/fts3-docs/]].
	113	+
	114	+For Swift-to-Swift transfer, the user has to specify OS project ids which indicate the data source and destinations.
	115	+
	116	+Users can find the project id by either:
	117	+
	118	+1. using the command ##openstack project list## with the Openstack CLI client.
	119	+1. login to the Openstack dashboard, go to //Identity -> Projects//.
	120	+For example, on [[https:~~/~~/ncloud.bsc.es>>url:https://ncloud.bsc.es]]:
	121	+[[image:image-20230412091641-1.png]]
	122	+and on [[https:~~/~~/castor.cscs.ch>>url:https://castor.cscs.ch]]:
	123	+[[image:image-20230412091702-2.png]]
	124	+
	125	+To transfer from/to the object storages at JSC or CSCS, the user also needs to specify an OS token at the moment.
	126	+
	127	+* For **JSC** users, please refer to the documentation [[here>>url:https://apps.fz-juelich.de/jsc/hps/just/object-storage.html#user-environment-preparation]] to create the ##rc## file, then do ##openstack token issue##, your OS token will be shown in the “id” field.
	128	+* For **CSCS** users, the easiest way to get an OS token is to follow the guide on this GitHub page: [[https:~~/~~/github.com/eth-cscs/openstack/tree/master/cli>>url:https://github.com/eth-cscs/openstack/tree/master/cli]]. When authenticated, the OS token is saved as environment variable ##OS_TOKEN##.
	129	+* If the user would like to specify the OS token for **BSC** her/himself (which is not necessary), guidance is provided here: [[https:~~/~~/bsc.es/supportkc/docs-ncloud/access#cli-access>>url:https://bsc.es/supportkc/docs-ncloud/access#cli-access]].
	130	+
	131	+Below is an example of submitting the transfer with CLI:
	132	+
	133	+##$fts-rest-transfer-submit \
	134	+-s https:~/~/fts.bsc.es:8446/ \##
	135	+##~-~-access-token $tok \##
	136	+##~-~-os-project-id “<source_project_id>:<dest_project_id>” \##
	137	+##~-~-os-token “<project_id>:<corresponding_os_token>” \##
	138	+##swifts:~/~/object.cscs.ch/<container_name>/<object_name> \##
	139	+##swifts:~/~/swift.bsc.es/<container_name>/<object_name>##
	140	+
	141	+### Using endpoint: https:~/~/fts.bsc.es:8446
	142	+# REST API version: 3.10.0  ##
	143	+##Job successfully submitted.##
	144	+##Job id: 532086a8-30a9-11eb-b0da-fa163e1833c1##
	145	+
	146	+Users can use multiple ##~-~-os-token## to specify OS tokens for different projects.