This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

This issue is a Blocker for us.It will be of great advantage and help , if  issue is considered for the current release.(In reply to comment #2)
> This issue has been proposed when we are only considering blocker
> issues in the current Red Hat Enterprise Linux release.
> 
> ** If you would still like this issue considered for the current
> release, ask your support representative to file as a blocker on
> your behalf. Otherwise ask that it be considered for the next
> Red Hat Enterprise Linux release. **    

This issue is a Blocker for us.It will be of great advantage and help , if  issue is considered for the current release.

mpi-selector is a bad hack from the OFED project.  It has been dropped entirely in favor of environment-modules.  The environment-modules package creates a shell command used to load and unload the necessary environment variables for the mpi packages.  To see what modules are available, use this command:

module avail

Loading a module is done via 

module load <module-name>

Unload is similar

module unload <module-name>

The various mpi implementations in rhel6 all require that environment-modules be installed prior to the mpi being installed, so if you have any mpis installed then you also have environment-modules installed.  The environment modules package is far superior to mpi-selector in that it can be used any time from the command line and does not require a person to log out and back in before the changes take effect or to unload a selection.

I'm opening a documentation request on this bug however.

Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.

New Contents:
The mpi-selector package is no longer used to select which mpi implementation to use under Red Hat Enterprise Linux 6.  Instead, the environment-modules package is used.  The module man page details usage of the environment modules package, but the simple directions are:

module avail (to see what modules are available)
module load <module-name> (to load a module)
module unload <module-name> (to unload a module)

In order to emulate the previous behaviour, it is sufficient for a user to place a call to module load in their personal .bashrc (or similar shell init script if they use a different command shell) to cause the proper module to be loaded at login each time.

(In reply to comment #4)
> mpi-selector is a bad hack from the OFED project.  It has been dropped entirely
> in favor of environment-modules.  The environment-modules package creates a
> shell command used to load and unload the necessary environment variables for
> the mpi packages.  To see what modules are available, use this command:
> 
> module avail
> 
> Loading a module is done via 
> 
> module load <module-name>
> 
> Unload is similar
> 
> module unload <module-name>
> 
> The various mpi implementations in rhel6 all require that environment-modules
> be installed prior to the mpi being installed, so if you have any mpis
> installed then you also have environment-modules installed.  The environment
> modules package is far superior to mpi-selector in that it can be used any time
> from the command line and does not require a person to log out and back in
> before the changes take effect or to unload a selection.
> 
> I'm opening a documentation request on this bug however.    

Thanks for guiding us.We will be following the steps mentioned.

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,7 +1,11 @@
-The mpi-selector package is no longer used to select which mpi implementation to use under Red Hat Enterprise Linux 6.  Instead, the environment-modules package is used.  The module man page details usage of the environment modules package, but the simple directions are:
+mpi-selector
+The mpi-selector package has been deprecated in Red Hat Enterprise Linux 6. environment-modules is now used to select which Message Passing Interface (MPI) implementation is to be used.
+The man page for the module command contains detailed documentation for the environment-modules package.
+To return a list of what modules are available, use:
 
-module avail (to see what modules are available)
-module load <module-name> (to load a module)
-module unload <module-name> (to unload a module)
+module avail
+To load or unload a module use the following commands:
 
-In order to emulate the previous behaviour, it is sufficient for a user to place a call to module load in their personal .bashrc (or similar shell init script if they use a different command shell) to cause the proper module to be loaded at login each time.+module load <module-name>
+module unload <module-name>
+To emulate the behaviour of mpi-selector, the module load commands must be place in the shell init script (e.g. /.bashrc) to load the modules every login