November 21, 2006 L-Store Planning Meeting (VU): Difference between revisions

From ReddNet
Jump to navigation Jump to search
Line 10: Line 10:
=== L-Store Releases and Features ===
=== L-Store Releases and Features ===
* <b>L-Store Release 0.8</b> --- December 4 REDDnet@I2 meeting
* <b>L-Store Release 0.8</b> --- December 4 REDDnet@I2 meeting
** API documentation will be provided
** API documentation will be provided
** L-Store Commands Implemented:
** L-Store Commands Implemented:
*** <i>mkdir
*** <i>mkdir
Line 19: Line 17:
*** read
*** read
*** help?</I>
*** help?</I>
** Clients will be made available for installation to attendees at REDDnet@I2
** Clients will be made available for installation to attendees at REDDnet@I2
*** for user testing and application development
*** for user testing and application development
*** files written to depots should be considered scratch
*** files written to depots should be considered scratch
**
**



Revision as of 15:27, 29 November 2006

Attending

  • Hagewood (Nevoa)
  • Brown, Dawson, de Ledesma, Sheldon, Tackett (VU)

Meeting Goal

Develop an initial strategy for development and releases of L-Store software. There was also some discussion of planned hardware deployment for the near term.

L-Store Releases and Features

  • L-Store Release 0.8 --- December 4 REDDnet@I2 meeting
    • API documentation will be provided
    • L-Store Commands Implemented:
      • mkdir
      • ls
      • write
      • read
      • help?
    • Clients will be made available for installation to attendees at REDDnet@I2
      • for user testing and application development
      • files written to depots should be considered scratch
  • L-Store Release 0.9 --- End of January 2007
  • L-Store Release 1.0 --- May/June 2007

Near-Term Hardware Deployment

  • Validation, Verification, and Performance Testing Depot
    • We will deploy 20 of the Capricorn Depots in a single system that can be used for validation, verification, and performance testing.
    • This system will be for developers use only, and it can be taken down at any time. Software can be updated at any time.
    • Nightly, the L-Store development release code will be built, installed, and tested with Clyde. This may take a few months to get going smoothly.
  • User System
    • The remainder of the systems (20) will be deployed as a user facility.