Markus Hilger
db22a3e41a
The oem lookup answers whether it found a handler for the vendor, and that answer was being stored as whether the lookup had been done at all. On anything the map does not name, which is every bmc that is not a Lenovo, the flag stayed false and each oem_init issued another Get Device ID and built another handler. Almost everything goes through oem_init, so this is a round trip added to almost every operation. Where those calls are close together it is far worse than that: reading the sensor data records asks for the event constants once per record, so a run of 172 records fired 176 Get Device ID commands back to back, which was enough to make the bmc stop answering and the read fail with a timeout. The same sequence now takes 3 commands. Settling for the generic handler is an answer. The device id cannot change within a session, so asking again buys nothing, and the handler it throws away each time is the one holding the sensor names it had cached.
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.