Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify how PMIX_PREFIX should be handled by the server side in PMIx_Spawn context #506

Open
krempel-pt opened this issue Mar 22, 2024 · 2 comments
Assignees

Comments

@krempel-pt
Copy link

We stumbled over this point while implementing our PMIx host server for the ParaStation MPI process management.

Is in unclear how and by whom PMIX_PREFIX if specified should be applied to the command. Discussing this with @rhc54 in openpmix/openpmix#3321 lead to implementing it in the server library, but then it must not be passed upwards to the host server, since it would not be able to detect whether it is already applied or not. So the suggestion is to clearly define that in the standard:

Suggested Clarification

If the implementation handles the prefix, then it must remove the PMIX_PREFIX attribute before passing the keys up to the server. If the server sees a PMIX_PREFIX key, then it must handle it.

References

17.3.11

@dsolt
Copy link
Contributor

dsolt commented Mar 25, 2024

Our working group is working on fixes to improve the process management chapter. (there is a PR open currently). As of now we do not have any textual changes around this, but I wanted to follow this as we can include changes in that PR if it helps move things along quicker.

@abouteiller
Copy link
Contributor

24Q2: we like the proposed text, advice to implementor.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants