-
Notifications
You must be signed in to change notification settings - Fork 41
Clariden docs #31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clariden docs #31
Conversation
|
preview available: https://docs.tds.cscs.ch/31 |
|
preview available: https://docs.tds.cscs.ch/31 |
| ## Cluster Specification | ||
| ### Hardware | ||
| Clariden consists of ~1200 [Grace-Hopper nodes][ref-alps-gh200-node]. Most nodes are in the [`normal` slurm partition][ref-slurm-partition-normal], while a few nodes are in the [`debug` partition][ref-slurm-partition-debug]. | ||
| The nodes are interconnected with the [slingshot high speed network][ref-alps-slingshot-network]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| The nodes are interconnected with the [slingshot high speed network][ref-alps-slingshot-network]. | |
| The nodes are interconnected with the [Slingshot high speed network][ref-alps-slingshot-network]. |
| As usual the login nodes have direct internet connections, while the compute nodes use a [proxy server][ref-alps-slingshot-network] to access the internet. | ||
| !!! todo | ||
| Document proxy and the implications (normally transparent, but git needs modifications | ||
| Fix the ref |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| Document proxy and the implications (normally transparent, but git needs modifications | ||
| Fix the ref | ||
|
|
||
| ### File systems and storage |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| ### File systems and storage | |
| ### File systems and storage | |
| Fix the ref | ||
|
|
||
| ### File systems and storage | ||
| The scratch filesystem is hosted on [IOPStore][ref-storage-iopstor], but also the capacity storage [Capstor][ref-storage-capstor] is mounted at `/capstor/scratch/cscs`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| The scratch filesystem is hosted on [IOPStore][ref-storage-iopstor], but also the capacity storage [Capstor][ref-storage-capstor] is mounted at `/capstor/scratch/cscs`. | |
| The scratch filesystem is hosted on [IOPStor][ref-storage-iopstor], but also the capacity storage [Capstor][ref-storage-capstor] is mounted at `/capstor/scratch/cscs`. |
? Not sure how "iopstor" should be capitalized... could be "Iopstor" as wel to mirror "Capstor"?
| Document proxy and the implications (normally transparent, but git needs modifications | ||
| Fix the ref | ||
|
|
||
| ### File systems and storage |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel like the list of filesystems could maybe be presented more clearly in a table?
| ### Available programming environments | ||
|
|
||
| ## Software and services | ||
| #### Container engine |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| #### Container engine | |
| #### Container engine | |
|
|
||
| !!! todo | ||
| information about CSCS services/tools available | ||
| #### UENV |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| #### UENV | |
| #### uenv | |
| !!! todo | ||
| information about CSCS services/tools available | ||
| #### UENV | ||
| Besides running containerized workflows, it is possible to run your jobs with a [UENV][ref-tool-uenv]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| Besides running containerized workflows, it is possible to run your jobs with a [UENV][ref-tool-uenv]. | |
| Besides running containerized workflows, it is possible to run your jobs with a [uenv][ref-tool-uenv]. |
| * uenv | ||
| * CPE | ||
| * ... etc | ||
| #### CPE |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| #### CPE | |
| #### CPE | |
| ## Maintenance | ||
| ### Calendar and key events |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| ## Maintenance | |
| ### Calendar and key events | |
| ## Maintenance | |
| ### Calendar and key events | |
|
Closing this because parts of it were cut and pasted and used for the clariden docs. |
No description provided.