Skip to content

Meeting 2021 04 08

Jump to bottom
Thomas Naughton edited this page Apr 8, 2021 · 5 revisions

Agenda

Attendees

Josh Hursey (IBM)
Thomas Naughotn (ORNL)
Ken Raffenetti (ANL)
Michael Karo (Altair)
Kathryn Mohror (LLNL)
Stephen Herbein (LLNL)
David Solt (IBM)
Aurelien Bouteiller (UTK)

Notes

  • Next Meetings and Deadlines
    • April 8, 2021 : Monthly Meeting
    • April 13, 2021 : Submissions for ASC agenda items due
    • April 27, 2021 : Finalize ASC agenda
    • (No monthly meeting in May due to ASC quarterly meeting)
    • May 11 & May 13, 2021 : ASC 2Q 2021 Meeting
    • June 10, 2021 : Monthly Meeting
  • ASC Quarterly
    • Items due 13-apr and skip the May meeting b/c of quarterly
  • PMIx Release Updates
    • v4 - Josh, some errata and soon have v4.1 (target summer)
    • v5 - Ken, no news to report
  • Software in the Public Interest (SPI) Update
    • Informally approved, but not received the official final paperwork yet
  • Debrief ECP Community BoF
  • PMIx Standard PRs
    • Items from the agenda that didn’t make the cut last ASC meeting, these will now be scheduled for next ASC
    • The group needs to review and vote in straw-polls asap
  • Governance PRs
    • Versioning and watermarking so that the governance document looks like the main standard document. https://github.com/pmix/governance/pull/28; This is all editorial, the chairs will have to decide if we need to take a vote, but it looks like not.
    • Small clarification on the number of secretary positions (2), consistent with what we have been doing https://github.com/pmix/governance/pull/31
    • Clarification of errata and major change process Major Text Change Process Errata Changes Process are ready for straw vote/review
    • Prototype requirement for provisional acceptance: last telecon did not settle the issue, discussion continues on issue https://github.com/pmix/governance/issues/27 ; please react on the issue, even if to just say ‘cool’
  • PMIx Standard PRs
    • Debugger events for coordination https://github.com/openpmix/openpmix/pull/2149#issuecomment-813639845
    • Discussion during call
      • PMIX_DEBUG_STOP_ON_EXEC, xxx_STOP_IN_INIT - changed from bool to list type
      • These are already out there, so changing behaviour maybe not so good.  So possibly deprecate and propose an alternative with new behaviour.
      • The current change would require existing uses to change calls in pretty mechanical way (bool to list), possibly regex able for simple instances.
      • Q: How would the aggregated PMIX_READY_FOR_DEBUG operate if an error occurred from one of the sub-instances (targets)?
      • Not sure, possibly something to look into
      • Discussion about how these bits behave for the debugger attach procedure
      • Q: Is there a good way to reflect that a deprecated item is notified in the openpmix implementation?
      • Deprecated list is in the standard, need to check on openpmix implementation
      • Plan to present more formal summary of these changes in future
    • Clarify three roles of consumers the PMIx interface review is easier by watching commits of the PR individually
      • 1st commit Depiction of the general use cases, server launch clients, tools etc.
      • Some wordsmithing still coming
      • 2nd commit advice to implementor that a library may be only one of the three roles and remain compliant (e.g., implement only the client interface and do the rest of the pmix-magic in some custom way)
      • Need some feedback on the client-role only, and similar name. What do people think about “role-compliance” terms?
      • Q: do we expect someone will really implement only client-server, but not tools? Yes, tools backend may add complexity, and maybe the RM doesn’t care about supporting tools, or targets a high throughput scenario where tool support would slow things down
      • C: maybe not concatenating the client-server-role, but instead enumerate client-role,server-role
    • Spontaneous discussion: slice-WG: can we have a way to list supported functionality?
      • We had a table on the website with Slurm, JSrun, etc. showing what functionality slices are currently supported, table was not found, but was great
      • the WG can take the mission of reviving that table, reach out to users to make sure that the table is correct
      • Note that roles and use-cases may not match 1-1 (one may support the tool role, but support only some tool use-cases).
  • Provisional Item Discussion
    • (no pr yet, Kathryn presented a highlighted standard document);
    • The text that will become a ‘required’ attribute (when moving from provisional to stable) should be marked as such in the text;
    • Stable entries can also be changed by errata
    • We may remove the confusing statement about ‘stable not being cross-compatible with provisional), this is already stated in the provisional section; need double checking
    • Major change proposed on voting rule for provisional (make it a real vote at the ASC rather than a github emoji vote); people are conflicted about it, requires more discussion
  • Working Group Updates
    • Ran out of time

Home

Working Groups

Events

Helpful How To...

ASC Quarterly Meetings

ASC Monthly Meetings

Clone this wiki locally