GitLab

Don't fetch the OPA libraries when they are already installed via RPM. Add the OPA plugin to the list of plugins to be built by default.

- New filtering methods applies a filtering regular expression to all
node names in the node list of a job; the mode of the filtered node names
is then computed, and the job is processed only if this matches an
arbitrary "match" string
- Can be used to assign jobs to different islands in a HPC system based
on the allocation of nodes

- Allows to reduce the size of the query results considerably

- Uses an overloaded version of the querySensor() method

- overloaded query() and fuzzyQuery() methods that allow to query a set
of sensor IDs at the same time
- also changed the behavior of fuzzuQuery(): only one query is performed
now, retrieving the most recent value BEFORE the specified timestamp

- Allows to print the covariance matrices of the gaussian mixture model

- Can be used to increase the number of data points for model training

- Suppressing an integer comparison warning

- Implemented "means" REST API action
- Integrated the Mahalanobis distance outlier cut

- A plugin based on gaussian mixture models to enable clustering for
performance variation analysis or outlier detection

- If a single unit of an operator fails computation, this does not
prevent anymore all other units from computing

- Will not crash anymore with an empty sensor tree

Adding more uniqueness for job ids from slurm (now user and number of nodes has to match). Refactored a little as well.

- Removed obsolete updateMetadata field

- Allows to remove all existing operations from a certain sensor

- The new implementation allows to publish multiple operations
concurrently from different sources

It is now possible to create proper RPM packages of Pusher and associated dependencies
After package installation one should consider modifying the config files in /etc/dcdb first
The package build process is still anything but good practice

- Can be disabled by toggling the isOperation metadata field for each
sensor

- Implemented a (overloaded) publishSensor method in SensorConfig that
uses a SensorMetadata object to publish metadata selectively - only
columns that are set are updated, query statement is built on the fly
- Changing type of operations to set of strings still pending

- Allows to encode "not set" states for single members