+++ This bug was initially created as a clone of Bug #245817 +++
+++ This bug was initially created as a clone of Bug #245816 +++
+++ This bug was initially created as a clone of Bug #225581 +++
1. Feature Name: upgrade openib, openmpi to OFED 1.2
a. Architectures (mark all that apply)
* 64-bit Itanium2
* 64-bit AMD64/Intel EM64T
64-bit IBM POWER
31-bit IBM S/390
64-bit IBM zSeries
b. Dependencies: OFED 1.2 release from community in April/May 2007
c. External links: www.openfabrics.org
d. Priority (H,M,L): H
e. Target Releases: RHEL 5.1
f. Target Release Date:
g. Drivers or hardware dependency: InfiniBand
h. Target Kernel:
3. Business Justification:
a. Why is this feature needed?
Distro support for IB native will mean it is well integrated with the
rest of the distro. HPC IB cluster sales have been growing.
b. What hardware does this enable? InfiniBand
c. Forecast, volume or high end platform? Carlsbad is a high-end platform
d. Any configuration info?
e. When needed? RHEL5.1 or sooner
f. Are there other dependencies (drivers).
a. Is code accepted upstream? If so, what version or patch?
Yes the kernel code is in 2.6.11 onwards, but they need to pick
a more recent version based on OFED 1.2 release.
There are changes in 2.6.20 which could be worth taking
(just use the OFED 1.2 release)
5. Hardware to Red Hat? Red Hat can't integrate/test features without hardware.
Gallup (BZ#223419) and Carlsbad (BZ# 223545) products are scheduled
to come to Westford.
6. Partner management contact, email, phone, chat
John Hesterberg, email@example.com, 651-683-5879, N/A
7. Partner technical contact, email, phone, chat
George Beshers, firstname.lastname@example.org, 978-392-2447, N/A
Where/location: Westford, MA
-- Additional comment from email@example.com on 2007-01-31 10:29 EST --
In Westford, Gurhan Ozen <firstname.lastname@example.org> is the QE engineer assigned to IB
testing. Please make sure that any hardware intended for IB testing is properly
labeled and Gurhan notified so that it can be used in our QE IB fabric. If
there are special development needs on these platforms, I'll coordinate with
Gurhan to make sure it is covered.
-- Additional comment from email@example.com on 2007-02-19 11:24 EST --
Can you update us on this? Will this make 5.1?
-- Additional comment from firstname.lastname@example.org on 2007-02-19 12:38 EST --
Not yet. The upstream 1.2 OFED release is only in alpha testing right now.
Whether or not it makes 5.1 is dependent on when they actually have a 1.2 release.
-- Additional comment from email@example.com on 2007-05-02 14:35 EST --
Groupe Bull is also asking for this.
-- Additional comment from firstname.lastname@example.org on 2007-05-02 15:03 EST --
Hey Doug -- Could you give us a quick update on the current status of upstream
1.2 OFED? Thanks!
-- Additional comment from email@example.com on 2007-05-26 05:28 EST --
Approved component for 5.1 PM ACK
-- Additional comment from firstname.lastname@example.org on 2007-05-31 12:49 EST --
QA ACK for 5.1.0. Looks like we have an assigned QA guy already (comment 1).
-- Additional comment from email@example.com on 2007-06-01 16:52 EST --
Red Hat Product Management and Engineering have evaluated this request and
currently plan to include it in the next Red Hat Enterprise Linux minor release.
Please note that its inclusion depends upon the successful completion of code
integration and testing.
-- Additional comment from firstname.lastname@example.org on 2007-06-26 16:33 EST --
I have to clone the original bug because I need separate bugs for each component
involved or else our system won't let me A) check in changes to CVS and B) file
-- Additional comment from email@example.com on 2007-06-26 16:35 EST --
Another clone for CVS checkins and errata.
Another clone for CVS/Errata.
*** Bug 247818 has been marked as a duplicate of this bug. ***
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.