Dear all,
I'm currently working on the oscar openmpi module and I need users feedback
regarding this module.
Right now (up to oscar 6.1.*) openmpi package is named "openmpi" and is located
into /opt (mith modules for PATHs setup and so).
Having a package that has the same name as a distro package can be missleading
and/or triggers issues.
To change things, there are 3 choices and I'd like return from you about what
would best fit your needs.
1/ having a openmpi-oscar package in /opt (providing openmpi)
=> PRO: you can still install system openmpi (EPEL or rhel)
=> CONS: need to modify the spec file (I'm in touch with the spec file
creator)
need to use modules-oscar (system environment-modules still
not supported)
packages depending on openmpi won't use this rpm. (there a
several ones on epel)
2/ having openmpi in /opt
=> PRO: no need to change the spec file.
=> CONS: right now overridden by epel version which replace this package
with a version located in /usr
with a version 1.6.3, will override epel version and break
dependancies of the epel packages requiring openmpi
=> configuring EPEL repos could trigger issues.
3/ having a standard openmpi-1.6.3 located in /usr equivalent to epel one but
with correct copilation option like tm (torque module) interface or blcr
(berkley checkpoint-restart).
=> PRO: no module file requirement
could be used by other packages requiring openmpi
no need to use epel version
will not be overridden by epel as version is higher
=> CONS: not sure that v1.6.3 is compatible with epel packages requiring
openmpi (though rpmbuild --rebuild the src.rpm should be sufficient
if epel decides to upgrade its version faster than oscar,
oscar package could be overridden by epel version breaking the tm interface and
blcr (epel openmpi is not build with tm interface and blcr).
At the moment, I've modified oscar build tree to have openmpi-oscar build into
/opt (my though is that packages that are not real oscar code but compiled with
specific oscar needs should be postpended with -oscar so it is easy to see that
this openmpi package is specific to oscar).
In the meantime, I'm using a standard openmpi-1.6.3 located in /usr and built
with epel options + tm + blcr.
So:
what are you using at the moment?
- custom openmpi build (rpm or nfs share)?
- epel rpm?
- oscar rpm?
What would help you?
- openmpi-oscar located in /opt
- openmpi located in /opt
- openmpi located in /usr
Many thanks for your feedback about this point.
Best regards,
Olivier.
--
Olivier LAHAYE
CEA DRT/LIST/DCSI/DIR
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Oscar-devel mailing list
Oscar-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oscar-devel
