Markus Hilger
4ca6ec365d
A stray trailing comma made the update detail a one element tuple, so a firmware error printed as a python tuple. A missing status printed the whole response dict. A failure that named no node was dropped entirely, which is how a service data request that the server refused came out as silence and a success exit code, and nodestorage, nodelicense and nodesupport exited zero even when they had reported an error. nodeconsole crashed decoding an absent screenshot, and again on the terminal calls behind a pipe, where a log replay crashed too; refuse the terminal only modes cleanly and dump the log when there is no terminal to replay into. nodedefine raised a ValueError on an argument without an equals sign, and firmware for a category the target does not describe printed usage as though the question had been malformed. On the server side the readability check was applied to the path a download is saved to, so asking for service data or saved licences at a path that does not exist yet failed claiming the destination was not readable.
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.