WARNING: This is the _old_ Lustre wiki, and it is in the process of being retired. The information found here is all likely to be out of date. Please search the new wiki for more up to date information.

Windows Native Client

From Obsolete Lustre Wiki
Revision as of 20:34, 4 May 2008 by Bsneitzel (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

Windows Client Meeting, Monday, 2008-04-21. Eric Barton Peter Bojanic Nikita Danilov Alex Tomas Matt Wu Bryon Neitzel

A Google Document was created for questions from the development staff for Braam's meeting with OSR this week. http://docs.google.com/a/lustre.org/Doc?id=d8jgmdp_20fpxwdgb. Alex and Nikita to document questions by Wednesday.

A branch has been created for use by OSR. b_winnt_port branch of lustre-core module (sharing HEAD lnet so far)

Comments from the Meeting:

- eeb: need a clean interface that porting will use. - eeb: need metadata interface that doesn't expose internal stuff to another platform

- Matt to continue documentation, compile issues, and porting all client components that are common to other platforms (LOV, LDLM, OSC, MDC, LVM, PTLRPC, etc) Eric would like to be involved before too much design work is done. - Matt has drafted a doc titled gcc_vc.pdf that describes the differences between the gcc and vc compilers, and some proposed solutions. This was sent to Dan Root, et al, on Jan 20. Eric to provide feedback.

- Alex wants to learn more about Windows. understand simple use cases.

- would OSR implement the file handle stuff? (do we need to export an MD FID lookup?)

- Get de-brief from Braam on meeting, have him give direction to Alex on md api

           - Alex to send a list of questions to braam

- Put a question in doc about what OSR can be doing?

- Need an OSR work plan as a result of Braam meeting, so the Lustre team knows all the dependencies and dates on items we're responsible for.

- Do we need an LNET branch? Give them a snapshot of all of the sources. Otherwise we don't know what they're implementing to. Nikita says current client IO can't be used for implementation, as it's not far enough along yet.

- Provide branch names: b_winnt _port, HEAD version of LNET. OSR will need their own private branch when they start to commit code. Need to sort out branch situation when OSR is ready to check in code. Their code cannot live in a pubic branch.