Thanks Piotr - I'll apply that and move it to the 1.7 branch. Some of us are trying to test the pmi2 support in 2.6.0 and hitting a problem. We have verified that the pmi2 support was built/installed, and that both slurmctld and slurmd are at 2.6.0 level. When we run "srun --mpi-list", we get:
srun: MPI types are... srun: mpi/mvapich srun: mpi/pmi2 srun: mpi/mpich1_shmem srun: mpi/mpich1_p4 srun: mpi/none srun: mpi/lam srun: mpi/openmpi srun: mpi/mpichmx srun: mpi/mpichgm So it looks like the install is correct. However, when we attempt to run a job with "srun --mpi=pmi2 foo", we get an error from the slurmd on the remote node: slurmd[n1]: mpi/pmi2: no value for key in req and the PMI calls in the app fail. Any ideas as to the source of the problem? Do we have to configure something else, or start slurmd with some option? Thanks Ralph On Jul 18, 2013, at 2:02 AM, Piotr Lesnicki <piotr.lesni...@ext.bull.net> wrote: > Hello, > > I think there a few things still missing in openmpi pmi2 to make it work with > slurm. We are the ones at Bull who integrated the pmi2 code from mpich2 to > slurm. The attached patch should fix the issue (call slurm with --mpi=pmi2). > This still needs to be checked with other pmi2 implemenations (we use pmi2.h > but some use pmi.h ? constants are prefixed with PMI2_ but some use PMI_ ?). > > Piotr Lesnicki > <pmi2.patch>
