Skip to content

Commit cc58285

Browse files
Merge pull request #5 from rnabioco/motd-maint-from-reservation
2 parents 0056e24 + 0f8a909 commit cc58285

4 files changed

Lines changed: 506 additions & 449 deletions

File tree

docs/admin.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,7 @@ scontrol create reservation \
2121
- **`Flags=MAINT`** tells the backfill scheduler not to schedule jobs that would overlap with the reservation. Jobs already running that finish before the start time are unaffected.
2222
- Users can see the upcoming reservation with `scontrol show reservation`.
2323
- Jobs whose wall time would bleed into the reservation window won't start until after it ends.
24+
- The reservation also drives the [login-splash maintenance banner](login-splash.md#maintenance-banner): once it's created, the countdown shown to users tracks the reservation's `StartTime`. With no `MAINT` reservation, the banner falls back to the last Thursday of the month, so the two stay in sync automatically.
2425

2526
### Useful reservation flags
2627

docs/login-splash.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,11 @@ Cluster maintenance is scheduled for the **last Thursday of every month**. The b
3535
| Day of maintenance | **Red** background | "MAINTENANCE TODAY: Thursday, March 26, 2026" |
3636
| More than 5 days out | No banner ||
3737

38-
No configuration is needed — the script calculates the next last-Thursday automatically.
38+
The banner date comes from the soonest upcoming SLURM `MAINT` reservation when
39+
one is scheduled (see [admin guide](admin.md#scheduling-maintenance)), so it
40+
always reflects the real maintenance window. If no reservation is queryable, the
41+
script falls back to calculating the next last-Thursday automatically. Either
42+
way, no per-login configuration is needed.
3943

4044
## Admin messages
4145

0 commit comments

Comments
 (0)