ceph-mirror/qa
ShreeJejurikar efe54523a4 rgw: support kafka 4.x brokers
librdkafka submodule

Vendors librdkafka v2.12.1 as a submodule (default) and teaches the
notification teuthology task to set up Kafka 4.x KRaft brokers. The
distro-shipped librdkafka 1.6.1 cannot SCRAM-auth against Kafka 4.x
brokers (#75900); the bundled version fixes that. Build with
WITH_SYSTEM_RDKAFKA=ON to opt back into the distro library (floor 2.6.1).
follwinf changes needed with teh submodule:
* build kafka_stub only in case of system librdkafka
* use the same header location in submodule and system
* supress compilation warning to avoid -WError issues

2.12.1 matches Fedora(44)'s current librdkafka-devel, so the vendored copy
tracks a version that distro packagers have already vetted rather than
whichever release happens to be latest upstream.

The teuthology version matrix picks one of {3.9.2, 4.1, 4.2, 4.3} per run.
3.9.2 covers the last Zookeeper-based release for the migration cohort.
4.1/4.2/4.3 track Apache's current three supported minor lines and are
resolved to the latest patch at test time via dlcdn.apache.org/kafka/, so
new patches within a supported minor need no PR update. A new minor line
(4.4) requires renaming one YAML.
* new java version (17) is needed for kafka 4.2 and up (we wil use it on
  all version)
* kerberos task need to run before the kafka install task

After pulling this branch, fetch the new submodule:

    git submodule update --init src/librdkafka

Fixes: https://tracker.ceph.com/issues/77336

Signed-off-by: ShreeJejurikar <shreemj8@gmail.com>
Co-authored-by: Yuval Lifshitz <ylifshit@ibm.com>
2026-07-22 10:29:04 +00:00
..
archs
cephfs qa/cephfs: install ceph-mgr-modules-standard for cephfs tests 2026-05-27 09:55:05 +05:30
client
clusters qa: remove vestiges of ceph-deploy 2026-04-14 09:03:58 -04:00
config qa/crimson: ignore PG_NOT_DEEP_SCRUBBED in all crimson tests 2026-07-09 08:26:47 +00:00
crontab qa/crontab/teuthology-cronjobs: Use debug flavor 2026-01-22 14:56:45 +02:00
debug
distros qa: install nvme-cli only if distro remains rocky10 2026-06-01 12:28:34 -04:00
erasure-code
libceph
machine_types
mds
mon/bootstrap
mon_election
msgr
nightlies
objectstore qa: remove vestiges of ceph-deploy 2026-04-14 09:03:58 -04:00
objectstore_cephfs
objectstore_crimson qa/suites/crimson: Add a test for PG merging in the crimson suite 2026-06-11 10:25:49 +05:30
objectstore_debug
overrides qa/suites/upgrade: ignore fs down variant 2026-05-28 13:54:38 -04:00
packages
rbd qa: krbd_blkroset.t: eliminate a race in the open_count test 2026-01-22 16:41:14 +01:00
releases qa/workunits/cephtool/test: update to umbrella 2026-03-25 16:53:04 +00:00
rgw qa/rgw: Run s3-tests from within the Ceph repo 2026-06-22 19:33:47 -04:00
rgw_bucket_sharding
rgw_frontend
rgw_pool_type
standalone Merge pull request #68503 from ifed01/wip-ifed-fix-ncb-expand 2026-07-14 16:23:36 +03:00
suites rgw: support kafka 4.x brokers 2026-07-22 10:29:04 +00:00
tasks rgw: support kafka 4.x brokers 2026-07-22 10:29:04 +00:00
timezone
workunits Merge pull request #67725 from mheler/wip-rgw-transition-recompress 2026-07-16 16:52:07 -04:00
.gitignore
.qa
asan.supp
CMakeLists.txt
find-used-ports.sh
loopall.sh
lsan.supp qa/lsan.supp: suppress CPython 3.12/3.13 interpreter leaks 2026-06-23 23:02:05 +08:00
Makefile
mypy.ini mypy: skip follow_imports for prettytable 2026-06-20 14:49:16 +08:00
README
run_xfstests_qemu.sh
run_xfstests-obsolete.sh
run_xfstests.sh
run-standalone.sh
runallonce.sh
runoncfuse.sh
runonkclient.sh
setup-chroot.sh
test_import.py
tox.ini
valgrind.supp qa/rgw/kafka: add valgrind exception for cyrus-sasl leak 2026-07-16 14:37:55 +00:00

ceph-qa-suite
-------------

clusters/    - some predefined cluster layouts
suites/      - set suite

The suites directory has a hierarchical collection of tests.  This can be
freeform, but generally follows the convention of

  suites/<test suite name>/<test group>/...

A test is described by a yaml fragment.

A test can exist as a single .yaml file in the directory tree.  For example:

 suites/foo/one.yaml
 suites/foo/two.yaml

is a simple group of two tests.

A directory with a magic '+' file represents a test that combines all
other items in the directory into a single yaml fragment.  For example:

 suites/foo/bar/+
 suites/foo/bar/a.yaml
 suites/foo/bar/b.yaml
 suites/foo/bar/c.yaml

is a single test consisting of a + b + c.

A directory with a magic '%' file represents a test matrix formed from
all other items in the directory.  For example,

 suites/baz/%
 suites/baz/a.yaml
 suites/baz/b/b1.yaml
 suites/baz/b/b2.yaml
 suites/baz/c.yaml
 suites/baz/d/d1.yaml
 suites/baz/d/d2.yaml

is a 4-dimensional test matrix.  Two dimensions (a, c) are trivial (1
item), so this is really 2x2 = 4 tests, which are

  a + b1 + c + d1
  a + b1 + c + d2
  a + b2 + c + d1
  a + b2 + c + d2

A directory with a magic '$' file, or a directory whose name ends with '$',
represents a test where one of the non-magic items is chosen randomly.  For
example, both

 suites/foo/$
 suites/foo/a.yaml
 suites/foo/b.yaml
 suites/foo/c.yaml

and

 suites/foo$/a.yaml
 suites/foo$/b.yaml
 suites/foo$/c.yaml

is a single test, either a, b or c.  This can be used in conjunction with the
'%' file in the same (see below) or other directories to run a series of tests
without causing an unwanted increase in the total number of jobs run.

Symlinks are okay.

One particular use of symlinks is to combine '%' and the latter form of '$'
feature.  Consider supported_distros directory containing fragments that define
os_type and os_version:

 supported_distros/%
 supported_distros/centos.yaml
 supported_distros/rhel.yaml
 supported_distros/ubuntu.yaml

A test that links supported_distros as distros (a name that doesn't end with
'$') will be run three times: on centos, rhel and ubuntu.  A test that links
supported_distros as distros$ will be run just once: either on centos, rhel or
ubuntu, chosen randomly.

The teuthology code can be found in https://github.com/ceph/teuthology.git

Note: The performance suites clone CBT from master here: https://github.com/ceph/cbt.git
CBT will not support cosbench beyond release tag v0.3, therefore no qa suite should use cosbench.
cosbench support has been removed from qa/tasks/cbt.py.