Markus Hilger
6361fd6578
Deleting a user gave up after one attempt and reported why the fallback of blanking the name failed rather than why the delete did. MegaRAC reports a timeout for a delete that a second ask completes, so retry, check whether the account went away, and keep the original error. Attaching media judged a device free by ConnectedVia, which describes how the device is wired to the host rather than whether anything is in it. Every device on this bmc reports a fixed value there, so nothing was ever selected and the attach reported success having done nothing. Judge by whether an image is loaded, fall back to the properties when an advertised insert action is not served, and say so when no device would take the image. The firmware category was passed to the library and ignored, so core, adapters, disks and misc all returned the same full list. Classify by what each entry is related to, and answer only for core when a platform says nothing about where its firmware belongs. reseat_bay reached for a hardcoded Nvidia action on Chassis_0, so it failed with a not found for that url instead of saying reseat is unsupported.
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.