LWG Minutes 2015-01-14: Difference between revisions

From OpenSFS Wiki
Jump to navigation Jump to search
(Created page with "Category:LWG == Agenda == * Agenda for Lustre Developer Project Meeting* Begin annual Lustre Survey* Open discussion == Attendance == colin richard cory james chris an...")
 
Line 7: Line 7:
== Attendance ==
== Attendance ==


colin
* Colin Faber (Seagate)
richard
* Richard Henwood (Intel)
cory
* Cory Spitz (Cray)
james
* James Simmons (ORNL)
chris
* Christopher Morrone (LLNL)
andreas
* Andreas Dilger (Intel)
sebastien
* Sebastien Buisson (Bull)
ann (cray)
* Ann Koehler (Cray)


== Agenda for January Developer Meeting ==
== Agenda for January Developer Meeting ==

Revision as of 19:15, 2 February 2015


Agenda

  • Agenda for Lustre Developer Project Meeting* Begin annual Lustre Survey* Open discussion

Attendance

  • Colin Faber (Seagate)
  • Richard Henwood (Intel)
  • Cory Spitz (Cray)
  • James Simmons (ORNL)
  • Christopher Morrone (LLNL)
  • Andreas Dilger (Intel)
  • Sebastien Buisson (Bull)
  • Ann Koehler (Cray)

Agenda for January Developer Meeting

Andreas sent suggestions to LWG mailing email list

Frank Zago will probably talk about some topic

Some time to talk about liblustreapi

Advanced debugging techniques (James not quite volunteering)

Ann Koehler from Cray reworking debug log functionality, page allocation

Cory - lnet RAS - Chris Horn

Issue tracking/source management - Colin

Cory - Test framework

Hackathon - is that practical?

Paul - try to prioritize most relevant stuff up front?

Linux kernel landing stuff (James) - discuss early in day thursday? Peter wants sysfs support before upstream merge Other things, check Greg KH email, talk to Oleg. Some simple things like wrapper functions... First goal get it out of staging, sencond step update client with latest Lustre changes. Bigger architectural issues needed to fix before getting out of staging. Event queues, task wait (have lustre's own wrappers right now). Upstream didn't like dump stack mechanism, we don't necessarily agree with.

Q&A session - but focussed on an area - describe how some part fits in the overall picture (ldlm, etc.)

Overview of basic problems solved

Documentation Discussion

High level overview lustre doc, describe architecture.

LID mentioned. Out of date, the autogenerated parts are the least useful. The prose is best, but there needs to be more of it.

Annual Lustre Survey

Cory - should ask some questions about development model.

Question about what people intend to upgrade _to_?

Are you using Lustre provided by a vendor, or one built yourself?

Are you using DNE?

Are you using HSM?

How long have you been using feature X?

  • I'm not
  • 6 months
  • 1 year

etc.

Are you using LFSCK?

Andreas - lustre.org available for advertising the survey? Chris - working is under way, lustre.org will hopefully be in good enough shape to be one place that we advertise the survey

Open Discussion

Cory - update on lustre.org

Chris relayed the current status of the transfer. Seagate is putting together the things we need to make the transfer happen.

arch.lustre.org - bunch of design stuff that was never public

LID docs could be useful