[mvapich-discuss] mpd hostname resolution?

[Kenneth Yoshimoto]

On Tue, 22 Feb 2011, Pavan Balaji wrote:

> Date: Tue, 22 Feb 2011 20:37:24 -0600
> From: Pavan Balaji <balaji at mcs.anl.gov>
> To: Kenneth Yoshimoto <kenneth at sdsc.edu>
> Cc: James Dinan <dinan at mcs.anl.gov>, mvapich-discuss at cse.ohio-state.edu
> Subject: Re: [mvapich-discuss] mpd hostname resolution?
> 
>
> On 02/22/2011 08:01 PM, Kenneth Yoshimoto wrote:
>>  If hydra requires passwordless ssh to the compute nodes, I am unable
>>  to use it.
>
> You don't want to setup passwordless ssh? What launcher does your system use?

I'm trying to run across separate clusters, so my launcher is gsissh-qsub.
A version of MPICH2 mpd has worked for me in the past, so I wanted to try
MVAPICH2 mpd.

>
> Most process managers (Hydra, mpirun_rsh, and even MPD if you use mpdboot) 
> require some form of automatic remote launching capability, such as ssh, rsh, 
> slurm, poe, lsf.
>
>>  From the docs, it seems that mpd is still an option.  Is it broken
>>  and unsupported?
>
> MPD was developed by the MPICH2 group and is not supported anymore. MVAPICH 
> folks *might* still be supporting it, but I don't believe so.

If MPD is not supported, then I'll look for other alternatives.

Thanks,
Kenneth

>
> You can tweak MPD as you are doing to get it to work without using 
> passwordless ssh, but that's internal usage and not meant to be directly used 
> that way by users.
>
>>  Or is there a way to bring Hydra up in a batch job, without
>>  ssh/rsh/slurm?
>
> There's an experimental launcher called "persist" in Hydra, which is meant 
> for manual launching (like what you are currently doing). We were working on 
> it to allow Hydra to work on Windows, but it's *really* experimental. You are 
> welcome to poke around with it, but it's *totally* unsupported.
>
> -- Pavan
>
>