Commit ea64c7bb authored by Cristiano Urban's avatar Cristiano Urban
Browse files

Updated README.md.

parent 76f20ee3
Loading
Loading
Loading
Loading
Loading
+4 −0
Original line number Diff line number Diff line
@@ -62,6 +62,7 @@ The *client* container provides the following command line tools:

- **vos_data**: launches a job to automatically store data provided by the user on a given storage point (hot or cold)
- **vos_group**: allows to add/list/remove users/groups to/from 'group_read' and/or 'group_write' of a VOSpace node and its child nodes (if any)
- **vos_user**: allows to add/remove users to/from the database
- **vos_import**: imports VOSpace nodes on the file catalog for data already stored on a given storage point
- **vos_job**: provides information about jobs
- **vos_storage**: allows to add/list/remove storage points.
@@ -83,6 +84,8 @@ On this container, hosted on the so-called transfer node, each user will find hi
The user will copy the data to be stored within the *store* folder, while he/she will find the requested data within the *retrieve* folder.
This use case was implemented in order to try to offer support to users providing huge amounts of data in the order of terabytes.

Log files can be found in /var/log/vos_ts.

#### Redis

You can access the Redis server from the **client** container by following the steps here below.
@@ -105,6 +108,7 @@ redis-cli -h job_cache
5. The messages sent by the user command line tools are handled by the following queues:
   - for vos_data the queue is *data_queue*
   - for vos_group the queue is *group_queue*
   - for vos_user the queue is *user_queue*
   - for vos_import the queue is *import_queue*
   - for vos_job the queue is *job_queue*
   - for vos_storage the queue is *storage_queue*