Even PRRTE won’t allow you to stop the orted from initializing its PMIx server. I’m not sure I really understand your objective. Remember, PMIx is just a library - the orted opens it and uses it to interface to its client application procs. It makes no sense to have some other process perform that role as it won’t know any job-level information.
It sounds like what you really want to do is replace the orted, and have your orted open your PMIx server? In other words, you want to use the PMIx reference library to handle all the PMIx stuff, and provide your own backend functions to support the PMIx server calls? If so, then your best bet would be to edit the PRRTE code in orte/orted/pmix and replace it with your code. You’ll have to deal with the ORTE data objects and PRRTE’s launch procedure, but that is likely easier than trying to write your own version of “orted” from scratch. As for Slurm: it behaves the same way as PRRTE. It has a plugin that implements the server backend functions, and the Slurm daemons “host” the plugin. What you would need to do is replace that plugin with your own. Ralph > On Oct 8, 2018, at 5:36 PM, Gilles Gouaillardet <gil...@rist.or.jp> wrote: > > Stephan, > > > Have you already checked https://github.com/pmix/prrte ? > > > This is the PMIx Reference RunTime Environment (PPRTE), which was built on > top of orted. > > Long story short, it deploys the PMIx server and then you start your MPI app > with prun > An example is available at > https://github.com/pmix/prrte/blob/master/contrib/travis/test_client.sh > > > Cheers, > > Gilles > > > On 10/9/2018 8:45 AM, Stephan Krempel wrote: >> Hallo everyone, >> >> I am currently implementing a PMIx server and I try to use it with >> OpenMPI. I do have an own mpiexec which starts my PMIx server and >> launches the processes. >> >> If I launch an executable linked against OpenMPI, during MPI_Init() the >> ORTE layer starts another PMIx server and overrides my PMIX_* >> environment so this new server is used instead of mine. >> >> So I am looking for a method to prevent orte(d) from starting a PMIx >> server. >> >> I already tried to understand what the slurm support is doing, since >> this is (at least in parts) what I think I need. Somehow when starting >> a job with srun --mpi=pmix_v2 the ess module pmi is started, but I was >> not able to enforce that manually by setting an MCA parameter (oss >> should be the correct one?!?) >> And I do not yet have a clue how the slurm support is working. >> >> So does anyone has a hint for me where I can find documentation or >> information concerning that or is there an easy way to achieve what I >> am trying to do that I missed? >> >> Thank you in advance. >> >> Regards, >> >> Stephan >> _______________________________________________ >> devel mailing list >> email@example.com >> https://lists.open-mpi.org/mailman/listinfo/devel >> > > _______________________________________________ > devel mailing list > firstname.lastname@example.org > https://lists.open-mpi.org/mailman/listinfo/devel _______________________________________________ devel mailing list email@example.com https://lists.open-mpi.org/mailman/listinfo/devel