(5 June 2020)

There are currently two release tracks of OpenHPC, both consisting of binary downloads in the form of RPMs. These RPMs are organized into repositories that can be accessed via standard package manager utilities (e.g. yum, zypper). The 1.3.x track of OpenHPC provides builds that are compatible with and tested against CentOS 7.7 as well as SUSE Linux Enterprise Server 12 SP4 and the 2.x track builds against CentOS 8.1 and OpenSUSE Leap 15. A typical deployment on a new system will begin with the installation of the base operating system on a chosen master host identified as the system management server (SMS), followed by enabling access to a compatible OpenHPC repository.

The OpenHPC repository is created and maintained using a dedicated instance of the Open Build Service (OBS) that is available here for the 2.x series, and here for the 1.3.x series. Once built by OBS, packages are mirrored at http://repos.openhpc.community.

To get started, you can enable an OpenHPC repository locally through installation of an ohpc-release RPM which includes gpg keys for package signing and defines the URL locations for [base] and [update] package repositories. A copy of the ohpc-release RPM is available for download here:

2.x Series:

1.3.x Series:

Install Recipes

To aid in the installation of OpenHPC packaged components,  a variety of companion installation recipes are available. These can be obtained via installation of the docs-ohpc RPM after the OpenHPC repository has been enabled locally. Alternatively, copies of the guides are also provided for each release track on the OpenHPC GitHub Wiki:

The intent of these guides is to present a simple cluster installation procedure using components from the OpenHPC software stack. The documentation is intended to be reasonably generic, but uses the underlying motivation of a small, stateless cluster installation to define a step-by-step process. Several optional customizations are included and the intent is that these collective instructions can be modified as needed for local site use cases.  Please consult the install guide for more detail and discussion regarding a companion template install script.