Markus Hilger
58d56426ed
There is no ipmi command for a bmc hostname, so get_hostname falls back to the DCMI management controller identifier. A bmc that does not implement the DCMI group at all rejects that with "invalid command", which was handed to the caller as if the request had been bad: nodeconfig <node> bmc read seven fields correctly and then reported "Error: Invalid command", and the api answered 500 Unexpected error. Route every DCMI request through one helper that turns "invalid command" and "command disabled or unavailable" into UnsupportedFunctionality, so the identifier, the asset tag and the hostname all report a platform that cannot do this rather than a fault. Where the caller asked about a hostname, say that rather than naming DCMI. The whole group read still ends in one error line, because an operation a platform cannot perform and one that failed are the same message to the client. That is worth separating, but not here.
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.