Interact with Systems
A Tapis system is a server or collection of servers associated with a single hostname. They may be public or private, and they may either be storage systems (used for storing files) or execution systems (used for running jobs).
On some tenants, users are provided private storage and execution systems attached to TACC resources. If you would like to create your own systems, skip ahead to Create a Private System.
Warning
The tacc.prod tenant likely does not contain default systems for your username. Skip ahead to Create a Private System before working through this guide.
Find Systems
Systems can be discovered using the tapis systems list
command:
$ tapis systems list
+-------------------------------+-------------------------------------------------+-----------+---------+
| id | name | type | default |
+-------------------------------+-------------------------------------------------+-----------+---------+
| tacc.stampede2.taccuser | Execution system for TACC Stampede2 | EXECUTION | False |
| tacc.work.taccuser | Storage system for TACC work directory | STORAGE | False |
| docking.storage | Storage VM for the drug discovery portal | STORAGE | True |
| tapis.storage.system | Tapis storage system | STORAGE | False |
| tapis.execution.system | Tapis execution system | EXECUTION | False |
| csc.2018.storage | Storage system for CSC 2018 Institute | STORAGE | False |
| docking.exec.ls5 | Lonestar 5 Supercomputer | EXECUTION | False |
| docking.slurm.stampede | Docking's Stampede SLURM Execution Host | EXECUTION | False |
| docking.work.storage.stampede | Stampede $WORK storage | STORAGE | False |
| docking.fork.fleming | Fork Execution VM for the drug discovery portal | EXECUTION | False |
| docking.storage2 | Storage VM for the drug discovery portal | STORAGE | False |
| docking.exec.lonestar | Lonestar 4 Supercomputer | EXECUTION | False |
+-------------------------------+-------------------------------------------------+-----------+---------+
On this tenant, the user taccuser
sees numerous storage and execution
systems. All systems are either public or private (with varying degrees of
privacy), each of which are shown here.
On tenants with many more systems, it may be useful to narrow the list with
the tapis systems search
command. For example, to discover systems only
owned by you:
$ tapis systems search --owner eq taccuser
+-------------------------+----------------------------------------+-----------+---------+
| id | name | type | default |
+-------------------------+----------------------------------------+-----------+---------+
| tacc.stampede2.taccuser | Execution system for TACC Stampede2 | EXECUTION | False |
| tacc.work.taccuser | Storage system for TACC work directory | STORAGE | False |
+-------------------------+----------------------------------------+-----------+---------+
Other useful searches might include:
$ tapis systems search --owner neq taccuser # systems you don't own
$ tapis systems search --public eq true # only public systems
$ tapis systems search --public eq false # only private systems
$ tapis systems search --type eq EXECUTION # only execution systems
$ tapis systems search --type eq STORAGE # only storage systems
$ tapis systems search --default eq true # your default system
You can also chain multiple search parameters. For example, to display only private storage systems:
$ tapis systems search --type eq STORAGE --public eq false
+--------------------+----------------------------------------+---------+---------+
| id | name | type | default |
+--------------------+----------------------------------------+---------+---------+
| tacc.work.taccuser | Storage system for TACC work directory | STORAGE | False |
+--------------------+----------------------------------------+---------+---------+
Note
Don’t forget to replace instances of taccuser with your actual username on the tenant
Discover System Hostname and Default Paths
To see additional system information, including hostname, root folder locations,
and availability, use the tapis systems show
command with a system ID. For
example, find out more information about your personal storage system as
follows:
$ tapis systems show -f json tacc.work.taccuser
1{
2 "id": "tacc.work.taccuser",
3 "name": "Storage system for the TACC WORK directory",
4 "type": "STORAGE",
5 "default": false,
6 "available": true,
7 "description": "Storage system for the TACC WORK directory via Stampede2",
8 "environment": null,
9 "executionType": null,
10 "globalDefault": false,
11 "lastModified": "7 hours ago",
12 "login": null,
13 "maxSystemJobs": null,
14 "maxSystemJobsPerUser": null,
15 "owner": "taccuser",
16 "public": false,
17 "queues": null,
18 "revision": 1,
19 "scheduler": null,
20 "scratchDir": null,
21 "site": null,
22 "status": "UP",
23 "storage": {
24 "proxy": null,
25 "protocol": "SFTP",
26 "mirror": false,
27 "port": 22,
28 "auth": {
29 "type": "SSHKEYS"
30 },
31 "publicAppsDir": null,
32 "host": "stampede2.tacc.utexas.edu",
33 "rootDir": "/work/01234/taccuser",
34 "homeDir": "/"
35 },
36 "uuid": "383424038079107562-242ac112-0001-006",
37 "workDir": null
38}
The -f json
flag was provided to render all information about the
system. As described above, this storage system is a gateway to your private
storage space on the TACC $WORK filesystem. The rootDir is the virtual root
path for operations performed on this system. The highlighted lines emphasize
the host and root directory when performing operations against this system.
In addition to standard host and path information, execution systems also contain information about queue types and availability.
Check System Status
It may be useful to check the status (availability) of a system in a scriptable way prior to, e.g., uploading files as part of a pipeline. The following command can be used with extra flags to strip out the useful part of the response:
$ tapis systems show -c status -f value tacc.work.taccuser
UP
Note
Use tapis command subcommand --help
to find usage information for
each command