[ofw] WinOF 1.0 (Windows OpenFabrics) is available

[Erez Cohen]

Stan,

We do not have a mechanism in place to build the WinOF stack. The builds
are done manually from time to time. Fab used to do this, this days
Mellanox are the one doing it. 
We definitely need to have a daily build mechanism for which we need a
dedicated server in OpenFabrics and a large storage to place those
builds. That was one of the goals I had for the last Sonoma meeting but
we never got to that.

For now, I think customers who need the latest WSD fix can simply build
the code from SVN and replace the WSD DLL or they can take the latest
WSD fix (SVN 666) from
http://lists.openfabrics.org/pipermail/ofw/2007-May/001537.html (need to
change file extension to .7z). Please note that this fix is not the
final one, we are still chasing a potential issue with WSD.

I think once we will have the WSD issue fixed and the SRP enhancements
we will build new bin files so this may be a good point for making
another MSI.


Best regards, 

Erez Cohen
Field Application 
Development Manager

Mellanox Technologies Ltd. 
Tel : + 972 - 4 - 9097200 ext 378
Cell : + 972 - 54 - 5468801
Fax : + 972 - 4 - 9593245
www.mellanox.com

-----Original Message-----
From: Smith, Stan [mailto:stan.smith at intel.com] 
Sent: Tuesday, July 17, 2007 1:49 AM
To: Erez Cohen; Tzachi Dar
Subject: RE: [ofw] WinOF 1.0 (Windows OpenFabrics) is available

Erez Cohen wrote:
> Stan,
> 
> In general I have no objection to build a drop (ideally we should have

> a daily MSI build for testing/regression) but it is important that 
> people understand this is not even RC as we do not have feature freeze

> and we did not test this code.
> 
> How complex is it for you to generate the MSI?
Not too bad - validating the install package is what takes time...

Both the InstallShield and WIX installers depend on the binary release
structure which has been used in the past openib-windows binary releases
(566, 614). BTW, where would I find the script which compiles an
openib-windows source tree and populates the binary release tree?

The underlying question is how are the x64 binary tree 32-bit versions
of complib (cl32.dll) ibal32.dll and others constructed?

If I have a binary release tree to work with, then it takes about 15
minutes to build the InstallShield setup.exe install package files (x86,
x64 &ia64); I've yet to figure out how to run InstallShield from a
command line - it's heavily GUI oriented. Approximately 1 day for a
quick install verify pass, nothing in-depth.

For the WIX installer, assuming a binary release tree is available,
about the same amount of time to build & validate.
The WinOF WIX installer build produces a .msi file, the msi build is
driven from a Makefile. If you can explain how to build the 32-bit
variants mentioned previously, I can modify the WIX Makefiles to
generate a WIX install package directly from the src tree thus enabling
a daily build install package generation capability.

The WIX installer is slightly different from the WinOF 1.0 installer in
that it's ALWAYS a custom install, otherwise the same. Short story is to
go down the 'typical' or 'minimal' WIX install path with a specific
install screen of what was to be installed would require modifications
to the open-source files which define the WIX mondo GUI setup thus
creating a specific for openib-windows GUI; this is how the WIX folks do
things - if you do see what you want, build it. The downside would be
the  incorporation of modified WIX mondo GUI & files into the
openib-windows src tree. 
If we use just the 'custom' install, then we use open-source WIX GUI
files without modification.

I'll send you a WinOF 1.0 WIX based installer for you to take a look at.

I understand/appreciate the issues around producing a release which has
not been feature frozen and/or fully tested. The concern was that of the
WSD null-pointer dereference patch which did not make it into WinOF 1.0.

Thanks,

Stan.




> 
> Best regards,
> 
> Erez Cohen
> Field Application
> Development Manager
> 
> Mellanox Technologies Ltd.
> Tel : + 972 - 4 - 9097200 ext 378
> Cell : + 972 - 54 - 5468801
> Fax : + 972 - 4 - 9593245
> www.mellanox.com
> 
> -----Original Message-----
> From: Smith, Stan [mailto:stan.smith at intel.com]
> Sent: Thursday, July 12, 2007 11:30 PM
> To: Erez Cohen; Tzachi Dar
> Subject: FW: [ofw] WinOF 1.0 (Windows OpenFabrics) is available
> 
> 
> What are your thoughts on doing a WinOF 1.1 head of svn tree build & 
> release?
> 
> BTW, thoughts on release numbering:
>   X.Y where
> 	X is incremented when new functionality is incorporated into the

> release (connected mode IPoIB)
> 	Y is incremented for bug fixes.
> 
> Thanks,
> 
> Stan.
> 
> 
> Livingston, James wrote:
>> Stan,
>> 
>> Does this release contain the WSD fix in Tzachi Dar's "RE: [ofw] NULL

>> pointer dereference in WSD provider" message to the list of 
>> 5/21/2007?
>> 
>> Cheers,
>> jwl
>> 
>>> -----Original Message-----
>>> From: ofw-bounces at lists.openfabrics.org 
>>> [mailto:ofw-bounces at lists.openfabrics.org] On Behalf Of Smith, Stan
>>> Sent: Thursday, July 12, 2007 12:28 PM
>>> To: Erez Cohen
>>> Cc: ofw at lists.openfabrics.org
>>> Subject: [ofw] WinOF 1.0 (Windows OpenFabrics) is available
>>> 
>>> 
>>> WinOF 1.0 'gold release' is available @ 
>>> http://www.openfabrics.org/~ardavis/WinOF_1.0/
>>> 
>>> A hearty 'Thank you' to all who assisted in WinOF 1.0 creation.
>>> Special recognition goes to Erez Cohen for being patient.
>>> 
>>> Stan.
>>> _______________________________________________
>>> ofw mailing list
>>> ofw at lists.openfabrics.org
>>> http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw