This repo adds basic pmix support to Flux. It contains two main components
The former is loaded by requesting it on the job submission command line, e.g.
$ flux run -o pmi=pmix myprogramThe latter may be selected on the broker command line, e.g.
$ jsrun flux start -o,-Sbroker.boot-method=pmixor by setting the FLUX_PMI_CLIENT_METHODS environment variable globally:
FLUX_PMI_CLIENT_METHODS="simple pmix single"The pmix specs cover a broad range of topics. Although the shell plugin is based on the openpmix "reference implementation", it only populates callbacks and attributes needed to bootstrap some versions of openmpi. As such, the pmix interface offered by this plugin should not be used for advanced use cases such as: debugger/tool interfaces, process spawn, resource allocation, job control, I/O forwarding, process groups, fabric support, storage support, event notification, or mpi sessions.
Bootstrap scalability with this plugin is likely to be on par with Flux PMI-1, since fence is implemented with the same collective algorithm as PMI-1, and the cost of fence will dominate for the larger jobs.
Although Flux can now launch Flux with pmix by combining the two capabilities
provided by this project, this is not advisable as the Flux pmix server does
not pre-populate keys that Flux expects to find in the PMI KVS when launched
in a hierarchy, such as flux.instance-level and flux.taskmap.
While other MPIs such as mpich and derivatives have optional pmix bootstrap support, using pmix to launch them under Flux is neither well tested nor expected to confer any advantage over the PMI-1 default.
Since the pmix server is embedded in the flux-shell, it is completely initialized and torn down for each job, and runs unprivileged as the job owner.
SPDX-License-Identifier: LGPL-3.0
LLNL-CODE-764420