Markus Hilger
8521c6ad4b
bmc.py, serversession.py, fakebmc.py and virshbmc.py were byte identical to upstream pyghmi: the async port went through the session layer beneath them and left the server side alone. So every response created a coroutine and dropped it, and the overrides the now async parent awaits returned None. Running fakebmc bound no socket, spun a core, and answered nothing. Everything that sends a response is a coroutine now, and so is the dispatch that reaches it; the hooks a subclass implements stay ordinary functions, so an out of tree Bmc is unaffected unless it overrides the payload handlers. Two things had to leave their constructors, both being coroutines: assigning the server socket, into bind(), which is why listen() is no longer a classmethod, and answering the open session request, into send_open_session_response. Verified against upstream with ipmitool over nine commands, with identical output. SOL is not covered: fakebmc reports the payload disabled on both.
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.