*** This version of Confluence is for testing only and contains a copy of content from June 29th 2026. No changes will be preserved. ***
...
- Collum group may not use Loring's nodes.
- And Loring's group may not use Collum's nodes.
Table
...
of information, by group
| Group | Group's nodes And software licensed. | Access to other groups' nodes (assume access to own group's nodes, naturally) | WebMO data (GB) | Current users' data (GB) | Inactive users' data (GB) | Back-up? (EZ-Backup) | Back-in-Time versioning | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Collum | 8 compute nodes. Maybe 1 more (former head node). Has paid for WebMO | Widom (Collum group paid to add hard drives to all 7 of Widom's compute nodes. 12TB (= 6TB * 2) hard drive space now available on each of Widom's nodes.) | Yes | No | (To get from Lulu) | (To get from Lulu) | (To get from Lulu) | Yes | ||||||||
| Abruna | 10 compute nodes (
Maybe 1 more (former head node, we expect) | n/a | n/a | ~500 (11/11/16) | No | No | (To get from Lulu) | No | ||||||||
| Loring | 5 compute nodes. Oldest nodes on the cluster. | Widom | n/a | No | No | (To get from Lulu) | (To get from Lulu) | No | ||||||||
| Widom | Widom contributing the current head node. 8 compute nodes.
| Loring Special queue* | n/a | (To get from Lulu) | (To get from Lulu) | No | No | |||||||||
| SLin | (SLin currently has no compute nodes) |
Widom | n/a | (To get from Lulu) | (To get from Lulu) | No | No |
|
*Special queue: Queue was created and for use by a single member of Widom's group to enable their research without consuming 100% of Widom's nodes.
...
Q: Enable WebMO for groups other than Collum? If so, add column with nodes enabled.
Q: Enable Back-in-Time, for versioning? If so, how provision and who pays what? (Does CAC have better options, if cluster is hosted there?)
Q: Backing up user accounts and other research data? If beyond Collum's group, how provision and who pays what? (Does CAC have better options, if cluster is hosted there?)
Know issues:
Q: How do we prevent individual from bringing shared head node to its needs by running an application directly on the head node, instead of using queues? (Does CAC have suggestions?)
| Children Display | ||||||
|---|---|---|---|---|---|---|
|
...