Skip to content

2019 04 Meeting notes

jhansonhpe edited this page Apr 26, 2019 · 3 revisions

Date: April 26, 2019 Attendees:

  • Jeff Hanson, HPE
  • Ryan Grant, SNL
  • Natalie Bates, EEHPCWG
  • Barry Rountree, LLNL
  • Torsten Wilde, HPE
  • Sid Jana, Intel
  • Matt Kappel, Cray
  • Steve Martin, Cray
  • Kevin Pedretti, SNL
  • Todd Rosedahl, IBM
  • Steve Leak, NERSC

Should we release Power API SPEC as a version before Power Stack integration. Barry wanted to clean up some components. Should they wait to be done? Sid what does a version number mean? How stable does 1.0 (if we used that) has to be. Ryan said new major would be only when backward compat is lost OR a whole lot of new code (aka PowerStack). Ryan suggests using a release note to explain. Barry wants to make some API changes (some adds and some drops). There are only a few things to be done quickly. Sid and Torsten suggest postponing until after ISC/PowerStack meeting for 1.0 release. Steve Martin should we publish 0.9 first? Ryan likes this. As does Sid. Then have a deadline of SC for 1.0. Sid said that Altair will be coming to Power Stack meeting and will get the names for Jeff. ScheMD will be there virtually. A 1.0 version by SC (November) would give everyone time to get proposals and votes. Ryan to put out a 0.9 version and make available. To give a semi final version for ISC/PowerStack. Sid what about reference implementations that adhere? Should we say they exist? Yes says Ryan. However Barry asks what does it mean to be compliant and useful. Ryan wants to have work on this. Reference implementation is mostly compliant with the spec. It may have missing features and may not be the most efficient. Ryan will fix the versioning of reference implementation because it will say 2.1. He will put in some content to address the perceived issue. Ryan will package the release as a PDF as 0.9RC and email out withing two weeks. Power Stack (aka Intel and LLNL) has SLURM interaction. This is really preliminary. Ryan and Sid to discuss 1:1 first before bring to either broader community.