Dear Jeff,
Thanks for your fast and helpful answer (and please excuse my being so
late in answering you).
> So LAM would have to translate that somehow. I'm open to suggestions
on
> how to do that...
>
> An off-the-top-of-my-head idea is that if the file
> $sysconfdir/lam-host-map.txt exists, the tcp RPI module will read it
at
> run-time and covert the lamd-supplied addresses/names as per the file.
> The file could be a very simple format, perhaps something like:
>
> -----
> # one entry per line
> pbs1.example.com mpi=internal-fast1.example.com
> pbs2.example.com mpi=internal-fast2.example.com
> -----
>
> The "mpi=" bit is there for two reasons:
>
> - indicate that MPI communications should use that address (as opposed
to
> LAM out-of-band communications and whatnot)
> - I can re-used the boot schema file parsing code and simply extract
the
> "mpi" key on each entry :-)
>
> How does that sound? Would that satisfy your requirements?
>
> (keep in mind that this would appear in 7.1 at the earliest)
This mechanism would indeed satisfy my request. May I suggest a small
enhancement using an environment variable named say LAMHOSTSMAP:
- if this variable is not set, no mapping will be done,
- if this variable is set, a mapping based on the file $LAMHOSTSMAP will
be done.
This would leave the possibility not to perform the mapping, or to
perform it using an alternate transformation (in case of three NICs for
instance).
Jean-Marie Teuler
|
