Markus Hilger
d77e71967a
Reading the alert destinations of a bmc that has none reported "Unknown code 0x80 encountered", which is the fallback text for a completion code the library has no name for. 0x80 on this parameter is not a failure, it is the platform saying it does not have alert destinations, and the redfish side of the same resource has said so in words for a while. The lan parameter fetch already knew how to tell those apart, so build the alert reads on it rather than on a raw command that raises on any non-zero code, and raise UnsupportedFunctionality with something to read. Both the count and an individual destination are covered, so a platform that offers one and not the other says the same thing instead of failing differently. Splitting the completion code handling out of the parameter fetch is what makes that reuse possible; the interpretation of the payload, and every answer it gives, is unchanged. The oem hook for the destination count was passing its byte through ord(), which raises TypeError on the bytearray it is given. No handler in tree implements the hook, so it had never been called; hand it the integer.
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.