Loading README.txt +37 −42 Original line number Diff line number Diff line Loading @@ -140,7 +140,7 @@ The output should be something like this: Another thing you can do is to launch the 'dataArchiver.py' client. Launching the client without any argument will show you how to use it: client@28970a09202d:~$ python3 dataArchiverCli.py client@28970a09202d:~$ python3.9 dataArchiverCli.py NAME dataArchiverCli.py Loading @@ -165,8 +165,8 @@ DESCRIPTION The username must be the same used for accessing the transfer node. For example, if we want to perform a 'cold storage' request for a the 'curban' user, we do: client@28970a09202d:~$ python3 dataArchiverCli.py cstore curban For example, if we want to perform a 'cold storage' request for the 'curban' user, we do: client@28970a09202d:~$ python3.9 dataArchiverCli.py cstore curban Sending CSTORE request... Loading Loading @@ -209,13 +209,13 @@ You can access the redis server from the 'client' container: redis:6379[2]> lrange ready 0 5 1) "{\"jobId\": \"56577c8645da11ebbbfe356e379843eb\", \"jobType\": \"other\", \"ownerId\": \"2386\", \"phase\": \"PENDING\", \"quote\": null, \"startTime\": null, \"endTime\": null, \"executionDuration\": null, \"destruction\": null, \"parameters\": null, \"results\": null, \"jobInfo\": {\"requestType\": \"CSTORE\", \"userName\": \"szorba\"}}" \"results\": null, \"jobInfo\": {\"requestType\": \"HSTORE\", \"userName\": \"szorba\"}}" 2) "{\"jobId\": \"53d2f2a545da11ebb7bd356e379843eb\", \"jobType\": \"other\", \"ownerId\": \"2048\", \"phase\": \"PENDING\", \"quote\": null, \"startTime\": null, \"endTime\": null, \"executionDuration\": null, \"destruction\": null, \"parameters\": null, \"results\": null, \"jobInfo\": {\"requestType\": \"CSTORE\", \"userName\": \"sbertocco\"}}" 3) "{\"jobId\": \"502afdca45da11eb9676356e379843eb\", \"jobType\": \"other\", \"ownerId\": \"3354\", \"phase\": \"PENDING\", \"quote\": null, \"startTime\": null, \"endTime\": null, \"executionDuration\": null, \"destruction\": null, \"parameters\": null, \"results\": null, \"jobInfo\": {\"requestType\": \"CSTORE\", \"userName\": \"curban\"}}"lrange ready 0 5 \"results\": null, \"jobInfo\": {\"requestType\": \"CSTORE\", \"userName\": \"curban\"}}" You can access the file catalog from the 'client' container: 1) Access the db via psql client: Loading @@ -225,47 +225,42 @@ You can access the file catalog from the 'client' container: The default output of the query after the container initialization should be something like this: vospace_testdb=# SELECT node_id, parent_path, path, name, type, owner_id, creator_id, content_MD5 FROM Node; node_id | parent_path | path | name | type | owner_id | creator_id | content_md5 ---------+-------------+-----------+------------+-----------+----------+------------+------------- 1 | | | | container | 0 | 0 | 2 | | 2 | curban | container | 3354 | 3354 | 3 | 2 | 2.3 | store | container | 3354 | 3354 | 4 | | 4 | sbertocco | container | 2048 | 2048 | 5 | 4 | 4.5 | store | container | 2048 | 2048 | 6 | | 6 | szorba | container | 2386 | 2386 | 7 | 6 | 6.7 | store | container | 2386 | 2386 | 8 | | 8 | test | container | 2386 | 2386 | 9 | 8 | 8.9 | f1 | container | 2386 | 2386 | 10 | 8.9 | 8.9.10 | f2_renamed | container | 2386 | 2386 | 11 | 8.9.10 | 8.9.10.11 | f3 | container | 2386 | 2386 | (11 rows) vospace_testdb=# SELECT node_id, parent_path, path, name, tstamp_wrapper_dir, type, owner_id, creator_id, content_MD5 FROM Node; node_id | parent_path | path | name | tstamp_wrapper_dir | type | owner_id | creator_id | content_md5 ---------+-------------+---------+------------+--------------------+-----------+----------+------------+------------- 1 | | | | | container | 0 | 0 | 2 | | 2 | curban | | container | 3354 | 3354 | 3 | | 3 | sbertocco | | container | 2048 | 2048 | 4 | | 4 | szorba | | container | 2386 | 2386 | 5 | | 5 | test | | container | 2386 | 2386 | 6 | 5 | 5.6 | f1 | | container | 2386 | 2386 | 7 | 5.6 | 5.6.7 | f2_renamed | | container | 2386 | 2386 | 8 | 5.6.7 | 5.6.7.8 | f3 | | data | 2386 | 2386 | (8 rows) A few seconds after launching three jobs with 'dataArchiverCli.py', the database will be populated and launching the previous SQL query you will be able an output like the one here below: vospace_testdb=# SELECT node_id, parent_path, path, name, type, owner_id, creator_id, content_MD5 FROM Node; node_id | parent_path | path | name | type | owner_id | creator_id | content_md5 ---------+-------------+--------------+---------------------+-----------+----------+------------+---------------------------------- 1 | | | | container | 0 | 0 | 2 | | 2 | curban | container | 3354 | 3354 | 3 | 2 | 2.3 | store | container | 3354 | 3354 | 4 | | 4 | sbertocco | container | 2048 | 2048 | 5 | 4 | 4.5 | store | container | 2048 | 2048 | 6 | | 6 | szorba | container | 2386 | 2386 | 7 | 6 | 6.7 | store | container | 2386 | 2386 | 8 | | 8 | test | container | 2386 | 2386 | 9 | 8 | 8.9 | f1 | container | 2386 | 2386 | 10 | 8.9 | 8.9.10 | f2_renamed | container | 2386 | 2386 | 11 | 8.9.10 | 8.9.10.11 | f3 | container | 2386 | 2386 | 12 | 2.3 | 2.3.12 | 2020_12_24-11_22_47 | container | 3354 | 3354 | 13 | 2.3.12 | 2.3.12.13 | mydir | container | 3354 | 3354 | 14 | 2.3.12 | 2.3.12.14 | foo2.txt | data | 3354 | 3354 | e07f37a6bfe96ad66e408380a5e3a899 15 | 2.3.12.13 | 2.3.12.13.15 | another_foo2.txt | data | 3354 | 3354 | e048e5108d71191158b50052d531b0ca 16 | 4.5 | 4.5.16 | 2020_12_24-11_23_02 | container | 2048 | 2048 | 17 | 4.5.16 | 4.5.16.17 | foo4.txt | data | 2048 | 2048 | d41d8cd98f00b204e9800998ecf8427e 18 | 6.7 | 6.7.18 | 2020_12_24-11_23_17 | container | 2386 | 2386 | 19 | 6.7.18 | 6.7.18.19 | foo5.txt | data | 2386 | 2386 | d41d8cd98f00b204e9800998ecf8427e vospace_testdb=# SELECT node_id, parent_path, path, name, tstamp_wrapper_dir, type, owner_id, creator_id, content_MD5 FROM Node; node_id | parent_path | path | name | tstamp_wrapper_dir | type | owner_id | creator_id | content_md5 ---------+-------------+------------+------------------+---------------------+-----------+----------+------------+---------------------------------- 1 | | | | | container | 0 | 0 | 2 | | 2 | curban | | container | 3354 | 3354 | 3 | | 3 | sbertocco | | container | 2048 | 2048 | 4 | | 4 | szorba | | container | 2386 | 2386 | 5 | | 5 | test | | container | 2386 | 2386 | 6 | 5 | 5.6 | f1 | | container | 2386 | 2386 | 7 | 5.6 | 5.6.7 | f2_renamed | | container | 2386 | 2386 | 8 | 5.6.7 | 5.6.7.8 | f3 | | data | 2386 | 2386 | 9 | 2 | 2.9 | mydir | 2021_01_12-14_48_07 | container | 3354 | 3354 | 10 | 2 | 2.10 | foo2.txt | 2021_01_12-14_48_07 | data | 3354 | 3354 | e07f37a6bfe96ad66e408380a5e3a899 11 | 2.9 | 2.9.11 | another_foo2.txt | 2021_01_12-14_48_07 | data | 3354 | 3354 | e048e5108d71191158b50052d531b0ca 12 | 3 | 3.12 | foo4.txt | 2021_01_12-14_48_22 | data | 2048 | 2048 | 5f429d803340bb7748c52b3931ed54cf 13 | 4 | 4.13 | aaa | | container | 2386 | 2386 | 14 | 4.13 | 4.13.14 | bbb | | container | 2386 | 2386 | 15 | 4.13.14 | 4.13.14.15 | foo5.txt | | data | 2386 | 2386 | 262214d5cde30a74997199fb4e220a26 (15 rows) From the file catalog database you can also obtain information about jobs, according to the UWS specification. Loading Loading
README.txt +37 −42 Original line number Diff line number Diff line Loading @@ -140,7 +140,7 @@ The output should be something like this: Another thing you can do is to launch the 'dataArchiver.py' client. Launching the client without any argument will show you how to use it: client@28970a09202d:~$ python3 dataArchiverCli.py client@28970a09202d:~$ python3.9 dataArchiverCli.py NAME dataArchiverCli.py Loading @@ -165,8 +165,8 @@ DESCRIPTION The username must be the same used for accessing the transfer node. For example, if we want to perform a 'cold storage' request for a the 'curban' user, we do: client@28970a09202d:~$ python3 dataArchiverCli.py cstore curban For example, if we want to perform a 'cold storage' request for the 'curban' user, we do: client@28970a09202d:~$ python3.9 dataArchiverCli.py cstore curban Sending CSTORE request... Loading Loading @@ -209,13 +209,13 @@ You can access the redis server from the 'client' container: redis:6379[2]> lrange ready 0 5 1) "{\"jobId\": \"56577c8645da11ebbbfe356e379843eb\", \"jobType\": \"other\", \"ownerId\": \"2386\", \"phase\": \"PENDING\", \"quote\": null, \"startTime\": null, \"endTime\": null, \"executionDuration\": null, \"destruction\": null, \"parameters\": null, \"results\": null, \"jobInfo\": {\"requestType\": \"CSTORE\", \"userName\": \"szorba\"}}" \"results\": null, \"jobInfo\": {\"requestType\": \"HSTORE\", \"userName\": \"szorba\"}}" 2) "{\"jobId\": \"53d2f2a545da11ebb7bd356e379843eb\", \"jobType\": \"other\", \"ownerId\": \"2048\", \"phase\": \"PENDING\", \"quote\": null, \"startTime\": null, \"endTime\": null, \"executionDuration\": null, \"destruction\": null, \"parameters\": null, \"results\": null, \"jobInfo\": {\"requestType\": \"CSTORE\", \"userName\": \"sbertocco\"}}" 3) "{\"jobId\": \"502afdca45da11eb9676356e379843eb\", \"jobType\": \"other\", \"ownerId\": \"3354\", \"phase\": \"PENDING\", \"quote\": null, \"startTime\": null, \"endTime\": null, \"executionDuration\": null, \"destruction\": null, \"parameters\": null, \"results\": null, \"jobInfo\": {\"requestType\": \"CSTORE\", \"userName\": \"curban\"}}"lrange ready 0 5 \"results\": null, \"jobInfo\": {\"requestType\": \"CSTORE\", \"userName\": \"curban\"}}" You can access the file catalog from the 'client' container: 1) Access the db via psql client: Loading @@ -225,47 +225,42 @@ You can access the file catalog from the 'client' container: The default output of the query after the container initialization should be something like this: vospace_testdb=# SELECT node_id, parent_path, path, name, type, owner_id, creator_id, content_MD5 FROM Node; node_id | parent_path | path | name | type | owner_id | creator_id | content_md5 ---------+-------------+-----------+------------+-----------+----------+------------+------------- 1 | | | | container | 0 | 0 | 2 | | 2 | curban | container | 3354 | 3354 | 3 | 2 | 2.3 | store | container | 3354 | 3354 | 4 | | 4 | sbertocco | container | 2048 | 2048 | 5 | 4 | 4.5 | store | container | 2048 | 2048 | 6 | | 6 | szorba | container | 2386 | 2386 | 7 | 6 | 6.7 | store | container | 2386 | 2386 | 8 | | 8 | test | container | 2386 | 2386 | 9 | 8 | 8.9 | f1 | container | 2386 | 2386 | 10 | 8.9 | 8.9.10 | f2_renamed | container | 2386 | 2386 | 11 | 8.9.10 | 8.9.10.11 | f3 | container | 2386 | 2386 | (11 rows) vospace_testdb=# SELECT node_id, parent_path, path, name, tstamp_wrapper_dir, type, owner_id, creator_id, content_MD5 FROM Node; node_id | parent_path | path | name | tstamp_wrapper_dir | type | owner_id | creator_id | content_md5 ---------+-------------+---------+------------+--------------------+-----------+----------+------------+------------- 1 | | | | | container | 0 | 0 | 2 | | 2 | curban | | container | 3354 | 3354 | 3 | | 3 | sbertocco | | container | 2048 | 2048 | 4 | | 4 | szorba | | container | 2386 | 2386 | 5 | | 5 | test | | container | 2386 | 2386 | 6 | 5 | 5.6 | f1 | | container | 2386 | 2386 | 7 | 5.6 | 5.6.7 | f2_renamed | | container | 2386 | 2386 | 8 | 5.6.7 | 5.6.7.8 | f3 | | data | 2386 | 2386 | (8 rows) A few seconds after launching three jobs with 'dataArchiverCli.py', the database will be populated and launching the previous SQL query you will be able an output like the one here below: vospace_testdb=# SELECT node_id, parent_path, path, name, type, owner_id, creator_id, content_MD5 FROM Node; node_id | parent_path | path | name | type | owner_id | creator_id | content_md5 ---------+-------------+--------------+---------------------+-----------+----------+------------+---------------------------------- 1 | | | | container | 0 | 0 | 2 | | 2 | curban | container | 3354 | 3354 | 3 | 2 | 2.3 | store | container | 3354 | 3354 | 4 | | 4 | sbertocco | container | 2048 | 2048 | 5 | 4 | 4.5 | store | container | 2048 | 2048 | 6 | | 6 | szorba | container | 2386 | 2386 | 7 | 6 | 6.7 | store | container | 2386 | 2386 | 8 | | 8 | test | container | 2386 | 2386 | 9 | 8 | 8.9 | f1 | container | 2386 | 2386 | 10 | 8.9 | 8.9.10 | f2_renamed | container | 2386 | 2386 | 11 | 8.9.10 | 8.9.10.11 | f3 | container | 2386 | 2386 | 12 | 2.3 | 2.3.12 | 2020_12_24-11_22_47 | container | 3354 | 3354 | 13 | 2.3.12 | 2.3.12.13 | mydir | container | 3354 | 3354 | 14 | 2.3.12 | 2.3.12.14 | foo2.txt | data | 3354 | 3354 | e07f37a6bfe96ad66e408380a5e3a899 15 | 2.3.12.13 | 2.3.12.13.15 | another_foo2.txt | data | 3354 | 3354 | e048e5108d71191158b50052d531b0ca 16 | 4.5 | 4.5.16 | 2020_12_24-11_23_02 | container | 2048 | 2048 | 17 | 4.5.16 | 4.5.16.17 | foo4.txt | data | 2048 | 2048 | d41d8cd98f00b204e9800998ecf8427e 18 | 6.7 | 6.7.18 | 2020_12_24-11_23_17 | container | 2386 | 2386 | 19 | 6.7.18 | 6.7.18.19 | foo5.txt | data | 2386 | 2386 | d41d8cd98f00b204e9800998ecf8427e vospace_testdb=# SELECT node_id, parent_path, path, name, tstamp_wrapper_dir, type, owner_id, creator_id, content_MD5 FROM Node; node_id | parent_path | path | name | tstamp_wrapper_dir | type | owner_id | creator_id | content_md5 ---------+-------------+------------+------------------+---------------------+-----------+----------+------------+---------------------------------- 1 | | | | | container | 0 | 0 | 2 | | 2 | curban | | container | 3354 | 3354 | 3 | | 3 | sbertocco | | container | 2048 | 2048 | 4 | | 4 | szorba | | container | 2386 | 2386 | 5 | | 5 | test | | container | 2386 | 2386 | 6 | 5 | 5.6 | f1 | | container | 2386 | 2386 | 7 | 5.6 | 5.6.7 | f2_renamed | | container | 2386 | 2386 | 8 | 5.6.7 | 5.6.7.8 | f3 | | data | 2386 | 2386 | 9 | 2 | 2.9 | mydir | 2021_01_12-14_48_07 | container | 3354 | 3354 | 10 | 2 | 2.10 | foo2.txt | 2021_01_12-14_48_07 | data | 3354 | 3354 | e07f37a6bfe96ad66e408380a5e3a899 11 | 2.9 | 2.9.11 | another_foo2.txt | 2021_01_12-14_48_07 | data | 3354 | 3354 | e048e5108d71191158b50052d531b0ca 12 | 3 | 3.12 | foo4.txt | 2021_01_12-14_48_22 | data | 2048 | 2048 | 5f429d803340bb7748c52b3931ed54cf 13 | 4 | 4.13 | aaa | | container | 2386 | 2386 | 14 | 4.13 | 4.13.14 | bbb | | container | 2386 | 2386 | 15 | 4.13.14 | 4.13.14.15 | foo5.txt | | data | 2386 | 2386 | 262214d5cde30a74997199fb4e220a26 (15 rows) From the file catalog database you can also obtain information about jobs, according to the UWS specification. Loading