[Twg] TWG meeting minutes for 2011-05-12

[John Carrier]

Attached are the meeting minutes from today's TWG call.  We discussed my summary of the release collateral discussion we've had  the past few meetings:

   Proposed Release Collateral:
      - high level design (HLD) document
      - test plan and results
      - code following standard Lustre guidelines 
      - complete release checklist
      - patches sized for easy inspection
      - review by two independent inspectors

See today's minutes for more information. Discussion of these points were mostly covered in minutes from our 4/21 and 4/28 meetings.   Please post questions/comments to discuss at lists.opensfs.org.

Next meeting is next Thursday (5/19) @ 9:30a PDT/12:30p EDT, (715) 726-4994, ID/password 72090.


-------------- next part --------------
OpenSFS Technical Working Group
Meeting minutes : 05/12/2011

Concall: start : 9:30a PT, adjourn : 9:55a PT

Next meeting: Thursday, 05/17/2011 @ 9:30a PDT/12:30p EDT
   Dial-in numbers are 715-726-4994 
   Meeting ID and password are 72090

Attending

   Name              Organization   email
   ----------------- -------------- ----------------------------
   Cory Spitz        Cray           spitzcor at cray.com
   John Carrier      Cray           carrier at cray.com
   Alex Kulyavtsev   FNAL           aik at fnal.gov
   Joshua Walgenbach IU             jjw at indiana.edu
   Chris Morrone     LLNL           morrone2 at llnl.gov
   Dave Dillow       ORNL           dillowda at ornl.gov

Agenda
   review collateral proposals

Discussion

   John described an email conversation he had with Jim Ryan and Evan
   Felix about an industry group trying to identify a neutral repository
   for Lustre.  They are interested in our efforts to define release
   collateral.  John invited them to join our dicussion on
   discuss at lists.opensfs.org.
   
   The following lists summarize the discussions of release collateral
   from this and our three preceding meetings.  Please send suggestions
   for improving the proposals to discuss at lists.opensfs.org.
   
   
   Proposed Release Collateral
   ---------------------------

      - high level design (HLD) document
      - test plan and results
      - code following standard Lustre guidelines
      - complete release checklist
      - patches sized for easy inspection
      - review by two independent inspectors

    Notes:
         
      We have asked the community for 
       1) help defining the release
       2) volunteers to review patches

      We agreed not to ask for a detailed design document (DLD). This
      is largely of use only to the organization writing the code. After
      implementation is complete, the code itself is the design
      document.  The HLD, however, must provide sufficient detail to
      understand how the code is implemented.

      Tests defined in the test plan must be publically available.

      John is to send this summary of release collateral to lustre-devel
      to get feedback from a broader audience.

   Proposed SOW Requirements
   -------------------------

      - design documents
         - architecture level design (ALD)
         - high level design (HLD)
      - implementation checkpoints
         - publically available development branch
         - intermediate milestones to verify functionality
         - publically available test plans
      - code to land upstream in a public, neutral repository (TBD)
         - include all release collateral defined above

    Notes:

      The ALD summarizes the requirements and provides an overview of
      the proposed solution.  It is the first opportunity for the Lustre
      community, outside the RFP review team, to see the feature
      proposal.

      The HLD is done after presentation and discussion of the ALD. It
      will explain the ideas behind the design, an overview of the
      proposed implementation, and any diagrams needed to clarify the
      design. There should be no procedure prototypes or data structure
      definitions.

      Since OpenSFS is requiring this document before coding starts, we
      expect the HLD to be updated after the implementation is
      complete and before inspections begin for release.

      The SOW needs to define where the testing for the intermediate
      steps will be done and by whom.  If we expect OpenSFS members to
      run the tests or use their clusters, we need commitments for these
      resources.  

adjourn 9:55PT