**As of August, 2020 this site has been moved and reorganized to https://github.com/ovis-hpc/distribution/ ** This site will continue as baallan's development repo for work to be eventually published at ovis-hpc.

As of Dec 2018, there are several planned platforms, organized by directory. See below for instructions on package construction.

Platforms with binary packaging

• v43.toss3.opt.stable/ TOSS 3 RHEL 7 derivative as Software Collections

• toss2/ TOSS 2 RHEL 6 derivative with specialized plugins is deprecated.

• toss3/ TOSS 3 RHEL 7 derivative with specialized plugins

• rhel6/ desktop Redhat Enterprise 6 without specialized subsystems is deprecated.

• rhel7/ desktop Redhat Enterprise 7 without specialized subsystems.

• rhel7-rabbitmq/ desktop Redhat Enterprise 7 with librabbitmq packages added.

Platforms with source build examples

• u16/ Ubuntu 16 without specialized plugins
• If you wish to contribute a binary build (.deb format), please contact ovis-help@sandia.gov.

Making software collections for LDMS (/opt packages)

Clone this repository to a scratch directory, go to the directory of interest and follow the README.md. Building the collections has multiple "package, then install" steps unless you have advanced package building automation.

Making packages

Clone this repository to a scratch directory, go to the directory of interest, and execute the firerpms script. E.g.

git clone gitlab@gitlab.opengridcomputing.com:baallan/distribution.git
cd distribution
cd rhel7
./firerpms

If successful, this will get you a list of rpms for the latest stable public release on that platform. The rpms are relocatable, which is at variance with most Linux distribution's standard policies. You will need pre-installed the utility packages for building RPMs in general. This works for LDMS v3 and other versions installed in the standard /usr prefix by default.

Making packages off the grid

Sites which need to build RPMs on a machine without external access to github must stage a clone (not a zip file) of distribution, ovis, and SOS repositories. See the OffGrid.md instructions for the simplest way to do it.

Installation

See the Installation.md file for RPM usage guidance.

What is new

See v2Comparison.md for info on how the current release compares to LDMS v2.

Making test packages

For any platform, there may also be a $platform.unstable/ directory containing development, test, and historical builds. Third parties should not attempt to build these unstable packages. These will be under numerous names. There will often be a firerpms script which combines the most recent development sources. In many cases the repositories used will require special access privileges. When working with test packages, pay particular attention to the variables at the top of the fire script which control repository and branch.

Configuring an HPC cluster with LDMS

Scalable configuration management of clusters is most easily done using the libgenders options to control the ldmsd systemd service. An example of this is given in gendersTutorial.md.

Packaging for versions 4 of OVIS

The optional object store sosdb uses python/numpy/cython for easy access to data arrays in python. The default RHEL 7 Numpy (1.7) and Cython (0.19) are incompatible with sosdb usage. While personal builds can be performed with any modern batteries-include python distribution instead of Redhat's, rpm builds require known rpms for cython and numpy, so these are provided in the toss3.numpy and toss3.cython directories.

• The numpy and cython rpm spec files and generated rpms for python 2.7 will also work in plain RHEL 7 environments.
• v41.rhel7.unstable: This builds the v4.x series for RHEL7. It currently uses v4.2.3 OVIS and corresponding v4.2.1 SOS for TOSS 3, both from github.
• v42.toss3.unstable: This builds the 4.2.3 OVIS and 4.2.1 SOS for TOSS 3.4.
• v43.toss3.opt.unstable: This builds the 4.3.1 OVIS and 4.3 SOS for TOSS 3.5 /opt deployments.

Packaging conflicts for EPEL and Redhat note: unsatisfied dependencies

If you build the ovis packages on a machine with EPEL bits in the environment, it is entirely likely that the packages will not be usable in a pure Redhat environment. In particular we have observed installation failures on plain redhat 7 with errors such as "libssl.so.1.1 missing" even though the openssl packages are present. This occurs if the ovis packages are built on a machine with newer ssl installed via EPEL and then installed on a non-EPEL machine. This is a misuse of the packages, not a bug in our RHEL 7 packaging scripts.