How do I enable OHPC with Bright?

"OpenHPC is a collaborative, community effort that initiated from a desire to aggregate a number of common ingredients required to deploy and manage High Performance Computing (HPC) Linux clusters including provisioning tools, resource management, I/O clients, development tools, and a variety of scientific libraries."

Bright offers a package to easily integrate, and leverage OHPC libraries and packages for use within a Bright cluster.

Prerequisites

The ohpc-reposetup requires either RHEL/CentOS 7 or SLES 12 as these are the two operating systems that OHPC supports. Currently, only the x86_64 architecture is supported by this procedure.

This package assumes that /opt/ohpc will be a symlink to /cm/shared/apps/ohpc/ and admins will be prompted if a previous OHPC install is detected. Each software image will also contain a symlink as mentioned above so that OHPC can resolve its path correctly.

[root@bright80]# ohpc-reposetup.shChecking prerequisite files.Setting up OHPC for use with Bright...Backing up default modules./etc/sysconfig/modules/lmod/cm-lmod-init.sh/etc/sysconfig/modules/lmod/00-modulepath.sh=== The following images were detected ===Please choose which images you wish toenable the OHPC repo in.==========================================a) All software images.0) default-image /cm/images/default-imaged) Disable OHPC on the head node and software images.q) Quit.(selection): aYou selected: aEnable OHPC in all software images.Creating symlink to /opt/ohpc in: /cm/images/default-imageBacking up lmod modules./cm/images/default-image/etc/sysconfig/modules/lmod/00-modulepath.sh/cm/images/default-image/etc/sysconfig/modules/lmod/z00-lmod.sh/cm/images/default-image/etc/sysconfig/modules/lmod/z01-default_modules.sh

Once the script has been run to set up the OHPC repository with Bright, then cluster admins can then install packages via yum or zypper from the head node. No action is needed for the compute nodes to see these changes. As with any module, users should then load with "module load" and "module unload".