We strive to make incremental updates at roughly 6 months intervals. Release history and roadmap information can be found on the GitHub Wiki.
What is the overall support plan for OpenHPC?
OpenHPC offers community driven support via several email lists for end users and developers.
What tool sets are included in OpenHPC?
Please see the Component List page on the GitHub Wiki for the latest list of packages. In addition, the documentation for each release includes a manifest of pre-packaged components (and their version info).
Is it required that all components from the stack be used or can you pick and choose?
No, it is not required to install all components. In particular, development tools and libraries can be chosen based on local application requirements. Note, however, that package dependencies are includes as part of the OpenHPC integration effort, so sub dependencies may be required in order to install particular components.
How can one view the dependencies of packages and the resulting growth in code size as packages are added?
Package dependencies can be ascertained via package manager tools during installation from an OpenHPC repository (or mirror). Similarly, the repository size can also be queried via standard package manager tools (e.g. “dnf repoinfo”).
Is the base OS included in with the stack?
No. A supported base operating system should be installed first.
What is meant by build and test environment?
The build environment refers to the Open Build Service (OBS) that serves as the underlying build infrastructure. It initiates package builds based on commit triggers, tracks inter-package dependencies, and publishes resulting repositories. The test environment corresponds to the use of continuous integration (CI) infrastructure and the companion OpenHPC test suite to carry out a variety of integration oriented tests as the project evolves.
How is the OpenHPC stack validated?
Included within OpenHPC is an integration test suite that is executed on a variety of cluster platforms prior to release. The intent of this suite is to ensure basic functionality of each tested component when installed on a cluster beginning with a bare metal installation.
How were the initial packages for the stack selected?
Package selection was prioritized initially with an initial goal of being able to provide basic end-to-end functionality for common services typical of HPC deployments. The initial functionality includes example provisioning and resource management services along with a variety of administrative utilities and development tools/libraries.
How are future packages for the stack selected?
Package selection will be prioritized based on a number of factors including (but not limited to) its relevance and usage by the HPC community, development stability, required integration effort, coexistence capability with other included packages, functionality coverage, and willingness of community members to help integrate and maintain the package. Requests for package inclusion can be made in our Submission Repository.