[openfabrics-ewg] Meeting Minutes - 3/20 Call

[Matters, Todd]

Oooops, I meant RDS.

 

 

 

______________________

Todd A. Matters

SilverStorm Technologies

(610)233-4809

 

________________________________

From: openfabrics-ewg-bounces at openib.org
[mailto:openfabrics-ewg-bounces at openib.org] On Behalf Of Matters, Todd
Sent: Thursday, March 23, 2006 12:56 PM
To: Pramod Srivatsa (psrivats); Openfabrics-ewg at openib.org
Subject: RE: [openfabrics-ewg] Meeting Minutes - 3/20 Call

 

Regarding SDP, moving the code to the trunk was more problematic than
originally anticipated.  We propose that we continue to take the code
from the contrib. for RC2.  

 

Todd

 

 

______________________

Todd A. Matters

SilverStorm Technologies

(610)233-4809

 

________________________________

From: openfabrics-ewg-bounces at openib.org
[mailto:openfabrics-ewg-bounces at openib.org] On Behalf Of Pramod Srivatsa
(psrivats)
Sent: Monday, March 20, 2006 4:48 PM
To: Openfabrics-ewg at openib.org
Subject: [openfabrics-ewg] Meeting Minutes - 3/20 Call

 

Please reply with additions / corrections. 

 

1. Role for Chair:

    - Timely reports to the OF-BOD

    - Coordinate the interests of the group

    - Run the EWG meetings and setting the agenda

    - Same chair for 1st two releases

    - Rotate for every release after the 2nd one, based on company
alphabetical order

    - Vendors have the option to opt-out

    - Cisco (Shawn Hansen) will be chair: Unanimous

 

2. Role of the Release Coordinator:

    - Meet needs of members of the EWG

    - Which components go into each release

    - What is the release criteria for each component

    - What the schedule is for the releases

    - Rotate for every release after the 2nd one, based in company
alphabetical order

   - Silicon vendors only will be release coordinators

   - Mellanox (Tziporet) will be RC: 

 

3. OFRv1 vis-a-vis IBEDv1

    - Betsy: Requirement of IBEDv1 is not clear versus OFRv1

    - Matt: Go with two stacks versus three stacks (OF-development
branch, OF-release branch, IBED release); Having multiple production
stacks does not make sense for customers. 

    - Bryan: Can create OFR-RC2 with patches from Mellanox; Need to
review all the patches with Tziporet

    - EWG is a superset of OFR in the following way:

        - SDP: Michael Tsirkin will finish writing SDP (Not in mainline
kernel, may not forward binary compatible)

            - Option of having a beta of SDP on top of OFRC

        - RDS: No code in the OpenIB trunk

 

4. Opens on maintainers:

    - See Sujal's mail from March 16 (1:51PM) for the complete list

    - OpenMPI: Mellanox to sign open-mpi paper by March 27th.
B-maintainer decision will be deferred.

    - SDP: Mellanox will decide who the b-maintainer should be

    - MVAPICH: Need b-maintainer; Shawn will confirm

 

5. Next steps:

    - Discuss / decide point #3 above on e-mail

    - Setup call next week to close on today's discussion

 

-Pramod

 

=======================

Pramod Srivatsa

Product Manager, SVBU

M: 408.203.6543

E: pramod.srivatsa at cisco.com <mailto:pramod.srivatsa at cisco.com> 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/ewg/attachments/20060323/aa57f15c/attachment.html>