Nate Coraor
2014-10-08 14:26:29 UTC
Hi all,
For the last few days I've been working on adding support for the
-M/--clusters option to slurm-drmaa. I have it working but it's taken
a few hacks:
1. I cannot see any public way to actually use the multi-cluster
functionality. It's possible to query slurmdbd for all the cluster
info you can get with sacctmgr via the public API, but I had to expose
working_cluster_rec in libslurmdb to be able to use those cluster
records for submit and status requests. Of course this will not work
with any standard installations (and may not be entirely safe).
2. I'm using the non-published slurmdb_get_info_clusters() function to
get cluster records. It's possible to get them with the public
slurmdb_clusters_get() function, but for some reason the
plugin_id_select returned by the latter (and indeed, as found in
slurmdbd's database) is incorrect for both clusters (both are 101 in
slurmdbd, should be 2).
Could anyone provide guidance on how to fix these? Am I going at this all wrong?
Thanks,
--nate
For the last few days I've been working on adding support for the
-M/--clusters option to slurm-drmaa. I have it working but it's taken
a few hacks:
1. I cannot see any public way to actually use the multi-cluster
functionality. It's possible to query slurmdbd for all the cluster
info you can get with sacctmgr via the public API, but I had to expose
working_cluster_rec in libslurmdb to be able to use those cluster
records for submit and status requests. Of course this will not work
with any standard installations (and may not be entirely safe).
2. I'm using the non-published slurmdb_get_info_clusters() function to
get cluster records. It's possible to get them with the public
slurmdb_clusters_get() function, but for some reason the
plugin_id_select returned by the latter (and indeed, as found in
slurmdbd's database) is incorrect for both clusters (both are 101 in
slurmdbd, should be 2).
Could anyone provide guidance on how to fix these? Am I going at this all wrong?
Thanks,
--nate