Skip to content

Commit b5d2bc2

Browse files
author
Joona Tolonen
committed
Initial version of the CSC services for courses page
1 parent 1ad9cd3 commit b5d2bc2

File tree

2 files changed

+80
-0
lines changed

2 files changed

+80
-0
lines changed

docs/support/tutorials/index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -107,5 +107,6 @@ You can find Rahti tutorials in [Cloud Services > Rahti > Tutorials](../../cloud
107107

108108
## CSC Resources for Courses
109109

110+
* [CSC Services for courses](services-for-courses.md)
110111
* [A Puhti webinterface demo for course organizers](https://github.com/CSCfi/Jupyter_www_puhti)
111112
* [Noppe environment for creating custom notebooks](../../cloud/noppe/guide_for_teachers.md#creating-custom-images)
Lines changed: 79 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,79 @@
1+
# CSC Services for Courses
2+
3+
This guide will explain how to use the course project type with CSC's
4+
high-performance computing (HPC) and cloud services.
5+
6+
## Prerequisites
7+
8+
Staff members from higher education institutions and state research institutes can create a MyCSC course project. What you will need is:
9+
10+
1. [A CSC account](../../accounts/how-to-create-new-user-account.md)
11+
2. [A MyCSC course project](../../accounts/how-to-create-new-project.md)
12+
3. [A Service activated](../../accounts/how-to-add-service-access-for-project.md)
13+
14+
## Available services
15+
16+
The following services are available to support you in delivering your course. All services except Noppe require an active MyCSC project with the relevant service enabled. Applying for more quota depends on the services; see the details below. The medium (M) billing unit package is the default package granted for course projects. This should cover most use cases.
17+
18+
The services are listed in alphabetical order.
19+
20+
### Allas
21+
22+
### cPouta
23+
24+
### Mahti and Puhti (HPC)
25+
26+
!!! info "Next HPC: Roihu"
27+
28+
CSC's next national supercomputer Roihu, a BullSequana XH3000 hybrid system, will replace the Puhti and Mahti supercomputers. More information about [Roihu](../../computing/systems-roihu.md).
29+
30+
Courses using the HPC should have fewer than 50 people. To ensure students have access to the necessary resources, reservations should be made well in advance (i.e. several weeks beforehand) to guarantee capacity during practical sessions. Reservations allocate supercomputer nodes to your project, meaning that only course's students can use them. This ensures reasonable queuing times, even if the system is in heavy use.
31+
32+
Please note that reservation requests may be declined, so it is good practice to request one when planning the course. If students are completing the course independently over a longer period, they can use the standard queuing system and its limits. In that case, it is your project's BUs that provide guidance on reasonable resource usage.
33+
34+
HPCs have guidance on reservations in two categories: Typical and maximum possible. Please note that these requests may be denied or reduced, as with any other resource request at CSC. In practice, requests at the maximum level should only be made for major or high-priority events. Only request the needed resources, and provide an explanation as to why you require them (you may require less than the amounts specified below).
35+
36+
#### Puhti
37+
38+
*Typical reservation*
39+
40+
- Each day:
41+
- CPU: A dedicated reservation can include a maximum of two regular nodes (2 x 40 cores and 2 x 192 GB).
42+
- Reservations are valid from 08:00 to 17:00 at most.
43+
- A maximum of five days in total.
44+
45+
*Maximum reservation*
46+
47+
- Each day:
48+
- CPU: A dedicated reservation can include a maximum of five regular nodes (200 cores).
49+
- GPU: A dedicated reservation can include a maximum of four GPU nodes.
50+
- The reservation is valid for a maximum of 12 hours per day. Timeslots can be requested (e.g. 08:00–20:00 or 12:00–24:00).
51+
- A maximum of ten days in total.
52+
53+
#### Mahti
54+
55+
*Typical reservation*
56+
57+
- Each day:
58+
- CPU: A dedicated reservation can include a maximum of two regular M-nodes (2x128 cores and 2x256 GB).
59+
- GPU: A dedicated reservation can include a maximum of 14 [GPU slices](../../computing/running/batch-job-partitions.md#gpu-slices) (1 node).
60+
- Reservations are valid from 08:00 to 17:00
61+
- Maximum total of five days.
62+
63+
*Maximum reservation*
64+
65+
- Each day:
66+
- CPU: A dedicated reservation can include a maximum of eight regular M-nodes (8 x 128 cores and 8 x 256 GB).
67+
- GPU: A dedicated reservation can include a maximum of 28 [GPU slices](../../computing/running/batch-job-partitions.md#gpu-slices) (1 node).
68+
- Reservations are valid for a maximum of 12 hours per day and can be requested in time slots (e.g. 08:00–20:00 or 12:00–24:00).
69+
- Maximum total of ten days.
70+
71+
### Noppe
72+
73+
### Pukki DBaaS
74+
75+
### Rahti
76+
77+
### SD Desktop
78+
79+

0 commit comments

Comments
 (0)