Markus Hilger
233fc9ec5a
The redfish event log was taken from every log service the manager advertises, whatever those turned out to be. On a bmc that keeps its systemd journal there, nodeeventlog answered with a thousand lines of kernel probe failures and daemon chatter, and the log the user asked for was never read at all, because this implementation keeps it under the system. Clearing was worse: of the services it did find, the ones with a clear action were the dumps, so a clear destroyed diagnostic data, left the event log untouched, and reported success. Judge a log service before reading it. A service whose id or name says journal, dump, post code, host logger or crash is not an event log, and both reading and clearing skip it, so a clear can no longer take out something that was never asked for. If that leaves the manager with no event log at all, look under the system, where such an implementation keeps it. Only then: a bmc that has one under the manager is served exactly as before, from the same requests, so this cannot change what an implementation that already worked reports. The list of services was also being extended in place, and it belongs to whatever the url cache is holding, so an extra log added by an oem handler accumulated on every call within the cache window.
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.