ARCHIVED: On the TeraGrid, how do I find data, scheduling, and file
system policies for each resource?
Note: After ten years of service to the national
science and engineering community, the TeraGrid project has ended. It
is succeeded by a new National Science Foundation (NSF) program, the Extreme Science and Engineering
Discovery Environment (XSEDE). You should move any data stored on
TeraGrid systems to an alternate storage resource. If you have
leftover service units on your TeraGrid allocation, or if your
research requires further use of high performance computational,
visualization, storage, and network resources, consider applying
for an allocation on one or more XSEDE digital
services.
To view detailed information on data, scheduling, and file system
policies for each TeraGrid resource, use the
tg-policy command.
The following flag options are available:
-data |
Data policy
|
-sched |
Scheduling and queue policy
|
-fs |
File system summary
|
-help |
Help display
|
-v |
tg-policy command version
|
-a |
Return all
|
Following is an example of output from the tg-policy
-a command on Ember (NCSA):
Scheduling Policy:
--------------------------
Given the small node count at this site please submit jobs with extra
discretion. Select small node counts for long running jobs, or short
execution times for large node count jobs. Priority is given to the
realtime visualization systems between 8am-6pm. Jobs will be interrupted
if someone requires physical access to the visualization resources.
Advance notice may or may not be available.
Site Data Policy:
-----------------
Home directories receive catastrophic backup data protection. Daily management
of data files therefore is the user's responsibility. If the data is important
to you, find a safe location for it. We *may* be in the position to retrieve a
file occasionally, but there are no guarantees. Home directory space is limited
but not directly metered.
Scratch areas and parallel filesystems are not backed up and data storage for
any length of time is not guaranteed.
------------------------------------------
ember.ncsa.illinois.edu policy
------------------------------------------
------------------------------------------
Available Filesystems Summary
------------------------------------------
1) Node Scratch (local scratch space on a single compute node)
Size: 14903.7 GB
Location: , $TG_NODE_SCRATCH
Purged: after each job
Backups: none
Quota: none
Notes:
2) Cluster Scratch (scratch space shared by all compute nodes)
Size: 14903.7 GB
Location: , $TG_CLUSTER_SCRATCH
Purged: as needed
Backups: none
Quota: none
Note:
3) Cluster Home (home directory space shared by all compute nodes)
Size: 14903.7 GB
Location: , $TG_CLUSTER_HOME
Purged: as needed
Backups: daily in general but normally within a week
Quota: none
Note:
4) Cluster PFS (parallel filesystem shared by all compute nodes)
Size: not available at this location
Location: not available at this location
Purged: not available at this location
Backups: not available at this location
Quota: not available at this location
Note: not available at this location
5) Cluster GPFS (GPFS directory space shared by all compute nodes)
Size: not available at this location
Location: not available at this location
Purged: not available at this location
Backups: not available at this location
Quota: not available at this location
Note: not available at this location
6) Cluster PVFS (PVFS directory space shared by all compute nodes)
Size: 14903.7 GB
Location: , $TG_CLUSTER_PVFS
Purged: as needed
Backups: none
Quota: none
Note:
tg-policy v0.2
This is document awnt in domain all.
Last modified on November 23, 2011.
