Markus Hilger
fd84d38bbd
pyghmi asks for this parameter with xraw_command and catches the completion code for a bmc that does not have it, and folding aiohmi in renamed that call to oldraw_command rather than raw_command, so the handler could no longer fire. Answering the code out of the returned dictionary repaired the crash but kept the call on the older contract, which is now the only one left in the tree. Catch it again instead: raw_command puts the completion code on the exception as ipmicode, and nothing here reads the payload of a reply that carries a code, which is the one thing catching gives up. No behaviour change, checked against the previous version over the same fake session for a good reply, an empty one, 0x80 and 0xC9 with and without a stray payload, four other completion codes, a timeout, a lost session and a reply with no data at all: same return value, same exception type, text and ipmicode, same bytes on the wire.
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.