Markus Hilger
bf9aba73d3
The sdr carries unit fields for every sensor record, and they were read into the reading whether or not the sensor has a number for them to describe. A discrete sensor reports which of its states are asserted and no value at all, so a watchdog came back with units of "% ", and a discrete sensor on a full record picks up a base unit the same way, reporting degrees celsius for a sensor that never has a temperature. A caller that shows the unit alongside whatever value it was handed then prints a unit with nothing to apply it to, which is what the client was taught to skip in 8c8c32cc. The client is not the only consumer of a reading, so answer the question in the library. The record itself says which sensors those are, and the reading path already works it out to decide whether to decode a number: a sensor has one only if the numeric format says how to read it, or the format is unsigned and the record either supports thresholds or is of reading type 1. Ask that once, where the units are assembled, and give the sensors that fail it no unit, so the unit and the value cannot come to different conclusions about whether the sensor has a reading at all. A threshold or numeric sensor reports exactly what it did before, including the ones whose unit is a percentage, a combination of two units, or nothing because the record names no unit. On the Lenovo XCC this was checked against nothing changes: its 305 readable sensors decode identically, discrete ones included, because they are all compact records naming no unit in the first place. The sensors that change are the ones the finding came from, which name a unit on a record that has no number to put it on.
Confluent
Confluent is a software package to handle essential bootstrap and operation of scale-out server configurations. It supports stateful and stateless deployments for various operating systems.
Check this page for a more detailed list of features.
Confluent is the modern successor of xCAT. If you're coming from xCAT, check out this comparison.
Documentation
Confluent documentation is hosted on: https://xcat2.github.io/confluent-docs/
Download
Get the latest version from: https://xcat2.github.io/confluent-docs/downloads/
Check release notes on: https://xcat2.github.io/confluent-docs/release_notes/
Open Source License
Confluent is made available under the Apache 2.0 license: https://opensource.org/license/apache-2-0
Developers
Want to help? Submit a Pull Request.
Versioning and releases
The top-level VERSION file names the release the current branch is working toward. Build scripts
call ./mkversion, which turns it into the version stamped on packages: the tag itself on a release
tag (4.0.1), otherwise a development version (4.0.1.dev5+gdeadbee, or 4.0.1~dev5+gdeadbee for
the packages that have no setup.py).
mkversion also derives a version from the newest tag reachable from HEAD and uses whichever is
higher, so forgetting to bump VERSION after tagging the current branch cannot walk the version
backwards. Staying ahead of tags on other branches is what VERSION itself is for: patch releases
are tagged on release branches, which master never sees.
Cutting a new series:
- Land the release commit on master and tag
X.Y.0there. - Create branch
X.Yfrom that tag; it inheritsVERSION=X.Y.0. - Only then bump
VERSIONon master. Doing it before step 2 leaves the release branch on the wrong series.
Patch releases land on branch X.Y and are tagged X.Y.Z there; no VERSION edit is needed.