Markus Hilger
3563da041b
terminate() called sys.exit(0) from a signal handler while the asyncio loop was running. The SystemExit escaped run_forever, and closing the loop afterwards then failed with "Cannot close a running event loop", so every clean stop wrote a cascade of tracebacks and left a pending task behind. Ask the loop to stop instead: deliver the signals through add_signal_handler, which is the signal safe route, and set an event the main coroutine waits on so that it returns and asyncio can unwind itself. Flush configuration on the way out, as the client requested shutdown has always done. That client requested shutdown went the same way, calling sys.exit from inside a request coroutine, and it is the route the systemd unit uses to stop the service. It now asks for the same orderly stop through a hook the running service registers, keeping the old behaviour when nothing is registered. Measured on all three routes, with redfish and ipmi sessions to a bmc in flight: under a third of a second and no tracebacks, where before each one wrote a cascade.
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.