Informal REDDnet software stack meeting, 3Dec06: Difference between revisions
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
==Elements of the LN software stack== | ==Elements of the LN software stack== | ||
*IBP | |||
**NFU | |||
*exNode library | |||
*LoRS toolkit | |||
*L-Store | |||
*L-bone | |||
*LoDN | |||
*LSL | |||
*libxio | *I/0 libraries | ||
*stdio | **libxio | ||
*netCDF/L | **stdio | ||
*HDF5 | **netCDF/L | ||
*MPI/IO | **HDF5 | ||
**MPI/IO | |||
*Nevoa tools and services=== | |||
*File system work | |||
==Issues== | ==Issues== | ||
Revision as of 15:14, 28 November 2006
Goals
- Settle on the contents of the first "REDDnet release" of the LN stack, subject to revision as a result of the discussions with users in the next days meeting.
- Layout a roadmap for further development, subject to the same reservation as above
- Discuss and formulate a plan for coordinating the work of the software community
Elements of the LN software stack
- IBP
- NFU
- exNode library
- LoRS toolkit
- L-Store
- L-bone
- LoDN
- LSL
- I/0 libraries
- libxio
- stdio
- netCDF/L
- HDF5
- MPI/IO
- Nevoa tools and services===
- File system work
Issues
- Interoperability -- My assumption is that IBP and exNode library are relatively settled and provide the basis for interoperability. The question is where else do we need or want to try to achieve it?
- State of the software
- Documentation
- Licensing
- Security
Order of items to be discussed
One natural way to do this is to work our way up the stack, but if have ideas about the critical items, we need to budget our time. Maybe we need to review a common checklist for all the software items (i.e. create a matrix) and review the matrix as a whole and then start discussing the problems, plans and issues.