Skip to content

Meeting 2023 03 09

Jump to bottom
Thomas Naughton edited this page Mar 9, 2023 · 2 revisions

Agenda

Next PMIx ASC Monthly Meeting:
 * April 13, 2023

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

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
Aurelien Bouteiller UTK
Michael Karo Altair
Ken Raffenetti ANL
Ralph Castain Nanook
Norbert Eicker FZJ
Howard Pritchard LANL
Thomas Naughton ORNL
Isaias Compres TUM

Notes

  • PMIx v4 release update
    • https://github.com/pmix/pmix-standard/milestone/9
    • Josh created a work list of items to resolve for v4.2 release, help if have time
    • PMIx v4.2 standard tickets, plan to review and try to triage/assign ownership for items that need to be pulled into v4.2 tickets (see board).  Rough plan to try and get that triage before next month meeting, please take a look.
  • PMIx v5 release update
    • https://github.com/pmix/pmix-standard/milestone/6
    • move all v4.2 changelog items to v5.0 changelog and add remark that the change is between v4.1 to v5.0.
    • Need to update the v5.0 AUTHORS list (see #437)
    • Posted names and org to list to determine anyone that may have a name/spell change.  So far only 1 person responded, plan to continue and can edit as needed in future.
    • One person remaining to reach out to for confirmation.
    • This list included a number of people in the original RSE meeting, which included people from co-hosted MPI meeting.  Question of whether these people who may have just been present.  The general sentiment thus far has been to be inclusive and just include all who have been involved.
    • Discussion to just push v4.2 out to avoid possible confusion/omissions in the v5.0, for few items that might not yet have been pulled over.  So general sentiment is to carry the v4.2 items over to v5.0 to avoid this possible issue.
    • Need to take the ABI repo, resolve minor AUTHORs listing and few updates posted on PR.
  • CI for comparing OpenPMIx with PMIx Standard
    • https://github.com/openpmix/pmix-tests/pull/155
    • Look at triage file to see all symbols that need review
    • Status update - no symbols that have not been triaged.  Still have some that appear in the diff with v5 standard.  They are attributes with 1 API symbol.
    • These items need a champion to bring these ALLOC items over for provisional status in the v5.1 timeframe.
    • The Tools WG may be able to pick this up and champion it.
    • TODO: Add LINK to changes-std-v5 list
  • https://github.com/openpmix/pmix-tests/tree/master/check-standard/etcWorking Group Updates
    • IAWG (Dave)
      • Update from Ken, going chapter by chapter and looking into events chapter.  The publish/lookup has been put on hold for now and continue with other chapters.
      • Q: Ready to have something for reading on events at May meeting?
        • Yes, expect that is the plan
    • TDWG (Isaias)
      • Moving back to meeting on first Wednesday of month (easy to remember)
      • Working to map to current PMIx API and possibly make things a little simpler for users, but currently looks that can do the dynamic scheduler needs with the existing PMIx interfaces.
      • May need to work with Aurelian and others related to resilience for dealing with consistency on state.  Possibly do this discussion during the Tools WG timeslot. Next meeting April 5 at 5pm German time.
      • Suggestion: Update PMIx subscription calendar with this change.
      • Thomas: Will update Google calendar to 1st wed of month.
  • General
    • May want to review and existing tickets
    • Discussion about errata tickets for old v2 series.  Discussion about how to handle the errata in general.  In end plan is to just create a new minor release, as is case with other changes, and then can tell users to look at the latest version on a given series (e.g., v2 series would have a new v2.3 with these changes).  Simplifies where people should look for “latest” and major API/ABI changes require bump of major (first) number.
    • Discussion on adding text for a prototype requirement for Provisional acceptance.  Point made that it might be troublesome to have a formal requirement.  We have case example about tabling publish/lookup b/c there is not a plan for implementation, so seems we have precedence without needing to formalize.  Possibly raise for full discussion at next meeting as to fate of this suggestion for governance.
    • Please review standard check triage items
    • Note: For looking at triage items comparing standard vs. implementation
  • Open Discussion

Home

Working Groups

Events

Helpful How To...

ASC Quarterly Meetings

ASC Monthly Meetings

Clone this wiki locally