LWG Minutes 2018-02-08

Attendance
Cray: Cory Spitz,  Ben Evans

ORNL: James Simmons

HPE: Olaf Weber, Christopher Voltz

IU: Ken Rawlings

Intel: Joe Gmitter, Peter Jones

Actions
New Actions Captured:


 * Cory to have an engineer assess and respond to LU-10443
 * Peter to follow up on the MPICH issue

Existing Open Actions:


 * None

Actions Recently Closed:


 * None

Minutes
2.10.3 Release Update

Peter


 * The release has gone out since the last call. The issue we were concerned about previously were environmental and not a code issue.
 * We now begin to start thinking about 2.10.4.

2.11.0 Release Update

Peter


 * We have been working on the 2.11 burndown list. We have covered this previously, but just wanted to mention again that moving a JIRA ticket to 2.12.0 still permits landing ahead of 2.11.0 code freeze if it become ready.  However, we will not hold the release for it to become ready.
 * Joe: We have a few minor issues for FLR that are in the process of landing and we continue to shape up the two performance improvements for Data on MDT (read-on-open, lock conversion).
 * Any community feedback on 2.11.0?
 * James: We are testing on our Cray system.  PFL seems to have caused the MPICH library to break, resulting in poor performance because it choses the worst possible layout with one stripe.  Cory, anything to add on this?
 * Cory: This sounds like a bug in the code base if the API has changed.
 * James: This is fixed in LU-9657.
 * Peter: This is the first time we have heard this brought up and we will look into it.  Peter to action action to follow up.
 * James: LU-8854 and LU-9431 would be important for us and we hope to see them land.
 * Peter: We are doing landings a few times a week and if these become ready they can be pulled into landing consideration.
 * Peter: LU-10443 could use review from Cray to assess the bug being reported.
 * Action: Cory to have an engineer respond on the ticket.
 * Cory: In general, please add shadow to any reviews needing expediting where Cray can assist
 * Cory: How is 2.11 trending to release next month?
 * Peter: With what we know about it right now, it looks to be on track.  Historically there is an upsurge in testing as the window is about to close and things come up that need investigation, so it is always tough to predict at this point.
 * Cory: When do we expect the gatekeeper to curtail landings to master?
 * Peter: That is what we refer to as code freeze, which is when we branch b2_11 and only land blocking issues to both master and b2_11 simultaneously.  The general trend would indicate that this is a few weeks out.

Upstream Lustre Client

James


 * The next window is about to open.
 * Neil Brown is looking for help on testing on the email list. James is going to give him a drop of his test suite that he uses locally to get him going.

lustre.org

Ken


 * We are investigating the options for hosting the webinar.
 * Old pages on the old wiki will be merged into a single page in the new space and should be ready for review by the next call.

Other Business


 * Peter: The OpenSFS survey is out and number of respondents so far has exceeded the final total last year.
 * Cory: With regard to LUG, are we doing a developer day again?  How is that shaping up?
 * Peter: The board asked if he could coordinate things with the LWG for another developer day.  We have starting giving some it some thought about suggestions to bring up for the next call.  If you have some ideas, feel free to bring up on the next call as well.

Next meeting will be on 2018-02-22 at 11:00am Pacific