[slurm-users] Slurm Perl API use and examples
Marcus Wagner
wagner at itc.rwth-aachen.de
Wed Mar 25 13:33:06 UTC 2020
Hi John,
no, we just use the API for monitoring issues.
Best
Marcus
Am 25.03.2020 um 13:35 schrieb Burian, John:
> Marcus,
>
> Do you use the Perl API to submit jobs/request allocations, or only to query the state of jobs, etc.? If you submit jobs, how do you populate the hash that is passed as a job_desc_msg_t structure? Thanks,
>
> John
>
>
> -----Original Message-----
> From: slurm-users <slurm-users-bounces at lists.schedmd.com> on behalf of Marcus Wagner <wagner at itc.rwth-aachen.de>
> Reply-To: Slurm User Community List <slurm-users at lists.schedmd.com>
> Date: Tuesday, March 24, 2020 at 9:49 AM
> To: "slurm-users at lists.schedmd.com" <slurm-users at lists.schedmd.com>
> Subject: Re: [slurm-users] Slurm Perl API use and examples
>
> [WARNING: External Email - Use Caution]
>
> In fact, we ARE using the perl API, but there are some flaws.
>
> E.g. the array_task_str of the jobinfo structure. Slurm abbreviates long
> list of array indices, like scontrol does:
>
> e.g.
> 1-3,5-8,45-...
>
> yes, you can really find there three dots. In my opinion, this is ok for
> a general tool like scontrol to abbreviate the output, but it does not
> make any sense within a API.
>
> Does anyone know, if the C-API also abbreviates things like that?
>
>
> Best
> Marcus
>
> Am 23.03.2020 um 20:47 schrieb Burian, John:
> > I have some questions about the Slurm Perl API
> > - Is it still actively supported? I see it's still in the source in Git.
> > - Does anyone use it? If so, do you have a pointer to some example code?
> >
> > My immediate question is, for methods that take a data structure as an input argument, how does one define that data structure? In Perl, it's just a hash, am I supposed to populate the keys of the hash by reading the matching C structure in slurm.h? Or do I only need to populate the keys that I care to provide a value for, and Slurm assigns defaults to the other keys/fields? Thanks,
> >
>
>
>
More information about the slurm-users
mailing list