LWG Minutes 2015-03-11: Difference between revisions

From OpenSFS Wiki
Jump to navigation Jump to search
(Created page with "== Agenda == * LUG LWG Meeting * Developer Day Agenda * Lustre Roadmap Update == Attendance == * Chris Morrone (LLNL) * Peter Jones (Intel) * Cory Spitz (Cray) * Sebastien ...")
 
No edit summary
 
Line 1: Line 1:
[[Category:LWG]]
== Agenda ==
== Agenda ==



Latest revision as of 11:45, 16 March 2015


Agenda

  • LUG LWG Meeting
  • Developer Day Agenda
  • Lustre Roadmap Update

Attendance

  • Chris Morrone (LLNL)
  • Peter Jones (Intel)
  • Cory Spitz (Cray)
  • Sebastien Buisson (Bull)
  • Chris Hanna (IU)
  • Colin Faber (Seagate)
  • Justin Miller(Cray)
  • Paul Sathis (Intel)

Minutes

LUG LWG Meeting

There will be a face-to-face meeting of the LWG on Wednesday afternoon after the end of LUG. What should be the start time? Early start time we would need to order lunch, which would require early registration. If we pick a later time, people can get lunch on their own before the meeting.

It was decided to have a later time of 1:30 and no lunch provided.

Developer Day Agenda

There were very little volunteers to lead discussion sessions during Developer Day on April 16th, 2015. It was recommended that everyone go back to their organization and encourage developers to volunteer if they have something to talk about.

Lustre Roadmap Update

  • Layout Enhancement
  • DNE phase II
  • Quota for Project (get update)
  • UID/GID mapping on track (MGS integration still outstanding)
  • End-to-End Dta Integrity with T10 (change to ???)
  • Large Bulk IO (change to ???)
  • Data MDT (change to ???)
  • RHEL 7 server support ready in 2.8

Sebastien - Kerberos Revival? Just beginning, not able to estimate

 completion time yet.  (Make Sebastien the Point of Contact)

Other

What will Chris say about maintenance releases during his talk?

He will focus on talking about what we do with the master branch. Master is the point of collaboration for the Lustre open source community. Focussing on making those releases as high quality as possible, discuss changes to make that happen. Direct people to the vendors for support and long term maintenance releases.