Register the singleton's nspace with the PMIx server

[bosilca]

Once we have created the necessary PRRTE infrastructure to support the singleton, we need to register that info with our internal PMIx server so it can be served to any requesting clients.

Signed-off-by: Ralph Castain [email protected]
(from upstream commit 89fdffe)

[github-actions]

Hello! The Git Commit Checker CI bot found a few problems with this PR:

8f3060e: Register the singleton's nspace with the PMIx serv...

• check_cherry_pick: contains a cherry pick message that refers to a commit that exists, but is in an as-yet unmerged pull request: 89fdffe

Please fix these problems and, if necessary, force-push new commits back up to the PR branch. Thanks!

[github-actions]

Hello! The Git Commit Checker CI bot found a few problems with this PR:

8f3060e: Register the singleton's nspace with the PMIx serv...

• check_cherry_pick: contains a cherry pick message that refers to a commit that exists, but is in an as-yet unmerged pull request: 89fdffe

Please fix these problems and, if necessary, force-push new commits back up to the PR branch. Thanks!

[hppritcha]

if we merge this and update the ompi main prrte sha to include this we will need to advance pmix sha. That may lead to mpi4py failures however.

[rhc54]

You cannot compile your PRRTE fork against PMIx upstream master - it is too out-of-sync. You'd have to switch back to upstream PRRTE.

[hppritcha]

we will not do that until open-mpi/ompi#12906 pass mpi4py

[rhc54]

we will not do that until open-mpi/ompi#12906 pass mpi4py

Understood and agreed - was only pointing out the problem. I'm working on it 😄