1
1
openmpi/orte/mca/plm
Ralph Castain a62b2a0150 Per the July technical meeting:
Standardize the handling of the orte launch agent option across PLMs. This has been a consistent complaint I have received - each PLM would register its own MCA param to get input on the launch agent for remote nodes (in fact, one or two didn't, but most did). This would then get handled in various and contradictory ways.

Some PLMs would accept only a one-word input. Others accepted multi-word args such as "valgrind orted", but then some would error by putting any prefix specified on the cmd line in front of the incorrect argument.

For example, while using the rsh launcher, if you specified "valgrind orted" as your launch agent and had "--prefix foo" on you cmd line, you would attempt to execute "ssh foo/valgrind orted" - which obviously wouldn't work.

This was all -very- confusing to users, who had to know which PLM was being used so they could even set the right mca param in the first place! And since we don't warn about non-recognized or non-used mca params, half of the time they would wind up not doing what they thought they were telling us to do.

To solve this problem, we did the following:

1. removed all mca params from the individual plms for the launch agent

2. added a new mca param "orte_launch_agent" for this purpose. To further simplify for users, this comes with a new cmd line option "--launch-agent" that can take a multi-word string argument. The value of the param defaults to "orted".

3. added a PLM base function that processes the orte_launch_agent value and adds the contents to a provided argv array. This can subsequently be harvested at-will to handle multi-word values

4. modified the PLMs to use this new function. All the PLMs except for the rsh PLM required very minor change - just called the function and moved on. The rsh PLM required much larger changes as - because of the rsh/ssh cmd line limitations - we had to correctly prepend any provided prefix to the correct argv entry.

5. added a new opal_argv_join_range function that allows the caller to "join" argv entries between two specified indices

Please let me know of any problems. I tried to make this as clean as possible, but cannot compile all PLMs to ensure all is correct.

This commit was SVN r19097.
2008-07-30 18:26:24 +00:00
..
alps Per the July technical meeting: 2008-07-30 18:26:24 +00:00
base Per the July technical meeting: 2008-07-30 18:26:24 +00:00
bproc Fixes trac:1392, #1400 2008-07-28 22:40:57 +00:00
ccp Per the July technical meeting: 2008-07-30 18:26:24 +00:00
lsf Per the July technical meeting: 2008-07-30 18:26:24 +00:00
process Fixes trac:1392, #1400 2008-07-28 22:40:57 +00:00
rsh Per the July technical meeting: 2008-07-30 18:26:24 +00:00
slurm Per the July technical meeting: 2008-07-30 18:26:24 +00:00
submit Fixes trac:1392, #1400 2008-07-28 22:40:57 +00:00
tm Per the July technical meeting: 2008-07-30 18:26:24 +00:00
tmd Fixes trac:1392, #1400 2008-07-28 22:40:57 +00:00
xgrid Allow xgrid to compile. 2008-07-29 13:24:08 +00:00
Makefile.am Merge the ORTE devel branch into the main trunk. Details of what this means will be circulated separately. 2008-02-28 01:57:57 +00:00
plm_types.h Upgrade the node/orted failure detection code to cover all environments. Use the native environment's capabilities where possible - e.g., SLURM detects orted failure and can report it. Elsewhere, use a heartbeat system to detect orted failure - e.g., for TM and rsh. Heart rate is set via mca param. The HNP checks for callback every 2*heartrate, declares orted failure if not seen in last 2*heartrate time. 2008-06-02 21:46:34 +00:00
plm.h Fixes trac:1392, #1400 2008-07-28 22:40:57 +00:00