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 three roles of consumers of the PMIx interface #327

Merged
merged 3 commits into from
Jul 26, 2021

Conversation

jjhursey
Copy link
Member

Signed-off-by: Joshua Hursey [email protected]

@jjhursey jjhursey added the WorkInProgress Work In Progress label Jan 12, 2021
@jjhursey
Copy link
Member Author

@dsolt I'd like the IAWG to take a look at this before putting it forward. Maybe we can do so next week.
I'll leave it in draft/WIP until the WG gives it 👍

@jjhursey
Copy link
Member Author

@dsolt Let's add this to the working group agenda to review in the next week or two. We reviewed it last year, so I'm hoping it won't take too long.

@jjhursey jjhursey force-pushed the 3-roles branch 2 times, most recently from 0bef604 to 3869615 Compare April 5, 2021 20:23
@jjhursey
Copy link
Member Author

jjhursey commented Apr 5, 2021

I pushed the changes requested from the WG meeting on April 5, 2021

@jjhursey jjhursey added this to the PMIx v5 Standard milestone Apr 6, 2021
@jjhursey
Copy link
Member Author

jjhursey commented Apr 8, 2021

Notes from PMIx ASC Meeting April 8, 2021:

  • The Client role definition needs to allow for singletons (not started by an RM)
  • Naming:
    • Remove the -only suffix
    • Consider moving towards a list and removing the -and-. For example client-role,tool-role \ac{PMIx} standard compliant
  • Use case compliance can be a separate qualifier on the PMIx and RM requirements.

@jjhursey jjhursey marked this pull request as ready for review April 13, 2021 18:34
@jjhursey jjhursey added Eligible Eligible for consideration by ASC RFC Request for Comment and removed WorkInProgress Work In Progress Eligible Eligible for consideration by ASC labels Apr 13, 2021
@jjhursey
Copy link
Member Author

Please use emoji reactions ON THIS COMMENT to indicate your position on this proposal.

  • You do not need to vote on every proposal
  • If you have no opinion, don't vote - that is also useful data
  • If you've already commented on this issue, please still vote so
    we know your current thoughts
  • Not all proposals solve exactly the same problem, so we may end
    up accepting proposals that appear to have some overlap
    This is not a binding majority-rule vote, but it will be a very
    significant input into the corresponding ASC decision.

Here are the meanings for the emojis:

  • Hooray or Rocket: I support this so strongly that I
    want to be an advocate for it
  • Heart: I think this is an ideal solution
  • Thumbs up: I'd be happy with this solution
  • Confused: I'd rather we not do this, but I can tolerate it
  • Thumbs down: I'd be actively unhappy, and may even consider
    other technologies instead
    If you want to explain in more detail, feel free to add another
    comment, but please also vote on this comment.

@jjhursey jjhursey changed the title Clarify three roles of consumers the PMIx interface Clarify three roles of consumers of the PMIx interface Apr 15, 2021
@jjhursey jjhursey added the Eligible Eligible for consideration by ASC label Apr 15, 2021
@jjhursey jjhursey self-assigned this Apr 26, 2021
@kathrynmohror
Copy link
Collaborator

@jjhursey This PR passed its first vote on the condition that you apply the changes in the comments that contain the text 'revision exception'

@kathrynmohror kathrynmohror added the First Vote Passed ASC first vote passed label May 14, 2021
@jjhursey
Copy link
Member Author

  • Revision exception changes have now been committed to this branch.
  • I'll bring this for second vote in the 3Q 2021 meeting

@jjhursey
Copy link
Member Author

PMIx ASC 2Q 2021: May 11 & May 13

  • Passed first vote with Revision Exception: 7 yes / 0 no / 1 abstain
    • Failed without the Revision Exception): 1 yes / 4 no / 3 abstain
  • Eligible for second vote 3Q 2021 ASC Meeting
  • I confirmed that the Revision Exception has been applied.

@jjhursey
Copy link
Member Author

PMIx ASC 3Q 2021

  • Passed the second vote: 7 yes / 0 no / 2 abstain
  • Will be merged into the master branch targeting PMIx v5.0

@jjhursey jjhursey added the Accepted as Stable ASC second vote passed. Accepted as Stable! label Jul 22, 2021
jjhursey and others added 3 commits July 26, 2021 13:49
 * Clarify the three roles of consumers of the PMIx interface (clients / servers / tools)

Signed-off-by: Joshua Hursey <[email protected]>
Signed-off-by: Joshua Hursey <[email protected]>
@jjhursey
Copy link
Member Author

I rebased and merged this PR. It'll be in the v5 version of the document.

@jjhursey jjhursey merged commit 38029e5 into pmix:master Jul 26, 2021
@jjhursey jjhursey deleted the 3-roles branch July 26, 2021 18:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accepted as Stable ASC second vote passed. Accepted as Stable! Eligible Eligible for consideration by ASC First Vote Passed ASC first vote passed RFC Request for Comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants