[opensourcedex]

ohpc is a free, open source frameworks & platforms project written in C and released under Apache-2.0. It has 1,009 GitHub stars, 209 forks and 9 open issues, and was last pushed 23 hours ago. On this registry it ranks #119 of 132 tracked projects in Frameworks & Platforms, with 5 head-to-head comparisons available.

What is ohpc?

OpenHPC (the ohpc repository) is the integration, packaging, and test repository for community-built packages and installation guides used to deploy and manage HPC Linux clusters, aimed at system administrators and scientific computing teams that want pre-built cluster components.

What it is

OpenHPC is a community project, and the ohpc repository is its integration, packaging, and test repository. It supplies common, pre-built ingredients required to deploy and manage an HPC Linux cluster, covering provisioning tools, resource management, I/O clients, runtimes, development tools, containers, and scientific libraries. Three release series—2.x, 3.x, and 4.x—each target different major Linux OS distributions, so packages and guides track the distribution generation rather than a single fixed platform.

The concrete problem is the assembly and lifecycle management of an HPC software stack across supported Linux distributions. OpenHPC addresses it by publishing pre-built binaries through repositories that work with standard package managers such as dnf and zypper, and by supplying installation guides tailored to each supported provisioning system and resource manager. Rather than sourcing and integrating each component separately, an administrator enables the relevant OpenHPC repository and follows a documented, distribution-matched cluster installation path for the chosen release series.

Key capabilities

  • Pre-built binaries are delivered through OpenHPC repositories and consumed with standard Linux package managers, including dnf and zypper.
  • The ohpc-release RPM includes GPG keys for package signing and defines the URL locations for the base and update package repositories.
  • Three release series align the stack with supported OS targets: 2.x for EL8 and Leap15, 3.x for EL9, Leap 15, and openEuler 22.03, and 4.x for EL10 and openEuler 24.03.
  • Installation guides are provided for each supported provisioning system and resource manager, with detailed example instructions for installing a cluster.
  • The recipe explorer renders a matching installation guide after the user chooses a base OS, architecture, provisioner, and resource manager, covering current releases and development branches.
  • The packaged stack spans provisioning tools, resource management, I/O clients, runtimes, development tools, containers, and scientific libraries, with MPI and scientific computing represented in the project topics.

Who uses it and how

  • HPC system administrators and scientific computing teams use it to deploy and manage Linux clusters with pre-built provisioning, resource-management, runtime, container, and library components.
  • Sites running EL8 or Leap15 use the 2.x series; sites on EL9, Leap 15, or openEuler 22.03 use the 3.x series; sites on EL10 or openEuler 24.03 use the 4.x series.
  • Operators select their base OS, architecture, provisioner, and resource manager in the recipe explorer to obtain the installation guide that matches their environment.
  • Contributors request additional software by opening an issue with detail or by submitting a pull request; component PRs are expected to include tests and documentation and follow CONTRIBUTING.md.

Getting started

To get started, install the ohpc-release RPM for the appropriate release series to enable an OpenHPC repository locally, then install packages with dnf or zypper. The ohpc-release package, installation guides, and more information are available on the relevant 2.x, 3.x, or 4.x release series pages, and the guides can be read through the recipe explorer.

How it compares

The supplied facts name no paid products and no comparable alternative tools. Within this registry, OpenHPC therefore stands alone as the described integration, packaging, and test layer for HPC Linux clusters.

When to use it — and when not to

OpenHPC fits organizations that run a supported Linux distribution and want a package-manager-based route to an HPC cluster stack, following a guide matched to their provisioning system and resource manager. A self-hoster must enable and maintain the OpenHPC repository configuration through ohpc-release, including its GPG keys and the defined base and update URL locations, and must stay within the documented release-series and OS combinations. It is not a fit for anyone outside those supported OS targets or for anyone expecting the README alone to contain the full installation procedure, because detailed instructions live on the release series pages and in the recipe explorer.

project readme (upstream, from github) — read inline

OpenHPC

Community building blocks for HPC systems

Introduction

This stack provides a variety of common, pre-built ingredients required to deploy and manage an HPC Linux cluster including provisioning tools, resource management, I/O clients, runtimes, development tools, containers, and a variety of scientific libraries.

There are currently three release series: the 2.x, the 3.x and the 4.x which target different major Linux OS distributions:

  • The 2.x series targets EL8 and Leap15.
  • The 3.x series targets EL9, Leap 15 and openEuler 22.03.
  • The 4.x series targets EL10 and openEuler 24.03.

Getting started

OpenHPC provides pre-built binaries via repositories for use with standard Linux package manager tools (e.g. dnf or zypper). 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. Installation guides tailored for each supported provisioning system and resource manager with detailed example instructions for installing a cluster are also available. Copies of the ohpc-release package and installation guides along with more information is available on the relevant release series pages (2.x, 3.x or 4.x). The installation guides can also be read online in the recipe explorer: choose a base OS, architecture, provisioner and resource manager, and it renders the matching guide for the current releases and development branches.

Questions, Comments, or Bug Reports?

Subscribe to the users email list or see the page for more pointers.

Additional Software Requests?

If you would like to see new software included in OpenHPC, please open an issue with as much detail as possible. Even better, consider opening a pull request directly. A PR for a new component should typically include tests and documentation, but we are happy to guide contributors through the process.

Contributing to OpenHPC

Please see the steps described in CONTRIBUTING.md.

Project governance

OpenHPC is governed by a Governing Board and a Technical Steering Committee (TSC). The governance documentation, including the current TSC members, the TSC election process and the TSC meeting details, is maintained in the openhpc/governance repository.

Register your system

If you are using elements of OpenHPC, please consider registering your system(s) using the System Registration Form.

Frequently asked questions

Is ohpc free to use?

ohpc is open source under the Apache-2.0 licence. There is no licence fee and no seat count — you can self-host it or, where the project offers one, pay a vendor for a managed version instead.

What does ohpc do?

OpenHPC Integration, Packaging, and Test Repo

What is ohpc written in?

ohpc is primarily written in C. Its source is publicly available at https://github.com/openhpc/ohpc, and it has 1,009 GitHub stars.