-
Notifications
You must be signed in to change notification settings - Fork 22
ASC Q2 2025 Meeting
- Date: May. 6 & 8, 2025
- Time: 10 am - 1 pm US Central Daylight Time each day
- Location: Virtual Meeting. Zoom Info (link also in the Active notes Google doc below)
- Active Notes Link: Google Doc - Please add your name and affiliation.
- Governance Document [latest]
- Voting Link
This meeting has a floating agenda with specific synchronization points to keep us on track. Rough time estimates are provided per agenda item, and the co-chairs plan to cover the topics in the order seen below. However, since some agenda items will take longer/shorter than anticipated, an exact start/end timing is not guaranteed, and some items may float to the second day. If you cannot attend the full meeting and are presenting, please let the co-chairs know, and we can plan accordingly.
Start | End | Topic |
---|---|---|
10:00 am | 10:05 am | Gathering (--) |
10:05 am | 10:10 am | Roll Call |
10:10 am | 11:30 am | Discussion of agenda items |
11:30 am | 11:45 am | Break |
11:45 am | 1:00 pm | Discussion of agenda items |
-
Administrative announcement
- Calendar FY25
- ASC 25Q3: July 15, 17
- ASC 25Q4: Oct 14, 16
- Open PMIx ASC position:
- co-secretary: Open
- SPI 2024 report (due 5/14)
- Calendar FY25
-
Officer nominations:
-
Working Groups Updates:
- IAWG (Dave Solt)
- Dynamic/Tools (Isaias Compres)
- Call for new WGs?
-
Release planning
-
5.1v6.0- Elevations from v5 to non-provisional -- completed review, ready for PRs
- #516 - Add a description of what is an errata
- https://github.com/pmix/pmix-standard/milestone/10
-
-
Governance Votes
- None
-
Governance PRs up for a Reading (Errata):
- None
-
Governance PRs up for a Second Vote:
- None
-
Governance PRs up for a Reading and First Vote:
- None
-
PMIx Standard PRs up for a Reading (Provisional):
- None
-
PMIx Standard PRs up for a Reading (Errata):
- None
-
PMIx Standard PRs up for a Second Vote:
- None
-
PMIx Standard PRs up for a Reading and First Vote:
- None
-
Plenary discussion items
- #41 - Update README.md
- PMIx-Examples
- Roadmap/planning discussion
- Propose: Cancel 25Q2 Day-2 (Thu)
- Other/Open discussion
Person | Institution | Day 1 | Day 2 |
---|---|---|---|
Aurelien Bouteiller | AMD | X | |
Ken Raffenetti | ANL | X | |
Thomas Naughton | ORNL | X | |
Howard Pritchard | LANL | X | |
Norbert Eicker | JSC | X |
- Release planning
- v6.0
- #518 - Elevate Provisional from v5 to non-provisional, https://github.com/pmix/pmix-standard/issues/518
- Status: Have completed review, ready for PRs
- Make a review/triage of the drift items (script autogens) – possibly start separate ticket on this item. – Possibly just part of v6.0 milestone review and keep items in milestone if needed.
- #516 - Add a description of what is an errata, https://github.com/pmix/pmix-standard/pull/516
- Status: Review v4.1 history and see if already discussed/voted
- v6.0 Milestone: https://github.com/pmix/pmix-standard/milestone/10
- Status: Need to triage and prune/prompt items
- #518 - Elevate Provisional from v5 to non-provisional, https://github.com/pmix/pmix-standard/issues/518
- v6.0
- Plenary discussion items
- #41 - Update README.md, https://github.com/pmix/governance/pull/41
- PMIx-Examples
- https://pmix-examples.readthedocs.io
- Misc: Need permissions to transfer to pmix Github org
- Looks like Ralph/JoshH/JeffS have org admin permissions and can help
- Q: Level of review for pmix-examples material?
- Consensus was that do not want lots of formality
- Possibly have CI checks for reviews on github and for verifications
- Maybe have N reviews required before merge
- No need for format voting as not making changes to the Standard
- Github setups
- Add an “examples” label and maybe a new “examples” issues template
- Add CI to check tests/code
- Examples likely to be good method for driving ASC discussion (see “roadmap” discussion below)
- Roadmap/planning discussion
- V6.0 cleanup
- Triage old issues - cleanout/archive of issues in pmix-standard (possibly revive past items that have been forgotten, or squash as done/not interesting, etc.)
- Examples for use case
- Discussion: Interoperability client/server “wire protocol”?
- Example of singleton detection
- Possibly have standard wire protocol in project daemons
- Possibly eliminate client/server incompatibility problem
- Q: is wire protocol encapsulated in openpmix?
- Example contrasting point is mpich’s hydra that uses string based wire protocol
- Questions about status for protocol between client/server (not necessarily inter-daemon itself)
- Q: How does this differ from cross-version compat?
- Possibly create an example for client/server interoperability to have better insights on this topic
- High value item is walk-through PMIx_Init and what is involved in the initialization (env vars for discovery, etc.)
- If using examples, where should this fit? Client, Server, other?
- Will go between client/server library and host server
- Relates to “minimal server” example
- Discussion: Standard should be more detailed
- Example - non-blocking call, text is little loose for before/after in context of threads, need better precision in text.
- Refinements to text as implementations/examples proceed to help clarify vagueness when encountered.
- JSC working w/ Partec and encountering implementation items based on Standard and prompting a few items that fit under this category
- V6.0 cleanup
- Cancel 25Q2 Day-2 (Thu) b/c full agenda covered
- Other/Open discussion
- TODOs
- Post meeting notes
- Review v6.0 milestone issues (triage & comment as needed)
-
Look into pmix.org DNS issue(resolved) - Migrate pmix-examples => pmix Github Organization
- Create “examples” label in pmix-standard issues tracker
- Possibly issue for comments on “wire protocol” / interoperability example
- Thomas: SPI CY24 report & circulate for any edits/changes, then submit
- No meeting, full agenda covered on Day-1.