Markus Hilger
ee35fba8bf
A bmc may keep its sensor data records on the sensor device instead of in a repository, and this one does, so it had no sensors, no health and only a partial inventory over ipmi. The records themselves are identical, version 0x51 and the same types, so everything that decodes them is reused as is. Only the fetching differs: a command of its own, a reservation of its own, and records held per lun rather than in one place. The luns to ask, and a change indicator to cache on, come from Get Device SDR Info. The fetch is written out rather than shared with the repository one. The loops are alike, but nothing available here has a repository to test against, and the price of factoring them together is that a mistake would land on every bmc that works today rather than only on those that do not work at all. Records are cached in memory and on disk exactly as repository records are, keyed on the change indicator, and a device that offers no such indicator is read afresh each time rather than cached wrongly. Names are stripped of the nulls that pad a fixed width field. This bmc pads every name out to sixteen bytes, and a name carrying them cannot be matched by a caller asking for a sensor by name. On the bmc this was written for: 163 sensors and 9 frus, against the 163 the device reports it has. The 54 temperatures and 36 fans it now reads match what the same machine reports over redfish, to within the precision each side gives.
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.