[ofw] WinOF 1.0 RC2, available for test.

[Erez Cohen]

Hi Stan,

Some comments: 

>> 	- In custom installation, core should be a pre-request for all 
>> components. In the way it is implemented, it can be removed.

>Custom is indeed 'custom' - you get what you ask for. If you prefere, I
will make the Core manditory.
>Do you feel IPoIB is custom or manditory?

I agree that "custom is custom", the thing is that you can not do
ANYTHING with out the core, maybe only open documents... I think it will
be a source for usage errors. Think of the not so experienced user, he
may like to have a minimal installation to run MPI, so he will
mistakenly chose DAPL and that's it.
I strongly feel that we must enforce the dependencies in the installer.
As core is a prerequisite for all the other components I think it must
be installed. About IPoIB, WSD use some services from IPoIB therefore
IPoIB must be installed if one check WSD, even if not explicitly chosen.
Aging, I'm not sure if DAPL needs IPoIB.

I don't know how complex is to implement this dependencies. If it is not
simple I would just make core and IPoIB mandatory.

>> 	- Uninstall does not work from start -> OpenFabrics -> uninstall

>Odd, works for me on Win2k3? Was this an XP story?

Yes, it is XP. Sorry I forgot to mention.


>> 	- I think SM as a service should be install, not started in
typical 
>> installation.

>Here we simply disagree. I strongly believe SM should NOT be a default
install because typically you only install one SM. 
>In a cluster environment you end up with an SM on every node, hence
forcing a 'custom' install on all node except one; flip-side is one
custom install.
>OFED does not auto magically install a running SM on all nodes.

I'm not sure I explained my self correctly. I think the SM should be
installed as a service but should NOT be set to start automatically.
This way, you can set one or more machines in the cluster to start the
service automatically after the cluster was installed, you can change
the machine running SM by simple configuration (as all machines have the
service in MANUAL mode) without the need to install a service. 
As far as I know OFED does install SM on the nodes and add it to
/etc/init.d but will not set it to run on boot unless configured.




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: Monday, May 21, 2007 7:45 PM
To: Erez Cohen; ofw at lists.openfabrics.org
Subject: RE: [ofw] WinOF 1.0 RC2, available for test.

Erez,
  Thanks for taking the time to verify the install process.

Embedded comments follow.

Erez Cohen wrote:
> Stan,
> 
> Thank you for the great work. I have test this drop and below are my 
> comments. I'll review the documentation later this week.
> 
> Test description and setup:
> 	- Install, uninstall and reinstall on W2K3, 64 bit Intel Xeon
> 	- Install, uninstall and reinstall on W2K3, 32 bit Intel Xeon
> 	- Install, uninstall and reinstall on XP 32 bit
> 
> Test result:
> 	- Component list is missing in typical and compact installation

One would think that an expensive package like InstallShield would
provide this functionality? Turns out to be a royal pain-in-the-backside
to acquire this...Nonetheless, I'm looking into it Turns out a
current-features list needs to be populated, the downside is the Current
settings screen has no hook to accept this list, so one has to do the
entire Current settings screen by hand and feed it the current features
list according to InstallShield. PITBS!


> 	- No warning/Error if installing x86 on x64 machine

OK - will correct this oversight.

> 	- In custom installation, core should be a pre-request for all 
> components. In the way it is implemented, it can be removed.

Custom is indeed 'custom' - you get what you ask for. If you prefere, I
will make the Core manditory.
Do you feel IPoIB is custom or manditory?

> 	- uninstall - WinOF dir is not deleted

Understood, once-apon-a-time InstallShield did this correctly. For
unknown reasons IS-12 has decided not to remove WinOF; discovered this
behavior last Friday after I cut RC2. Currently repaired.

> 	- On XP and typical installation, WSD is been installed and
failed. 
> WSD is not supported and should not be installed in XP

>From Fab's discussion on XP, I came to the conclusion XP was only
marginally supported for openib-windows. Will investigate not installing
WSD on XP.

> 	- On XP, fatal installer error (1603) when uninstalling (SM was 
> running, don't know if it makes a difference)

See previous discussion on XP support, will look into it.

> 	- Uninstall does not work from start -> OpenFabrics -> uninstall

Odd, works for me on Win2k3? Was this an XP story?

> 	- WinOF is not in path environment variable. I think it can make
life 
> much easier...

The idea was less system pollution (aka modifications). Given the DAPL
DLL discussions, this may appear.

> 	- I think SM as a service should be install, not started in
typical 
> installation.

Here we simply disagree. I strongly believe SM should NOT be a default
install because typically you only install one SM. In a cluster
environment you end up with an SM on every node, hence forcing a
'custom' install on all node except one; flip-side is one custom
install.
OFED does not auto magically install a running SM on all nodes.

Anybody else want to chime in on this discussion?

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: ofw-bounces at lists.openfabrics.org 
> [mailto:ofw-bounces at lists.openfabrics.org] On Behalf Of Smith, Stan
> Sent: Saturday, May 19, 2007 12:04 AM
> To: ofw at lists.openfabrics.org
> Subject: [ofw] WinOF 1.0 RC2, available for test.
> 
> 
> WinOF 1.0 RC2 (Windows OpenFabrics Release Candidate #2)
> 
>  http://www.openfabrics.org/~woody/WinOF_1.0/WinOF_1-0_RC2.zip
> 
> Please direct comments and/or suggestions towards 
> 'ofw at lists.openfabrics.org'.
> 
> Stan.
> 
> Changes since WinOF RC1
> -----------------------
> 
> Added a 'Program Files->WinOF->Uninstall' shortcut to faciliate WinOF 
> removal.
> 
> Updated Release Notes with discussions on
>     1) How to perform a Silent/Unattended install or uninstall.
>     2) IPoIB interface IPv4 address assignment from a command line.
> 
> WinOF will not install if Windows programs reg.exe and sc.exe are not 
> present.
> 
> dat.dll and dapl.dll are correctly installed in %WINDIR%.
> _______________________________________________
> ofw mailing list
> ofw at lists.openfabrics.org
> http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw