LWG Minutes 2018-04-19

From OpenSFS Wiki
Revision as of 05:41, 8 April 2019 by Jgmitter (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Attendance

Cray: Cory Spitz, Ben Evans
ORNL: James Simmons, Dustin Leverman
HPE: Olaf Weber, Christopher Voltz, Stephen Champion
Sandia: Ruth Klundt
IU: Ken Rawlings
Intel: Joe Gmitter, Peter Jones, Andreas Dilger, Amir Shehata

Actions

New Actions Captured:

  • None

Existing Open Actions:

  • None

Actions Recently Closed:

  • None

Minutes

2.12.0 Release Update
Peter

  • We have been talking with DDN about what they want to try to get in as they have a few things they are working on. The thing most likely to land is the lazy size on MDT feature. Patches already are in flight and discussions with community are ongoing. They are also going to present it at developer day and the main conference. Will probably add to roadmap instead of FLR advancements as that is ground work for erasure coding and doesn’t need to be a marquee feature advertisement. We think that lazy size on MDT would be a better fit for the marquee list. Any opinions?
    • Cory: This is great news and encouraging. We are in favor of putting it on for 2.12.
  • We are also suggesting to modify feature freeze to be a 2 stage process. The "Feature Cut-off" date is for new functionality to be submitted. Patches must be in flight and maturing by this cut-off to be eligible. The following month is to work out review comments and bugs for those patches to get them landed. Any views on this, feedback?
    • The general consensus is agreement.


Upstream Lustre Client
James

  • We found a few bugs with the SMP changes, will be working through that.
  • Been porting and testing hashing stuff, will be collecting numbers.
  • We noticed router pinning not working in the upstream client.
  • We needs volunteers testing this stuff, resources and time.
    • Andreas: Getting to a point where the upstream client will get out of staging is a good goal for when we can start pushing patches directly there. Right now it isn’t even caught up to 2.10, mostly 2.9.


lustre.org
Ken Rawlings

  • We have followed up on the stack overflow discussion from last meeting with the board and are working on next steps to move forward.
  • We are working on the creation of a wiki page for guidelines, which we will then circulate a link on the mailing lists indwell add to the lustre.org front page.
    • We will be talking to users at LUG to get more input for the guidelines.
  • We wouldn’t be able to do a sub-site on stack overflow. We would just be a part of main site using tags. We will want to establish tags in the guidelines so we have reliable links etc…. This will coexist with the mailing list and will outline it in the guidelines.
  • Cory: what is the ETA to get rolling on the main site?
    • Relatively soon, the main thing there is getting the guidelines together. Nothing official we have to do to use stack overflow, so we can begin any time. Having the guidelines are the key.
  • As for moderating the site, we have done some investigation. Will are going to have to put something together to monitor for unanswered questions.


Other Business

  • Peter: Is there any feedback on the roadmap or suggested changes?
    • No feedback.


Next meeting will be on 2018-05-03 at 11:00am Pacific