Loading README.txt +72 −39 Original line number Diff line number Diff line Simple communication test that involes 5 docker containers: - client (container_name: test_client, files to run: 'vos_rest_client.py' and 'dataArchiver.py') - client (container_name: client, files to run: 'vos_rest_client.py' and 'dataArchiver.py') - server (container_name: transfer_service) - RabbitMQ (container_name: rabbitmq) - Redis (container_name: redis) Loading @@ -17,7 +17,7 @@ running (read the section here below). ############################################################################################################### You can start the whole environment with (launch the following command from the 'docker' dir): You can start the whole environment from the 'vos-ts' directory with: $ docker-compose up Once all the containers are up and running, open another shell and access the 'client' container: Loading @@ -29,40 +29,68 @@ $ python3.9 vos_rest_client.py QUEUE_NAME For example: $ python3.9 vos_rest_client.py start_job_queue The output should be something like this: The output should be something like this (you send and then you receive a response containing the info previously stored into the database): client@a89c0bb962f7:~$ python3.9 vos_rest_client.py start_job_queue Sending transfer request: { "transfer": { "@version": "2.1", "target": "vos://example.com!vospace/mydata1", "direction": "pullFromVoSpace", "protocol": { "@uri": "ivo://ivoa.net/vospace/core#httpget" } } } Response: { "jobId": "3ff92acedc9611eabf140242ac1f0007", "runId": null, "ownerId": "anonymous", "phase": "PENDING", "quote": null, "creationTime": null, "startTime": null, "endTime": null, "executionDuration": null, "executionDuration": 0, "destruction": null, "parameters": null, "results": [], "errorSummary": null, "jobInfo": { "transfer": { "@version": "2.1", "target": "vos://example.com!vospace/mydata1", "direction": "pullFromVoSpace", "protocol": { "@uri": "ivo://ivoa.net/vospace/core#httpget" "direction": "pullToVoSpace", "view": null, "protocol": [ { "endpoint": null, "param": [], "uri": "ia2:tape-recall" } ], "keepBytes": null, "version": null } }, "version": null } Response: { "job_id": "3ff92acedc9611eabf140242ac1f0007", "owner_id": "0000", "job_type": "pullToVoSpace", "phase": "PENDING", "start_time": null, "end_time": null, "job_info": { "transfer": { "view": null, "target": "vos://example.com!vospace/mydata1", "version": null, "protocol": [ { "uri": "ia2:tape-recall", "param": [], "endpoint": null } ], "direction": "pullToVoSpace", "keepBytes": null } }, "results": null } After processing the request, the server launches an internal thread delayed of 10 seconds which changes the Loading @@ -82,24 +110,29 @@ The output should be something like this: } Response: { "jobId": "3ff92acedc9611eabf140242ac1f0007", "phase": "EXECUTING", "quote": null, "startTime": null, "endTime": null, "executionDuration": null, "destruction": null, "parameters": null, "jobInfo": { "job_id": "3ff92acedc9611eabf140242ac1f0007", "owner_id": "0000", "job_type": "pullToVoSpace", "phase": "PENDING", "start_time": null, "end_time": null, "job_info": { "transfer": { "@version": "2.1", "view": null, "target": "vos://example.com!vospace/mydata1", "direction": "pullFromVoSpace", "protocol": { "@uri": "ivo://ivoa.net/vospace/core#httpget" } "version": null, "protocol": [ { "uri": "ia2:tape-recall", "param": [], "endpoint": null } ], "direction": "pullToVoSpace", "keepBytes": null } }, "results": null } --------------------------------------------------------------------------------------------------------------- Loading Loading @@ -208,7 +241,7 @@ vospace_testdb=# SELECT node_id, parent_path, path, name, type, owner_id, creato 11 | 8.9.10 | 8.9.10.11 | f3 | container | 2386 | 2386 | (11 rows) A few seconds after launching three jobs with 'dataArchiverCli.py', the database will be ppulated and launching the previous 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; Loading Loading
README.txt +72 −39 Original line number Diff line number Diff line Simple communication test that involes 5 docker containers: - client (container_name: test_client, files to run: 'vos_rest_client.py' and 'dataArchiver.py') - client (container_name: client, files to run: 'vos_rest_client.py' and 'dataArchiver.py') - server (container_name: transfer_service) - RabbitMQ (container_name: rabbitmq) - Redis (container_name: redis) Loading @@ -17,7 +17,7 @@ running (read the section here below). ############################################################################################################### You can start the whole environment with (launch the following command from the 'docker' dir): You can start the whole environment from the 'vos-ts' directory with: $ docker-compose up Once all the containers are up and running, open another shell and access the 'client' container: Loading @@ -29,40 +29,68 @@ $ python3.9 vos_rest_client.py QUEUE_NAME For example: $ python3.9 vos_rest_client.py start_job_queue The output should be something like this: The output should be something like this (you send and then you receive a response containing the info previously stored into the database): client@a89c0bb962f7:~$ python3.9 vos_rest_client.py start_job_queue Sending transfer request: { "transfer": { "@version": "2.1", "target": "vos://example.com!vospace/mydata1", "direction": "pullFromVoSpace", "protocol": { "@uri": "ivo://ivoa.net/vospace/core#httpget" } } } Response: { "jobId": "3ff92acedc9611eabf140242ac1f0007", "runId": null, "ownerId": "anonymous", "phase": "PENDING", "quote": null, "creationTime": null, "startTime": null, "endTime": null, "executionDuration": null, "executionDuration": 0, "destruction": null, "parameters": null, "results": [], "errorSummary": null, "jobInfo": { "transfer": { "@version": "2.1", "target": "vos://example.com!vospace/mydata1", "direction": "pullFromVoSpace", "protocol": { "@uri": "ivo://ivoa.net/vospace/core#httpget" "direction": "pullToVoSpace", "view": null, "protocol": [ { "endpoint": null, "param": [], "uri": "ia2:tape-recall" } ], "keepBytes": null, "version": null } }, "version": null } Response: { "job_id": "3ff92acedc9611eabf140242ac1f0007", "owner_id": "0000", "job_type": "pullToVoSpace", "phase": "PENDING", "start_time": null, "end_time": null, "job_info": { "transfer": { "view": null, "target": "vos://example.com!vospace/mydata1", "version": null, "protocol": [ { "uri": "ia2:tape-recall", "param": [], "endpoint": null } ], "direction": "pullToVoSpace", "keepBytes": null } }, "results": null } After processing the request, the server launches an internal thread delayed of 10 seconds which changes the Loading @@ -82,24 +110,29 @@ The output should be something like this: } Response: { "jobId": "3ff92acedc9611eabf140242ac1f0007", "phase": "EXECUTING", "quote": null, "startTime": null, "endTime": null, "executionDuration": null, "destruction": null, "parameters": null, "jobInfo": { "job_id": "3ff92acedc9611eabf140242ac1f0007", "owner_id": "0000", "job_type": "pullToVoSpace", "phase": "PENDING", "start_time": null, "end_time": null, "job_info": { "transfer": { "@version": "2.1", "view": null, "target": "vos://example.com!vospace/mydata1", "direction": "pullFromVoSpace", "protocol": { "@uri": "ivo://ivoa.net/vospace/core#httpget" } "version": null, "protocol": [ { "uri": "ia2:tape-recall", "param": [], "endpoint": null } ], "direction": "pullToVoSpace", "keepBytes": null } }, "results": null } --------------------------------------------------------------------------------------------------------------- Loading Loading @@ -208,7 +241,7 @@ vospace_testdb=# SELECT node_id, parent_path, path, name, type, owner_id, creato 11 | 8.9.10 | 8.9.10.11 | f3 | container | 2386 | 2386 | (11 rows) A few seconds after launching three jobs with 'dataArchiverCli.py', the database will be ppulated and launching the previous 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; Loading