Well we actually use a patched version of SLURM, 2.2.0-pre8. It is
planned to submit the modifications made internally at CSCS for the next
SLURM release in November. We implement ALPS support based on the basic
architecture of SLURM.
SLURM is only used to do the ALPS ressource allocation. We then use
mpirun based on the portals and on the alps libaries.
We don't use mca parameters to direct selection and the alps RAS is
automatically well selected.
On 07/09/2010 01:59 PM, Ralph Castain wrote:
> Forgive my confusion, but could you please clarify something? You are
> using ALPS as the resource manager doing the allocation, and then
> using SLURM as the launcher (instead of ALPS)?
> That's a combination we've never seen or heard about. I suspect our
> module selection logic would be confused by such a combination - are
> you using mca params to direct selection?
> On Jul 9, 2010, at 4:19 AM, Jerome Soumagne wrote:
>> We've recently installed OpenMPI on one of our Cray XT5 machines,
>> here at CSCS. This machine uses SLURM for launching jobs.
>> Doing an salloc defines this environment variable:
>> The reservation ID on Cray systems running ALPS/BASIL only.
>> Since the alps ras module tries to find a variable called
>> OMPI_ALPS_RESID which is set using a script, we thought that for
>> SLURM systems it would be a good idea to directly integrate this
>> BASIL_RESERVATION_ID variable in the code, rather than using a
>> script. The small patch is attached.
>> Jérôme Soumagne
>> Scientific Computing Research Group
>> CSCS, Swiss National Supercomputing Centre
>> Galleria 2, Via Cantonale | Tel: +41 (0)91 610 8258
>> CH-6928 Manno, Switzerland | Fax: +41 (0)91 610 8282
>> devel mailing list
>> devel_at_[hidden] <mailto:devel_at_[hidden]>
> devel mailing list
Scientific Computing Research Group
CSCS, Swiss National Supercomputing Centre
Galleria 2, Via Cantonale | Tel: +41 (0)91 610 8258
CH-6928 Manno, Switzerland | Fax: +41 (0)91 610 8282