Markus Hilger
9dd5802698
- the aarch64 osdeploy spec builds the stateful suse16 addons but its diskless loop was never extended, so the aarch64 rpm shipped suse16 without suse16-diskless and a packed image got a dangling addons.cpio. - imgutil's builddeb keeps its own copy of the directory list that confluent_imgutil.spec.tmpl has, and it had learned about neither suse16 nor el10. - gather_bootloader gained a /usr/share/efi fallback for shim on both architectures but only for x86_64 on grub, so an aarch64 root found a shim and then died copying grub. Finally, rewriting repos.d file by file rather than copying the tree meant a subdirectory or a file that is not valid UTF-8 aborted the build before any package was installed, which also regressed SUSE 15. Pass anything that is not a plain text repo definition through untouched and restore the modes on the ones that are rewritten.
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.