[slurm-users] Announcing Slurm-web v3.0.0, open source web dashboard for Slurm

[Rémi Palancher via slurm-users]

Hello Slurm users,

Some of you may find interest in the new major version of Slurm-web v3.0.0, an 
open source web dashboard for Slurm: https://slurm-web.com

Slurm-web provides a reactive & responsive web interface to track jobs with 
intuitive insights and advanced visualizations to monitor status of HPC 
supercomputers in your organization. The software is released under GPLv3 [1].

This new version is based on official Slurm REST API slurmrestd and adopts 
modern web technologies to provide many features:

- Instant jobs filtering and sorting
- Live jobs status update
- Advanced visualization of node status with racking topology
- Intuitive visualization of QOS and advanced reservations
- Multi-clusters support
- LDAP authentication
- Advanced RBAC permissions management
- Transparent caching

For the next releases, a roadmap is published with many features ideas [2].

Quick start guide to install: 
http://docs.rackslab.io/slurm-web/install/quickstart.html

RPM and deb packages are published for easy installation and upgrade on all 
most popular Linux distributions.

I hope you will like it!

[1] https://github.com/rackslab/Slurm-web
[2] https://slurm-web.com/roadmap/

--
Rémi Palancher
Rackslab: Open Source Solutions for HPC Operations
https://rackslab.io

-- 
slurm-users mailing list -- slurm-users@lists.schedmd.com
To unsubscribe send an email to slurm-users-le...@lists.schedmd.com

[slurm-users] Re: any way to allow interactive jobs or ssh in Slurm 23.02 when node is draining?

[Robert Kudyba via slurm-users]

Thanks for the reply, Luke. I also found that with Bright they have a file
called /etc/security/pam_bright.d/pam_whitelist.conf that can be used to
allow access.

On Thu, May 9, 2024 at 5:10 AM Luke Sudbery  wrote:

> Draining a node will not stop someone logging on via pam_slurm_adopt.
>
>
>
> If they have a running job, and can log on when the node is not draining,
> then they can log on when it is draining.
>
>
>
> If they don’t have a running job, they can’t log on whether it is draining
> or not.
>
>
>
> If you want people to be able to log on when they don’t have a job
> running, you could put them in a group which is given access in access.conf
> and PAM, as explained here:
> https://slurm.schedmd.com/pam_slurm_adopt.html#admin_access
> 
>
>
>
> Cheers,
>
>
>
> Luke
>
>
>
> --
>
> Luke Sudbery
>
> Principal Engineer (HPC and Storage).
>
> Architecture, Infrastructure and Systems
>
> Advanced Research Computing, IT Services
>
> Room 132, Computer Centre G5, Elms Road
>
>
>
> *Please note I don’t work on Monday.*
>
>
>
> *From:* Robert Kudyba via slurm-users 
> *Sent:* Friday, April 19, 2024 9:17 PM
> *To:* Slurm User Community List 
> *Subject:* [slurm-users] any way to allow interactive jobs or ssh in
> Slurm 23.02 when node is draining?
>
>
>
> *CAUTION:* This email originated from outside the organisation. Do not
> click links or open attachments unless you recognise the sender and know
> the content is safe.
>
>
>
> We use Bright Cluster Manager with SLurm 23.02 on RHEL9. I know about
> pam_slurm_adopt https://slurm.schedmd.com/pam_slurm_adopt.html
> 
> which does not appear to come by default with the Bright 'cm' package of
> Slurm.
>
>
>
> Currently ssh to a node gets:
>
> Login not allowed: no running jobs and no WLM allocations
>
>
>
> We have 8 GPUs on a node so when we drain a node, which can have up to a 5
> day job, no new jobs can run. And since we have 20+ TB (yes TB) local
> drives, researchers have their work and files on them to retrieve.
>
>
>
> Is there a way to use /etc/security/access.conf to work around this at
> least temporarily until the reboot and then we can revert?
>
>
>
> Thanks!
>
>
>
> Rob
>

-- 
slurm-users mailing list -- slurm-users@lists.schedmd.com
To unsubscribe send an email to slurm-users-le...@lists.schedmd.com

[slurm-users] Which "oci.conf" to use?

[Arnuld via slurm-users]

I have installed slurm and podman. I have replaced podman's default runtime
as per the documentation to "slurm". Documentation says I need to choose
one oci.conf:

https://slurm.schedmd.com/containers.html#example

Which one should I use? runc? crun? nvidia?

-- 
slurm-users mailing list -- slurm-users@lists.schedmd.com
To unsubscribe send an email to slurm-users-le...@lists.schedmd.com