Re: [slurm-users] Possible to get cluster utilization by partition?

[Chin,David]

I cooked one up myself using Python (with Pandas) which I feel is more
maintainable.

https://github.com/prehensilecode/slurm_utilization/blob/main/utilization_from_sacct.py

It's still in pretty rough shape, and could certainly use some refining.

Cheers,
Dave

--
David Chin, PhD (he/him)   Sr. SysAdmin, URCF, Drexel
dw...@drexel.edu 215.571.4335 (o)
For URCF support: urcf-supp...@drexel.edu
https://proteusmaster.urcf.drexel.edu/urcfwiki
github:prehensilecode
researchgate.NET:David-Chin-6

From: slurm-users  on behalf of 
Chin,David 
Sent: Friday, November 5, 2021 14:50
To: Slurm User Community List 
Subject: Re: [slurm-users] Possible to get cluster utilization by partition?


External.

Hi, Ole:

Thanks for the link to your tools. I'll take a closer look at them.

I wanted to make sure it wasn't something Slurm already had before I
started writing my own.

Perhaps someone out there can make that feature request and sponsor its
development at SchedMD. I feel like it would be a generally useful feature.

Cheers,
Dave

--
David Chin, PhD (he/him)   Sr. SysAdmin, URCF, Drexel
dw...@drexel.edu 215.571.4335 (o)
For URCF support: urcf-supp...@drexel.edu
https://proteusmaster.urcf.drexel.edu/urcfwiki
github:prehensilecode

From: slurm-users  on behalf of Ole Holm 
Nielsen 
Sent: Friday, November 5, 2021 03:26
To: slurm-users@lists.schedmd.com 
Subject: Re: [slurm-users] Possible to get cluster utilization by partition?

External.

Hi Dave,

On 11/4/21 21:47, Chin,David wrote:
> I am running Slurm 20.02.7. I would like to generate cluster utilization
> report based on the billing TRES, but separated by partition.
>
> I can get full cluster utilization using:
>
>  sreport cluster utilization -T billing start=2021-01-01 end=2021-06-30
>
> but it would be useful for understanding usage if a similar report could
> be produced for each partition.

This should probably be a FAQ :-)  The sreport utility can't provide
accounting information for partitions :-(

Alternatively, I have written the accounting tools slurmacct and
topreports which are available from
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOleHolmNielsen%2FSlurm_tools%2Ftree%2Fmaster%2Fslurmacctdata=04%7C01%7Cdwc62%40drexel.edu%7C0973c68a3b754bce6d6908d9a02dc25d%7C3664e6fa47bd45a696708c4f080f8ca6%7C0%7C0%7C637716940669785528%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=sqLpg4Ep94EaCeKYR5funLXV4ukxb6WxY3%2Brgx2KG5s%3Dreserved=0

While the output has a different format, we find this more useful than
sreport because the lines are sorted in the order of usage percentages.

/Ole



Drexel Internal Data


Drexel Internal Data


Drexel Internal Data

Re: [slurm-users] maridb version compatibility with Slurm version

[Paul Edmon]

I've regularly upgraded the mariadb version with out upgrading the slurm 
version with no issue. We are currently running 10.6.7 for MariaDB on 
CentOS 7.9 with Slurm 22.05.2.  So long as you do the mysql_upgrade 
after the upgrade and have a backup just in case you should be fine.


-Paul Edmon-

On 8/24/22 1:58 AM, navin srivastava wrote:

Hi,

I have a question related to the mariadb vs slurm version compatibility.
Is there any matrix available?

We are running with slurm version 20.02 in our environment on 
SLES15SP3 and with mariadb 10.5.x . We are upgrading the OS from 
SLES15SP3 to SP4 and with this we see the mariadb version is 10.6.x. 
and we are not upgrading the Slurm version.


What is the best way to deal with this as we patch the server 
quarterly and keep the slurm version unchanged as I locked this at os 
level  but the mariadb version update happens and as far as i see it 
has no impact.
is it good idea to keep the mariadb version also intact with the slurm 
version?


Regards
Navin.

Re: [slurm-users] Kernel keyrings on Slurm node inside Slurm job

[Yair Yarom]

Hi,

I think you should look at pam_keyinit and add it to the slurm pam (the one
used with the UsePAM configuration).
We currently don't do this, but it's on the todo list to check it out...
(so I'm not sure if it will work, or if it's the right way to do this).


On Tue, 23 Aug 2022 at 16:36, Matthias Leopold <
matthias.leop...@meduniwien.ac.at> wrote:

> Hi,
>
> I want to access the kernel "user" keyrings inside a Slurm job on a
> Ubuntu 20.04 node. I'm not an expert on keyrings (yet), I just
> discovered that inside a Slurm job a keyring for "user: invocation_id"
> is used, which seems to be shared across all users of the executing
> Slurm node (other users can access/destroy my keys).
>
> The structure in a session run from Slurm looks like this (when using
> cifscreds):
>
> Session Keyring
>
>   989278347 --alswrv  0 0  keyring: _ses
>
>   446567140 s-rv  0 0   \_ user: invocation_id
>
>   638050420 sw-v  35816 10513   \_ logon: cifs:d:itsc-test2
>
>
> The structure in a SSH session looks like this (when using cifscreds):
>
> Session Keyring
>
>   932177825 --alswrv   1000  1000  keyring: _ses
>
>   826996940 --alswrv   1000 65534   \_ keyring: _uid.1000
>
> 1006610690 sw-v   1000  1000   \_ logon: cifs:d:itsc-test2
>
>
> I researched about this invocation_id and found a section on
> "KeyringMode=" in systemd.exec man page, but that didn't really help me.
>
> Can you explain to me how it would be possible to get "private" keyrings
> inside a Slurm job on the executing node?
>
> thx
> Matthias
>
>

-- 

  /|   |
  \/   | Yair Yarom | System Group (DevOps)
  []   | The Rachel and Selim Benin School
  [] /\| of Computer Science and Engineering
  []//\\/  | The Hebrew University of Jerusalem
  [//  \\  | T +972-2-5494522 | F +972-2-5494522
  //\  | ir...@cs.huji.ac.il
 //|

[slurm-users] maridb version compatibility with Slurm version

[navin srivastava]

Hi,

I have a question related to the mariadb vs slurm version compatibility.
Is there any matrix available?

We are running with slurm version 20.02 in our environment on SLES15SP3 and
with mariadb 10.5.x . We are upgrading the OS from SLES15SP3 to SP4 and
with this we see the mariadb version is 10.6.x. and we are not upgrading
the Slurm version.

What is the best way to deal with this as we patch the server quarterly and
keep the slurm version unchanged as I locked this at os level  but the
mariadb version update happens and as far as i see it has no impact.
is it good idea to keep the mariadb version also intact with the slurm
version?

Regards
Navin.