Skip to content

Meeting 2019 07 26

Jump to bottom
Josh Hursey edited this page Jul 26, 2019 · 1 revision

Agenda

Notes

        Kathryn Mohror (LLNL)
	David Solt (IBM)
	Ralph Castain (Intel)
	Michael Karo (Altair)
	Ken Raffenetti (ANL)
	Stephen Herbein (LLNL)
	Howard Pritchard (LANL)
	Joshua Hursey (IBM)
  • PMIx standardization process
    • 6 organizations have voted in the straw poll, all positive
      • Are there any orgs that we need to contact to see if there are outstanding issues?
      • Straw Poll
        • Thumbs up: mike0042, jjhursey, abouteiller, SteVwonder, spophale, and kathrynmohror
        • Hooray: rhc54
    • One additional item added to the process: what happens if a co-chair resigns? We vote in a new one that serves until the end of the original term.
    • PR #179 covers stability classes
      • We think this is covered by PR #193
      • All good, can close
    • PR #181 covers standardization process
      • Are the issue and PR templates included in PR #193?
      • The templates are in the repo now and are referenced in the governance text
      • All good, can close
    • Add vote on “document extraction”?
      • The idea is to move the governance text from the README to a separate document that can be placed on the website. Easier to find, can be versioned independently from the Standard
      • The README can be an abbreviated version of the rules and have a pointer to the larger document
      • Kathryn: takes the duty of translating README markdown to latex (pandoc)
      • Ralph: takes the duty of editing the README
      • Yes, vote on this
    • Vote on co-chair?
      • Yes, it’s reasonable to vote on 8/2 whether Josh keeps his role as co-chair without a vote in October
    • Any other logistical votes for next week?
    • For next week: Set a date in October for quarterly meeting
      • PathForward Meeting October 21-25
      • SC19 Organizing Meeting Oct 1-2
  • SC plans: Two BoFs
    • Ralph: will write a note to Wesley to explain the difference between the two submissions
  • Issue #190: Mission statement
    • The original idea was to try to define it to get us to make progress on other issues, but in the meantime we have established governance rules and are making progress
    • Having the functionality groupings will ease the challenges of having a broad scope because libraries/implementations will only have to focus on what is important to them
    • Ralph: Will try to get Geoffroy to on a meeting or poke him to see his current feelings on this
  • (Dave) Working group update: Implementation agnostic document
    • Did not meet this week, will meet next week
    • About done with first pass on first chapter
    • Will take time to go through and generate proposed text, some is done, but there’s still quite a bit of work to do
    • A few more weeks before there is a draft of the first chapter
    • Dave’s fork is available as a PR on the standard repo if people want to look at it
  • (Stephen) Working group update: Slicing/Grouping of functionality
    • Wrapped up remaining RFCs (going through them, documenting)
    • There are a few PRs on RFC repo to go through, power control, co-launch tool, multi-tiered storage support. Some may be in the standard already, some are on their way
      • Power management has not made it in yet, may not since at the time it was unclear if PMIx should be managing power. Might be possible with high-level directives (e.g. at job launch time), but not thought through yet. Can possibly follow up, but don’t take anything in that RFC as “gospel”
      • Tool co-launch, leftover RFC that was used for note taking. Ended up going in a different RFC that already is included in the API.
      • Storage management: needs to be completed, centered around the idea to move data around storage hierarchy (e.g. pre-stage, post-stage, and data management that other infrastructures provide (HDFS)). Ralph said he needs to update this one
    • Then plan to group based on functionality
      • Will be pulling in community experts/users for each piece of functionality to make sure that decisions are informed and documented
    • Stephen will be reaching out to Ralph with a few questions that the WG had
      • Ralph will help by making sure that the RFC’s and other suggestions we have been looking through are up to date, e.g. debugging. There’s a few that probably need updating (scheduling, network?)

Action Items

  • Next Week (8/2) We Vote!
    • (Yes/No) Josh keeps 'Co-Chair' position without a separate vote in October 2019.
    • (Yes/No) Accept PR #193
  • Next week decide on the date for the October 2019 quarterly meeting.

Home

Working Groups

Events

Helpful How To...

ASC Quarterly Meetings

ASC Monthly Meetings

Clone this wiki locally