Closed
Description
Suggestion of having "global" and "local" MCA parameters in MCA config files.
- Local MCA params would be exactly what they are today (and in the absence of a designator, params default to local -- for backwards file format compatability), meaning that they are not sent to processes on remote nodes.
- Global MCA params would be bundled up by orterun and sent to all processes in the job, even if the user did not override those MCA parameters on the command line (or environment or ...) or not.
The intent is to be able to have a central set of MCA params that comes from a single location (i.e., you don't need to propagate the MCA params config file to all nodes in the job).