Skip to content

Meeting 2023 04 13

Thomas Naughton edited this page Apr 13, 2023 · 3 revisions

Agenda

Next PMIx ASC Monthly Meeting:
 * June 8, 2023
   - No monthly meeting in may due to 2Q 2023 meeting

PMIx ASC 2Q 2023 Meeting (Format: Virtual)
 * May 9 & 11, 2023 (10 am - 1 pm US Central)
   - April 11 : Announcement Deadline
   - April 25 : Agenda Finalization

PMIx ASC 3Q 2023 Meeting (Format: Virtual)
 * July 18 & 20, 2023 (10 am - 1 pm US Central)

PMIx ASC 4Q 2023 Meeting (Format: TBD - likely virtual)
 * Oct. 17 & 19, 2023 (10 am - 1 pm US Central)

Attendance

Person Institution
Josh Hursey IBM
Aurelien Bouteiller UTK
Michael Karo Altair
Thomas Naughton ORNL
Ken Raffenetti ANL
Norbert Eicker JSC
Dave Solt IBM

Notes

  • Note: No May monthly meeting, instead ASC Quarterly meeting (May 9 & 11)
  • PMIx v4.2 release update
    • Planning for July
  • PMIx v5.0 release update
    • Got author lists and revision bits resolved
    • Need to update Copyright and generate candidate PDF, but an item was raised during proofing
      • Q: about provisional items? – looks like a non-issue
      • Q: question about error codes from APIs and details in standard regarding latitude for implementations to return different values (text occurs in advise block, so non-normative). May want to change this due to ABI to clarify that implementer should follow certain values.  Question as to whether this should be an errata, editorial change, or how to handle.
      • Q: Are people ok with having this as an editorial change to update the advise to users.
        • Possible Options:
          • Strike all text
          • Update text to advise user to refer to constants by name
          • Strike text except for the piece about keeping PMIX_EXTERNAL_ERR_BASE.
        • Plan to discuss on github and deal with it as editorial change.
      • Need to cleanup the “PMIx v4.2” provisional markings.  Seems like editorial change.
    • General thoughts were that since this is non-normative text, so it is ok to make the changes as editorial edits.
  • Review drift in PMIx and OpenPMIx
    • 10 symbols added, need review (missing from PMIx standard)
    • 200 symbols are in triage file
    • Check the report on github
    • May want to make a pass on this at Quarterly ASC, possibly add some work time for this meeting (already have time blocked off if agenda is light).
  • Working Group Updates
    • Implementation Agnostic WG
      • Josh gave update
      • Been working on datatypes chapter, pack/unpack.  Not ready for next quarterly, but may want to have a preview in May.
      • also made it through the events chapter
      • Dave: Relationship between malloc/free, there is text stating that items are allocated by library and then user can free them.  But there is not a release function.  Or cases where things state the library will free something up.  May need to tighten up the text related to this memory alloc code.  Unsure how much time to spend on this in WG at moment.
      • Malloc/free bits seem pretty broad (span chapters) and may need to pull out and tackle on its own.  Probably will capture issue in a ticket & can deal with as time permits.
    • Tools & Dynamic Workflows WG
      • Norbert gave update
      • Much discussion lately on malleability, more work has been taking place outside the standard itself.  Using the WG to have broader discussions and clarifying when/where PMIx plays a role.
      • Aurelien: Mentioned that in MPI Forum, Martin Schriber mentioned some malleability related changes and whether it makes sense to have this in MPI or if it should be in PMIx.  That discussion is taking place in the MPI session working group.  Seems very relevant to what this WG is doing.
      • Ken: MPICH library is also working to integrate changes related to sessions support and another related work for this malleability work.
Clone this wiki locally