Skip to content

Meeting 2019 08 23

Jump to bottom
Josh Hursey edited this page Aug 23, 2019 · 1 revision

Agenda

Notes

        Joshua Hursey (IBM)
	Michael Karo (Altair)
	Ralph Castain (Intel)
	Danielle Sikich (Intel)
	Ken Raffenetti (Argonne)
	Kathryn Mohror (LLNL)
	Artem Polyakov (Mellanox)
	Thomas Naughton (ORNL)
  • WG mailing lists are active
  • Working group update: Implementation agnostic document
    • Reviewed PRs https://github.com/dsolt/pmix-standard/pulls
    • Discussed whether PMIx is a “messenger” or a “doer”
      • Do not want to prevent PMIx from providing a service if the RM doesn’t want to, but it’s primary role is as a messenger between the client, tool, and System Management Stack (SMS).
    • Discussed broadening the language from just an HPC focus to a broader distributed computing focus.
  • Working group update: Slicing/Grouping of functionality
    • Keep working on use case development
  • Discussion: Governance PR
    • https://github.com/pmix/governance/pull/4
    • Conflict in document: One paragraph says “major” and another says “minor”. Should be “major”
    • (Josh) Will walk this through the governance process and put on the ASC Q4 2019 agenda
  • Discussion: Major/Minor release timeline forcing function
    • Be careful of tying our hands to a timeline
      • Every year at the face-to-face meeting we can declare a major release.
      • This meeting will decide if a major release is necessary. But maybe there were only typos that may not warrant a major release. So we need some flexibility here.
      • Maybe we have a general guidance (not a formal forcing rule) for the ASC membership to release on a regular timeline.
    • Where should we collect these informal rules for rules?
      • Put on the governance Wiki
        • “ASC operating procedures”
      • Put in the Governance document as a new chapter with clear language that this is general guidance for the ASC membership.
        • Reference from the “Release Manger” section of the document
        • Separate section may allow for faster process on changes to philosophy section separate from rules.
    • Three options for placement: Add this to the issue for discussion.
      • Wiki
      • Existing governance document as new section
      • New companion governance document
    • What should the language be?
      • Does someone what to create an Issue with first draft of language?
        • Kathryn
    • (Josh) put on agenda for the quarterly meeting
  • ASC Quarterly Meeting planning update
    • https://github.com/pmix/pmix-standard/wiki/ASC-Q4-2019-Meeting
    • Secretary - 2 positions to distribute load
    • Post a call for nominations well before the quarterly meeting
      • Have folks replay to the co-chairs to compile a list
      • Folks can nominate up to the point of voting
      • 2 weeks before the meeting send out the list and allow for last minute additions
    • Josh has a draft of the announcement will circulate this afternoon to the mailing list
      • Finalize next meeting.
  • What do we want to do with https://github.com/pmix/pmix-standard/issues/190
    • Leave as inactive until it draws attention
    • The implementation agnostic working group is talking about some of this so might have something to contribute.
  • PMIx Standard v4 Standard PRs for review - timeout in 2 weeks if no objection.
  • Update on planning for v4
    • https://github.com/pmix/pmix-standard/issues/189
      • Put in the planned items for v4 then we switch to new governance in v5
      • Primary new interfaces support PMIx groups and fabric interaction
    • RFCs in progress
      • Chapter on protocol for tools and debuggers (no API/Attribute additions)
      • Storage APIs - possible that this may slip to v5
    • Timeline:
      • Roughly try to release by the end of the year - possibly at SC’19
      • Targeting move to v5 in Q1 2020
    • What if someone wants to introduce something new for v5, but if the document is re-organized then v5 might take a while. May need to split this activity up so as not to overly delay the new addition scheduled for v5.
      • Otherwise we can add them to v4.1 (or other v4.x point release) with the provisional marking.
  • Suggestion to not meet next week due to US holiday weekend with exception that attendance will be low.
    • (Josh) to send notice to the list. If there is an urgent item for discussion the we may hold the meeting, otherwise we will meet again in two weeks.

Action Items

  • (Josh) Send notice to pmix-forum mailing list canceling next week's teleconf
  • (Josh) Send out draft of the ASC quarterly meeting announcement to the pmix-forum mailing list for review.
  • (Josh) Add Governance PR to the ASC quarterly meeting
  • (Josh) Add discussion of "ASC operating procedures" to the ASC quarterly meeting (once posted)
  • (Kathryn) Draft a governance Issue on the establishment of "ASC operating procedures" with initial text on the release forcing function discussion.

Home

Working Groups

Events

Helpful How To...

ASC Quarterly Meetings

ASC Monthly Meetings

Clone this wiki locally