Re: [OMPI devel] PLM consistency: launch agent param
I suppose we could even just make it an mpirun cmd line param, at that point. As an MCA param, though, we have typically insisted on a particular syntax that includes framework and component... On 7/11/08 8:41 AM, "Don Kerr" wrote: > For something as fundamental as launch do we still need to specify the > component, could it just be "launch_agent"? > > Jeff Squyres wrote: >> Sounds good to me. We've done similar things in other frameworks -- >> put in MCA base params for things that all components could use. How >> about plm_base_launch_agent? >> >> >> On Jul 11, 2008, at 10:17 AM, Ralph H Castain wrote: >> >>> Since the question of backward compatibility of params came up... ;-) >>> >>> I've been perusing the various PLM modules to check consistency. One >>> thing I >>> noted right away is that -every- PLM module registers an MCA param to >>> let >>> the user specify an orted cmd. I believe this specifically was done so >>> people could insert their favorite debugger in front of the "orted" >>> on the >>> spawned command line - e.g., "valgrind orted". >>> >>> The problem is that this forces the user to have to figure out the >>> name of >>> the PLM module being used as the param is called "-mca >>> plm_rsh_agent", or >>> "-mca plm_lsf_orted", or...you name it. >>> >>> For users that only ever operate in one environment, who cares. However, >>> many users (at least around here) operate in multiple environments, >>> and this >>> creates confusion. >>> >>> I propose to create a single MCA param name for this value - >>> something like >>> "-mca plm_launch_agent" or whatever - and get rid of all these >>> individual >>> registrations to reduce the user confusion. >>> >>> Comments? I'll put my helmet on >>> Ralph >>> >>> >>> ___ >>> devel mailing list >>> de...@open-mpi.org >>> http://www.open-mpi.org/mailman/listinfo.cgi/devel >> >> > ___ > devel mailing list > de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/devel
Re: [OMPI devel] PLM consistency: launch agent param
For something as fundamental as launch do we still need to specify the component, could it just be "launch_agent"? Jeff Squyres wrote: Sounds good to me. We've done similar things in other frameworks -- put in MCA base params for things that all components could use. How about plm_base_launch_agent? On Jul 11, 2008, at 10:17 AM, Ralph H Castain wrote: Since the question of backward compatibility of params came up... ;-) I've been perusing the various PLM modules to check consistency. One thing I noted right away is that -every- PLM module registers an MCA param to let the user specify an orted cmd. I believe this specifically was done so people could insert their favorite debugger in front of the "orted" on the spawned command line - e.g., "valgrind orted". The problem is that this forces the user to have to figure out the name of the PLM module being used as the param is called "-mca plm_rsh_agent", or "-mca plm_lsf_orted", or...you name it. For users that only ever operate in one environment, who cares. However, many users (at least around here) operate in multiple environments, and this creates confusion. I propose to create a single MCA param name for this value - something like "-mca plm_launch_agent" or whatever - and get rid of all these individual registrations to reduce the user confusion. Comments? I'll put my helmet on Ralph ___ devel mailing list de...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/devel
Re: [OMPI devel] PLM consistency: launch agent param
Sounds good to me. We've done similar things in other frameworks -- put in MCA base params for things that all components could use. How about plm_base_launch_agent? On Jul 11, 2008, at 10:17 AM, Ralph H Castain wrote: Since the question of backward compatibility of params came up... ;-) I've been perusing the various PLM modules to check consistency. One thing I noted right away is that -every- PLM module registers an MCA param to let the user specify an orted cmd. I believe this specifically was done so people could insert their favorite debugger in front of the "orted" on the spawned command line - e.g., "valgrind orted". The problem is that this forces the user to have to figure out the name of the PLM module being used as the param is called "-mca plm_rsh_agent", or "-mca plm_lsf_orted", or...you name it. For users that only ever operate in one environment, who cares. However, many users (at least around here) operate in multiple environments, and this creates confusion. I propose to create a single MCA param name for this value - something like "-mca plm_launch_agent" or whatever - and get rid of all these individual registrations to reduce the user confusion. Comments? I'll put my helmet on Ralph ___ devel mailing list de...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/devel -- Jeff Squyres Cisco Systems
[OMPI devel] PLM consistency: launch agent param
Since the question of backward compatibility of params came up... ;-) I've been perusing the various PLM modules to check consistency. One thing I noted right away is that -every- PLM module registers an MCA param to let the user specify an orted cmd. I believe this specifically was done so people could insert their favorite debugger in front of the "orted" on the spawned command line - e.g., "valgrind orted". The problem is that this forces the user to have to figure out the name of the PLM module being used as the param is called "-mca plm_rsh_agent", or "-mca plm_lsf_orted", or...you name it. For users that only ever operate in one environment, who cares. However, many users (at least around here) operate in multiple environments, and this creates confusion. I propose to create a single MCA param name for this value - something like "-mca plm_launch_agent" or whatever - and get rid of all these individual registrations to reduce the user confusion. Comments? I'll put my helmet on Ralph
