<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>RE: [openfabrics-ewg] Getting EWG off to a rapid and positive start</title>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="Street"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PostalCode"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="State"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="City"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="address"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="country-region"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Copperplate Gothic Light";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
p
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Seems like Voltaire is OK for the below
proposal.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Proposed Voltaire Maintainers and B- Maintainers
list was already communicated to the mailing list.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'> <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>YaronS<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<p class=MsoNormal><font size=1 color=blue face="Copperplate Gothic Light"><span
style='font-size:9.0pt;font-family:"Copperplate Gothic Light";color:blue'>___________________________________________________________</span></font><font
color=navy><span style='color:navy'><o:p></o:p></span></font></p>
<p class=MsoNormal><st1:PersonName w:st="on"><font size=1 color=blue
face="Copperplate Gothic Light"><span style='font-size:9.0pt;font-family:"Copperplate Gothic Light";
color:blue'>Yaron Segev</span></font></st1:PersonName><font size=1 color=blue
face="Copperplate Gothic Light"><span style='font-size:9.0pt;font-family:"Copperplate Gothic Light";
color:blue'> | +972-9-9717650 (o) | +972-54-4996631 (m)<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=1 color=blue face="Copperplate Gothic Light"><span
style='font-size:9.0pt;font-family:"Copperplate Gothic Light";color:blue'>Director,
Software Development</span></font><font size=2 color=navy face=Arial><span
style='font-size:10.0pt;font-family:Arial;color:navy'><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=1 color=gray face="Copperplate Gothic Light"><span
style='font-size:9.0pt;font-family:"Copperplate Gothic Light";color:gray'>Voltaire
– <u>The Grid Backbone <o:p></o:p></u></span></font></p>
<p class=MsoNormal><font size=3 color=navy face="Times New Roman"><span
style='font-size:12.0pt;color:navy'><a href="http://www.voltaire.com/"
title="http://www.voltaire.com/"><font size=1 face="Copperplate Gothic Light"><span
style='font-size:9.0pt;font-family:"Copperplate Gothic Light"'>www.voltaire.com</span></font></a></span></font><font
size=1 color=blue face="Copperplate Gothic Light"><span style='font-size:9.0pt;
font-family:"Copperplate Gothic Light";color:blue'>______________________________________________</span></font><font
color=navy><span style='color:navy'><o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div style='border:none;border-right:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
openfabrics-ewg-bounces@openib.org [mailto:openfabrics-ewg-bounces@openib.org] <b><span
style='font-weight:bold'>On Behalf Of </span></b><st1:place w:st="on">Florin</st1:place>,
Reini<br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, March 16, 2006
9:52 PM<br>
<b><span style='font-weight:bold'>To:</span></b> Openfabrics-ewg@openib.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: [openfabrics-ewg]
Getting EWG off to a rapid and positive sta rt</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<div>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>Speaking for SilverStorm, I agree fully
with Sujal's process suggestions and process proposal below with one added
comment.</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>Since the EWG will be a
distribution not a release, I think it is important that we make sure we
cover the two primary goals that were the genesis of the EWG concept
1) Provide a single distribution to users that has multivendor
guaranteed component interoperability and 2) Provide a distribution to
users that has supportable, enterprise class components</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>I suggest that the distribution, in
addition to the "support" based classifications Sujal suggests below
also incorporate "interoperability" based logic in the component
classifications.</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>One suggested expanded definition approach
to Sujal's below:</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>1) Basic Component = All
vendors that will be offering the EWG distribution to the market agree to
interoperability, enterprise quality, and support
for basic components (IE. Core, IPoIB, etc.) </span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>2) Add-on Component = Full
multivendor interoperability and support is not guaranteed to the user for an
add-on component but the component is guaranteed to
be enterprise quality and support for the component is provided by one or
more vendors (IE. iSER, SRP, SDP, etc)</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>3) Technology preview = No
multivendor interoperability guarantee and no vendor support at
all ..... these components are at your own risk components in
the distribution (MVAPICH?) </span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<p><font size=2 color=black face=Arial><span style='font-size:10.0pt;
font-family:Arial;color:black'>Reini Florin</span></font> <o:p></o:p></p>
<p><font size=2 color=black face=Arial><span style='font-size:10.0pt;
font-family:Arial;color:black'>Vice President of Marketing</span></font> <br>
<font size=2 color=black face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:black'>SilverStorm Technologies<br>
</span></font><br>
<st1:Street w:st="on"><st1:address w:st="on"><font size=2 color=black
face=Arial><span style='font-size:10.0pt;font-family:Arial;color:black'>780
Fifth Ave, Suite 140</span></font></st1:address></st1:Street><br>
<st1:place w:st="on"><st1:City w:st="on"><font size=2 color=black face=Arial><span
style='font-size:10.0pt;font-family:Arial;color:black'>King of Prussia</span></font></st1:City><font
size=2 color=black face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:black'>, <st1:State w:st="on">PA</st1:State> <st1:PostalCode
w:st="on">19406</st1:PostalCode></span></font></st1:place><br>
<font size=2 color=black face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:black'>Tel: 610 233-4854</span></font> <br>
<font size=2 color=black face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:black'>Cel: 203-906-3570<br>
Fax: 610 233-4777<br>
E-mail: rflorin@silverstorm.com<br>
<u>www.silverstorm.com</u> </span></font><o:p></o:p></p>
<blockquote style='margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma'>-----Original Message-----<br>
<b><span style='font-weight:bold'>From:</span></b>
openfabrics-ewg-bounces@openib.org [mailto:openfabrics-ewg-bounces@openib.org]<b><span
style='font-weight:bold'>On Behalf Of </span></b>Sujal Das<br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, March 16, 2006
1:51 PM<br>
<b><span style='font-weight:bold'>To:</span></b> Openfabrics-ewg@openib.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: [openfabrics-ewg]
Getting EWG off to a rapid and positive sta rt</span></font><o:p></o:p></p>
<p><st1:City w:st="on"><st1:place w:st="on"><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>Bryan</span></font></st1:place></st1:City>
<font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>,</span></font><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>Thanks
for leading the discussion. </span></font> <font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>I have tried to address some of the
questions in the proposal below.</span></font><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>All,
</span></font><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>Here
is a strawman proposal for the EWG</span></font> <font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>Distribution</span></font> <font
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>process.
I would like to call a meeting of the EWG members on Monday between at 11:30 AM
PST (this time works for the folks in <st1:country-region w:st="on"><st1:place
w:st="on">Israel</st1:place></st1:country-region>). PLEASE CONFIRM:</span></font><o:p></o:p></p>
<p><b><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial;
font-weight:bold'>KEY PEOPLE in the process:</span></font></b><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>1.</span></font>
<font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>The
EWG needs a CHAIR, per Open Fabrics Bylaws who needs to be approved by the
BOD. The Chair is a liaison between the EWG and the BOD. Will
communicate the existence and purpose of the EWG to OpenFabrics-General.</span></font><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>2.</span></font>
<font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>RELEASE
COORDINATOR who drives the upcoming release. </span></font> <font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>Drives decisions</span></font>
<font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>collaboratively
to enable stable, supportable release</span></font> <font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>of EWG Distribution</span></font> <font
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>on
schedule. Defines:</span></font> <font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>Which software components are
included?</span></font> <font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Which hardware components are intended to work?</span></font><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>3.
Open Fabrics Release Committee Lead - the OFR LEAD (what <st1:City w:st="on"><st1:place
w:st="on">Bryan</st1:place></st1:City> from PathScale is today)</span></font><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>4.
TEST LEADS from each Company. Decides:</span></font> <font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>Which distros are
targeted?</span></font> <font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>What is the test matrix?</span></font> <font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>What documentation
will be written up for customers?</span></font><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>5.
MAINTAINERS and backups (B-MAINTAINER) for each component in EWG: Calls
dedicated technical meetings to ensure delivery, code/feature completeness.</span></font><o:p></o:p></p>
<p><font size=3 face="Times New Roman"><span style='font-size:12.0pt'> <o:p></o:p></span></font></p>
<p><b><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial;
font-weight:bold'>Suggested schedules:</span></font></b><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>EWG
Distribution 1.0 - sync with OFR Release 1.0 date of May 8.</span></font><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>EWG
Distribution 1.1 - Sept (4 months delta between releases)</span></font><o:p></o:p></p>
<p><font size=3 face="Times New Roman"><span style='font-size:12.0pt'> <o:p></o:p></span></font></p>
<p><b><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial;
font-weight:bold'>Proposal for electing the KEY PEOPLE:</span></font></b><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>1.
CHAIR is elected on a rotating basis - changing every 4 months with EWG release
completions. Represented by system companies - Cisco, Voltaire,
SilverStorm. In alphabetical order. So, starts with Cisco as the
CHAIR. Storage vendors like LSI if they meet the criteria to a EWG member can
be eligible to be CHAIR as well. First proposed rotation is after EWG
Distribution 1.1 (May 8 being too close). If that is a problem, it could
be Matt</span></font> <font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>representing a neutral party.</span></font><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>2.
RELEASE COORDINATOR is elected from either Mellanox or PathScale on a rotating
basis - changing every 4 months with EWG release completions. </span></font>
<font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>Change
will be decided when the time comes based on voting or</span></font> <font
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>recent past</span></font>
<font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>effectiveness
etc.</span></font> <font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>This person must be</span></font> <font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>commercially</span></font> <font
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>neutral to
the system companies who compete in the end user space. At any time
Mellanox or PathScale will be the RELEASE COORDINATOR or OFR LEAD, not
both. Currently Pathscale is OFR LEAD. So Mellanox will be RELEASE
COORDINATOR. First possible rotation (based on voting, effectiveness
etc.) is after EWG Distribution 1.1 (May 8 being too close)</span></font><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>3.
OFR LEAD is elected from either Mellanox or PathScale on a rotating basis -
changing every 4 months with EWG release completions.</span></font> <font
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>Change will
be decided when the time comes based on voting or</span></font> <font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>recent past</span></font>
<font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>effectiveness
etc.</span></font> <font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>This person must be</span></font> <font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>commercially</span></font> <font
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>neutral to
the system companies who compete in the end user space. </span></font> <font
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>At any time
Mellanox or PathScale will be the RELEASE COORDINATOR or OFR LEAD, not
both. Currently Pathscale is OFR LEAD. So Mellanox will be RELEASE
COORDINATOR. First possible rotation (based on voting, effectiveness
etc.) is after EWG Distribution 1.1 (May 8 being too close)</span></font><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>4.
TEST LEADS - elected by individual companies. Scott from Cisco, Bob from
SST, Moni from V, Amit from Mellanox, Betsy from Pathscale. </span></font>
<o:p></o:p></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>5.
MAINTAINERS (B-MAINTAINERS): Selected based on who is currently
maintaining. MAINTAINER selects B-MAINTAINER based on technical
expertise, past contributions. Here are MAINTAINERS and suggestions for
B-MAINTAINERS:</span></font><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>o</span></font>
<font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>MTHCA
- Roland (Michael Tsirkin)</span></font><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>o</span></font>
<font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>IPATH
- Roland (</span></font><st1:City w:st="on"><st1:place w:st="on"><font size=2
face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>Bryan</span></font></st1:place></st1:City><font
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>)</span></font><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>o
Core - Roland (</span></font><st1:City w:st="on"><st1:place w:st="on"><font
size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>Bryan</span></font></st1:place></st1:City><font
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>) </span></font><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>o
IPoIB - Roland (Eli Cohen)</span></font><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>o
SDP - Michael Tsirkin (?)</span></font><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>o
SRP - Roland (Vu)</span></font><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>o
iSER - Moni (?)</span></font><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>o
RDS - Todd (?)</span></font><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>o
MVAPICH - ?? (ideally would like companies with vested interest to productize
MVAPICH)</span></font><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>o
Open MPI -</span></font> <font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>?? (ideally would like companies with vested interest to
productize</span></font> <font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Open MPI)</span></font><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>o
OSM -</span></font> <font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Eitan (Hal) </span></font> <font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>(ideally would like companies with
vested interest to productize</span></font> <font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>OSM)</span></font><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>o
Diagnostic Tools -</span></font> <font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>Eitan</span></font> <font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>(Hal)</span></font><o:p></o:p></p>
<p><font size=3 face="Times New Roman"><span style='font-size:12.0pt'> <o:p></o:p></span></font></p>
<p><b><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial;
font-weight:bold'>RELEASE COMPONENT CATEGORIES:</span></font></b><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>They
fall under 3 categories:</span></font><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>o
BASE COMPONENTS: IPoIB, SDP, SRP, iSER, RDS, Open MPI,</span></font> <font
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>iPath,</span></font>
<font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>MTHCA</span></font><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>o
Depending on vendors desire/ability to qualify and support BASE COMPONENTS -
some may be released and supported by vendors as TECH PREVIEW only. E.g.,
iSER could be TECH PREVIEW for Cisco. </span></font> <font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>SRP could be TECH
PREVIEW for Voltaire. RDS could be TECH PREVIEW for all etc. The
goal is to get TECH PREVIEW components graduate to supported BASE COMPONENTS in
the EWG</span></font> <font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Distribution</span></font> <font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>1.1 scheduled for September.</span></font><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>o
ADD-ON -</span></font> <font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>These will be added in</span></font> <font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>Vendor specific</span></font>
<font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>distributions
as</span></font> <font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>add-ons</span></font> <font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>on top of (and not replacing) BASE
COMPONENTS. OSM, Proprietary SM, Proprietary MPI, other value added management
and tools etc fall in this category</span></font><o:p></o:p></p>
<p><font size=3 face="Times New Roman"><span style='font-size:12.0pt'> <o:p></o:p></span></font></p>
<p><b><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial;
font-weight:bold'>EWG DISTRIBUTION MANAGEMENT + SYNCH WITH OFR RC BRANCH</span></font></b><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>Copy
a specific trunk/branch version to</span></font> <font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>EWG area you can call this a tag.
The main idea of a tag is that you do not commit changes to the tagged area.</span></font><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>In
addition</span></font> <font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>there is a directory called patches where</span></font> <font
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>EWG places
the fixes wanted that were not in the trunk/branch. The</span></font> <font
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>OFR LEAD
folds those into the OFR-RC</span></font> <font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>branch immediately.</span></font> <font
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'> Coordinated
with RELEASE COORDINATOR as necessary.</span></font><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>Continue
copy of trunk/branch to the tag few times till</span></font> <font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>EWG gets to the
point</span></font> <font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>it wants to freeze code. >From this point (regression
test phase)</span></font> <font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>EWG only adds patches (some</span></font> <font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>can be EWG fixes
and some from the trunk/branch).</span></font><o:p></o:p></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>We
need a discussion on the contents of</span></font> <font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>the</span></font> <font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>OFR rc1</span></font>
<font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>branch</span></font>
<font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>-
whether it meets the need of end users defined by the EWG and if that needs to
be updated (as rc2) based on feedback from EWG.</span></font><o:p></o:p></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>Thanks</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>Sujal</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>-----Original Message-----<br>
From: Bryan O'Sullivan [<a href="mailto:bos@pathscale.com">mailto:bos@pathscale.com</a>]<br>
Sent: Thursday, March 16, 2006 9:36 AM<br>
To: Openfabrics-ewg@openib.org<br>
Subject: [openfabrics-ewg] Getting EWG off to a rapid and positive start</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>Hello -</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>I'll be PathScale's engineering and testing representative on
the EWG.</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>I would suggest that we start by clarifying the goals of the EWG</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>process, so that everyone is in sync.</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>My principal interest is in ensuring that there is no duplicated
or</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>wasted effort between the 1.0 process and the EWG process, and
that each</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>can proceed at its own appropriate pace with maximal cooperation
between</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>the two.</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>What I believe is a good way to achieve this is as follows.</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>Somebody needs to articulate the goals of the EWG process, and
the</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>timeline in which it will take place. Here are some
suggestions I have.</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'> * The existence of EWG should be
made public on openib-general,</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'> and it must be made
clear that there is cooperation, not</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'> duplication, between
the 1.0 and EWG processes.</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'> * Which software components are
included?</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'> * Which hardware components are
intended to work?</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'> * Which distros are targeted?</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'> * What is the test matrix?</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'> * What documentation will be
written up for customers?</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'> * How long is the support window?</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'> * What's the policy with respect
to switching to the official 1.0</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'> and subsequent
releases?</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>To get the testing and defect fixing balls rolling as quickly as</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>possible, EWG contributors ought to use the 1.0 release
candidate tree</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>at <a href="https://openib.org/svn/gen2/branches/1.0/"
target="_blank">https://openib.org/svn/gen2/branches/1.0/</a> as its initial
basis for</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>source code to build and test. You can download source
tarballs and</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>some RPM packages from <a href="http://openib.red-bean.com/"
target="_blank">http://openib.red-bean.com/</a></span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>It's fine with me if EWG branches from 1.0 so that it can
proceed at its</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>own pace. However, if this happens, there must be frequent
merges</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>between the two trees, because clearly everything that happens
in one</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>branch ought to be beneficial to the other.</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>The mechanism that EWG uses to track defects should be OpenIB
Bugzilla.</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>I believe it's already configured in an appropriate
manner. If not, I</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>will be happy to make any needed changes, or ask our colleagues
at</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>Sandia to help out.</span></font><o:p></o:p></p>
<p><font size=3 face="Times New Roman"><span style='font-size:12.0pt'>
</span></font><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'><b</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>_______________________________________________</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>openfabrics-ewg mailing list</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>openfabrics-ewg@openib.org</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'><a href="http://openib.org/mailman/listinfo/openfabrics-ewg"
target="_blank">http://openib.org/mailman/listinfo/openfabrics-ewg</a></span></font><o:p></o:p></p>
</blockquote>
</div>
</div>
</body>
</html>