Markus Hilger
bd5d7ffb94
Redfish identifies an account by a string, and an implementation is free to use the account name, which this one does. The handler converted the last element of the path to an integer, so every per user read, update and delete answered "invalid literal for int() with base 10: 'root'" as an unexpected error, with a traceback to match. Confluent offered the id itself, listing the account as "root", and then could not accept it back. Take the element as given. Everything below already compares ids as strings, and the input parsing already keeps a non numeric uid, so only this conversion stood in the way. nodebmcpassword goes through exactly this path, reading users/all for the id and then writing to that account, so it could not work at all on such a bmc. ipmi users really are numbered slots, so the conversion is right there and stays, but say so when it fails rather than letting a ValueError surface as an unexpected error.
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.