Markus Hilger
ba3edc2c02
A caller asking for fans or energy got nothing from any bmc that serves the Sensors collection. Those sensors were filed under their redfish reading type, Rotational for a fan, while the categories are named after the ipmi sensor types the rest of the code uses, so nothing matched. Power appeared to work only by coincidence, Power and Current happening to be spelled the same in both vocabularies. Translate the reading type as the sensor is mapped, so a sensor means the same thing whether it came from the Sensors collection, from the older Thermal and Power documents, or from ipmi. On the bmc this was found on, fans go from nothing to the 24 tachometers, and temperature and power already agreed with what the same hardware reports over ipmi. The fan controls stay out, and cannot be brought in. Their reading type is Percent, which is also what a battery state of health reports, and this bmc fills in no PhysicalContext to tell them apart, so there is nothing to classify them by that would not also drag in unrelated percentages.
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.