[openfabrics-ewg] Re: How to generate IBED releases using 1.0branch

[Tziporet Koren]

The way I see it is this:

Commonality between IBED and OpenFabrics Release 1.0:

   1. Both share the same user level code. (libraries, management
      utilities, opensm, uDAPL). The code is taken from 1.0 branch in
      both releases.
   2. Using bugzilla for bugs reporting.


Differences between IBED and OpenFabrics Release 1.0:

   1. OpenFabrics 1.0 release contains only the user level code while
      IBED release includes both user level and kernel modules.
   2. IBED release includes kernel modules that are not part of the
      Linux kernel (like iSER and RDS)
   3. IBED includes two MPI packages: OSU MPI and Open MPI.
   4. IBED release is packed in a convenient way for the end user.
   5. IBED supports existing distribution with older kernels (e.g.
      Redhat EL4 up2)


Thus really IBED contains the OpenFabrics release.

Not clear to me if Bryan is planning to prepare a separate OpenFabrics 
release, or he to use the common part of IBED. I would recommend to do 
it in the way and then the collaboration between both will be clear.

I hope this info is enough for the announcement mail. Note it is very 
important to send this message today since we start to see questions 
form different developers and I don't want that the answer will come 
from engineering.

Tziporet

Shawn Hansen (shahanse) wrote:
> Tzipporet and Bryan,
> Can you briefly write up your technical view on the most controversial 
> issue: How IBED is based on/differs from OpenFabrics Release 1.0.
> i.e. Are they separate releases, which release candidate will IBED be 
> based on, how will new changes be incorporated, branching/convergence 
> strategy, what happens with release 1.0 when that comes out, etc. 
> Also, which things are open items.
> Everyone else: Do you agree on Tziporet's message below?
> Thanks,
> --Shawn
>
> ------------------------------------------------------------------------
> *From:* Tziporet Koren [mailto:tziporet at mellanox.co.il]
> *Sent:* Thursday, March 30, 2006 7:16 AM
> *To:* Shawn Hansen (shahanse); Sujal Das; bos at pathscale.com
> *Cc:* Michael S. Tsirkin; Openfabrics-ewg at openib.org
> *Subject:* RE: [openfabrics-ewg] Re: How to generate IBED releases 
> using 1.0branch
>
> Hi,
>
> This is the technical details you can use to send such a mail.
>
> We are working on IBED release in collaboration of OpenFabrics release.
>
> The motivation behind the release:
>
> - Backport IB support from 2.6.17 to older kernels and existing 
> distributions (Redhat, SuSE)
>
> - Making it easy for people to test and use components that are not 
> yet in mainline kernel
>
> - One package supported by all IB OEMs and vendors
>
> - Please add more …
>
> The components of the IBDE release are (in brackets is the source 
> location):
>
> Kernel modules:
>
> - HCA drivers: mthca, ipath (git tree for 2.6.17)
>
> - core (all modules) (git tree for 2.6.17)
>
> - IPoIB (git tree for 2.6.17)
>
> - SRP (git tree for 2.6.17)
>
> - iSER (svn trunk)
>
> - SDP (svn trunk)
>
> - RDS: from SilverStorm contrib directory (till they move it to the trunk)
>
> User level modules:
>
> - All libraries and utilities from the 1.0 branch
>
> - Opensm from the 1.0 branch
>
> MPI:
>
> - OSU MPI – tarball based on release 0.97 provided by Mellanox
>
> - Open MPI – tarball based on XXX (Jeff to fill) provided by Cisco
>
> In the way this release is done both IBED release and OpenFabrics 
> share the same user space code, and testing done on one of them 
> contribute to both.
>
> Also working on kernel modules that are aimed for Linux kernel will 
> raise the quality level of Infiniband kernel code and will be aligned 
> with Linux releases.
>
> More information that you may want to add is that we will use the same 
> bugzilla to report bugs
>
> Tziporet
>