summarylogtreecommitdiffstats
AgeCommit message (Collapse)Author
2024-03-23merge: master <--- feature/v18.2.2-2Bazaah
* HEAD | \ | * c8a69c3 <github@luxolus.com> pkgbuild: pkgrel=2 | * a6b3328 <github@luxolus.com> pkgbuild: use mgr-alias-ceph-bcrypt.patch | * 8f49d39 <github@luxolus.com> repo: add mgr-alias-ceph-bcrypt.patch | / | master Signed-off-by: Bazaah <github@luxolus.com>
2024-03-23pkgbuild: pkgrel=2Bazaah
2024-03-23pkgbuild: use mgr-alias-ceph-bcrypt.patchBazaah
2024-03-23repo: add mgr-alias-ceph-bcrypt.patchBazaah
So that the mgr _actually_ uses our internal bcrypt fork.
2024-03-23merge: master <--- feature/v18.2.2-1Bazaah
* HEAD | \ | * c719c85 <github@luxolus.com> pkgbuild: pkgver=18.2.2 pkgrel=1 | * 3d35081 <github@luxolus.com> pkgbuild: add ceph_bcrypt to python-ceph-common | * 8b874b8 <github@luxolus.com> pkgbuild: add python-bcrypt sources,patches | * 8576de3 <github@luxolus.com> repo: add python-bcrypt patches | * 246af22 <github@luxolus.com> pkgbuild: restrict prepare() patch machinery to ceph-* | * fcde70e <github@luxolus.com> pkgbuild: mv {,ceph-}disable-empty-readable.sh-test | * abc0a56 <github@luxolus.com> pkgbuild: use mgr-ceph-module-stub.patch | * a75f61e <github@luxolus.com> repo: add ceph-18.2.2-mgr-ceph-module-stub.patch | * 93719e4 <github@luxolus.com> pkgbuild: use mgr-dashboard fix backport | * 836304d <github@luxolus.com> repo: backport mgr/dashboard fix for python-cryptography issues | * bfe55db <github@luxolus.com> pkgbuild: rm checkdepends->python-mock | / | master Signed-off-by: Bazaah <github@luxolus.com>
2024-03-23pkgbuild: pkgver=18.2.2 pkgrel=1Bazaah
2024-03-23pkgbuild: add ceph_bcrypt to python-ceph-commonBazaah
2024-03-23pkgbuild: add python-bcrypt sources,patchesBazaah
For our internal ceph fork of python-bcrypt
2024-03-23repo: add python-bcrypt patchesBazaah
- python-bcrypt-allow-subinterpreters.patch - python-bcrypt-prefix-ceph.patch Together, these allow us to build a renamed python-bcrypt package, as ceph_bcrypt. This will allow us to bypass the thorny pyo3 issues we have with various mgr modules exploding at runtime. References: https://github.com/bazaah/aur-ceph/issues/20
2024-03-23pkgbuild: restrict prepare() patch machinery to ceph-*Bazaah
So that we can introduce non ceph patches in future commits
2024-03-23pkgbuild: mv {,ceph-}disable-empty-readable.sh-testBazaah
2024-03-23pkgbuild: use mgr-ceph-module-stub.patchBazaah
2024-03-23repo: add ceph-18.2.2-mgr-ceph-module-stub.patchBazaah
This mocks out a module for mgr_module.py to 'import' during mypy type analysis. Previously the ceph_module.pyi was enough for this to work, but I guess something in the tooling changed. I cannot figure out why this ever worked before, and why it doesn't now. Maybe related to https://github.com/python/mypy/issues/16987 ?
2024-03-23pkgbuild: use mgr-dashboard fix backportBazaah
and remove the now unneeded py deps: - python-pyjwt - python-cryptography
2024-03-23repo: backport mgr/dashboard fix for python-cryptography issuesBazaah
Removes the (limited) runtime usages of python-jwt, and therefore, python-cryptography from the mgr dashboard module. This should restore dashboard functionality, if used alongside a patched pyo3 for python-bcrypt. Upstream-Ref: https://github.com/ceph/ceph/commit/33d8befcabe3e60d9ccf6e4fdc2598c4db22934b References: https://github.com/ceph/ceph/pull/55689 References: https://tracker.ceph.com/issues/63529 References: https://github.com/bazaah/aur-ceph/issues/20 References: https://git.st8l.com/luxolus/pyo3/commit/44d6919168621b46e4e884130ca43338655b020c
2024-03-23pkgbuild: rm checkdepends->python-mockBazaah
Dropped to AUR and I believe unneeded?
2024-02-07merge: master <--- feature/v18.2.1-2Bazaah
* HEAD | \ | * 713b181 <github@luxolus.com> pkgbuild: pkgver=18.2.1 pkgrel=2 | / | master Signed-off-by: Bazaah <github@luxolus.com>
2024-02-06pkgbuild: pkgver=18.2.1 pkgrel=2Bazaah
2023-12-31merge: master <--- feature/v18.2.1-1Bazaah
* HEAD | \ | * 41cb754 <github@luxolus.com> pkgbuild: pkgver=18.2.1 pkgrel=1 | * bb264d0 <github@luxolus.com> repo: rm ceph-17.2.6-mgr-dashboard-node-version.patch | / | master Signed-off-by: Bazaah <github@luxolus.com>
2023-12-31pkgbuild: pkgver=18.2.1 pkgrel=1Bazaah
2023-12-31repo: rm ceph-17.2.6-mgr-dashboard-node-version.patchBazaah
No longer needed, the upstream as upped their nodejs version. References: https://github.com/ceph/ceph/pull/52828 Upstream-Ref: https://github.com/ceph/ceph/commit/47f49e5b1ae2e5bf7aad5df23d877ae5df00210c
2023-11-06merge: master <--- feature/v18.2.0-2Bazaah
* HEAD | \ | * 5b3013f <github@luxolus.com> pkgbuild: pkgrel=2 | * 1ea1d50 <github@luxolus.com> pkgbuild: tidy up check() | * 110161f <github@luxolus.com> pkgbuild: switch off verbose build | / | master Signed-off-by: Bazaah <github@luxolus.com>
2023-11-06pkgbuild: pkgrel=2Bazaah
2023-11-06pkgbuild: tidy up check()Bazaah
pkill is not required by checkdepends anymore rendering this loop useless, and I haven't seen orphan processes so far. Can always add it back later if needed.
2023-11-06pkgbuild: switch off verbose buildBazaah
The build is in a good enough spot now that the extra verbosity is unneeded for most operations.
2023-09-09merge: master <--- feature/v18.2.0-1Bazaah
* HEAD | \ | * 321091d <github@luxolus.com> pkgbuild: pkgver=v18.2.0 pkgrel=1 | * fe66554 <github@luxolus.com> justfile: add cexec, ctest, repackage targets | * 343f78c <github@luxolus.com> justfile: improvements to upload to handle new packages | * 3ddb703 <github@luxolus.com> justfile: remove watch, logs | * 9ca7efd <github@luxolus.com> gh-upload-artifact: try pretty print happy path of upload | * 4cc7eb5 <github@luxolus.com> pkgbuild: updates to install files for v18 | * b019b81 <github@luxolus.com> pkgbuild: enable optional rbd components | * 1ce90d2 <github@luxolus.com> pkgbuild: disable proprietary rgw backends | * 76a50ba <github@luxolus.com> pkgbuild: disable tracing / opentelemetry | * 030000e <github@luxolus.com> pkgbuild: reenable system utf8proc | * ffbeef6 <github@luxolus.com> pkgbuild: use backport-log-runway-expansion.patch | * 216795b <github@luxolus.com> repo: add backport-log-runway-expansion.patch | * 9e5e0ad <github@luxolus.com> pkgbuild: use fix-ecode-shec-test.patch | * 2f5f113 <github@luxolus.com> repo: add ceph-18.2.0-fix-ecode-shec-test.patch | * 1f5029b <github@luxolus.com> pkgbuild: use ceph-18.2.0-fmt10-fixes.patch | * 279af4c <github@luxolus.com> repo: add ceph-18.2.0-fmt10-fixes.patch | * c1d084d <github@luxolus.com> repo: update ceph-17.2.4-test-bluefs-split.patch | * 5dd05c5 <github@luxolus.com> repo: rm upstreamed iterator depreciations | * ef24ee7 <github@luxolus.com> pkgbuild: update tox-mypy-false-postive.patch | * 5b923a5 <github@luxolus.com> pkgbuild: rm upstreamed gcc13 patches | * 4095603 <github@luxolus.com> pkgbuild: rm delete-test-librados-asio.patch | * a60c26a <github@luxolus.com> pkgbuild: rm -DFMT_DEPRECATED_OSTREAM | * 1531a6a <github@luxolus.com> pkgbuild: rm ceph-17.2.4.-tox-cephadm-rm.patch | * 187fed6 <github@luxolus.com> repo: revert backport-with-fmt-version.patch | * 4df4495 <github@luxolus.com> pkgbuild: add inetutils,xmlstarlet to checkdepends | * f36dcde <github@luxolus.com> pkgbuild: add makedepend 'thrift' | * da1d129 <github@luxolus.com> pkgbuild: cleanup pkgname, reorganize arch,pkgdesc | * bfd09af <github@luxolus.com> pkgbuild: reorganize makedepends, checkdepends | * f649488 <github@luxolus.com> pkgbuild: package virtual targets | * bf7fef7 <github@luxolus.com> pkgbuild: package misc. ceph tooling / libs | * eb35c47 <github@luxolus.com> pkgbuild: package more client / utils | * 0c50604 <github@luxolus.com> pkgbuild: package ceph cluster components | * f115c61 <github@luxolus.com> pkgbuild: package ceph python libs | * 7f61cf4 <github@luxolus.com> pkgbuild: package core clients | * d2936ef <github@luxolus.com> pkgbuild: package core libs | * 38b0f6b <github@luxolus.com> pkgbuild: add func _make_ceph_packages | * 7666ef7 <github@luxolus.com> pkgbuild: add _package, _print funcs | * a2346ce <github@luxolus.com> pkgbuild: rm old package() functions | / | master Closes: #16 Signed-off-by: Bazaah <github@luxolus.com>
2023-09-09pkgbuild: pkgver=v18.2.0 pkgrel=1Bazaah
2023-09-09justfile: add cexec, ctest, repackage targetsBazaah
- cexec Executes the given arg list inside the chroot > Build the 'osd' CMake target `just cexec make -j$(nproc) -C build osd` - ctest Runs ctest (with the optional args) inside the chroot > Run testsuite `just ctest` > Rerun only failed tests `just ctest --retry-failed` > Run a regex filtered list of tests `just ctest -R some_unittest` - repackage Repackages the project without triggering a rebuild
2023-09-09justfile: improvements to upload to handle new packagesBazaah
Now use an @all alias instead of naming packages directly, and pretty print the uploadees with column -t (from util-linux)
2023-09-09justfile: remove watch, logsBazaah
These never worked correctly anyway
2023-09-09gh-upload-artifact: try pretty print happy path of uploadBazaah
If curl returns success, assume the result is json and pipe through jq. This improves the output substantially as before it printed a compressed no-newline json blob for each artifact uploaded.
2023-09-09pkgbuild: updates to install files for v18Bazaah
Minor updates to the installed files for: - ceph-common - librbd - librgw - ceph-cephadm
2023-09-09pkgbuild: enable optional rbd componentsBazaah
- WITH_RBD_RWL, WITH_RBD_SSD_CACHE Enables the rbd writeback cache, both pmem and ssd variants. - WITH_RBD_MIRROR Enables mirroring rbd images between ceph clusters, similar to rgw multi-zonal replication These changes were prompted by github.com/Enelar in github.com/bazaah/aur-ceph/pull/18/commits/41a3081df83fb7ab9fd9d94f736ded417afb58da References: https://docs.ceph.com/en/reef/rbd/rbd-persistent-write-log-cache References: https://docs.ceph.com/en/reef/rbd/rbd-mirroring/
2023-09-09pkgbuild: disable proprietary rgw backendsBazaah
These are some seagate/intel specific features, seemingly to use ceph rgw as the S3 interface to their products, and/or supporting some intel encrypt/decrypt hardware. These are (currently) disabled by default, but I have added them for future proofing. I think these will never be valid/useful compile options on Archlinux.
2023-09-09pkgbuild: disable tracing / opentelemetryBazaah
My reasoning here is to avoid adding _even more_ dependencies to ceph-libs. I do want to revisit these when/if I break up the mega packages into separate libs
2023-09-09pkgbuild: reenable system utf8procBazaah
Was switched to default disabled, reenabling it here for our builds. Upstream-Ref: https://github.com/ceph/ceph/commit/90662cad562fffbdeac33f3b79eac6a02eff8c2a
2023-09-09pkgbuild: use backport-log-runway-expansion.patchBazaah
2023-09-09repo: add backport-log-runway-expansion.patchBazaah
This fixes failures found in test_concurrent_dir_link_and_compact_log_56210 where the underlying machinery would attempt to write into a too-small ondisk segment. We just backport the entire patch from `main`. Upstream-ref: https://github.com/ceph/ceph/commit/93961385d79a9fef44266181ce6a2c2b805093d4 References: https://github.com/ceph/ceph/blob/main/src/test/objectstore/test_bluefs.cc#L1359 References: https://github.com/ceph/ceph/pull/50216 References: https://tracker.ceph.com/issues/58759
2023-09-09pkgbuild: use fix-ecode-shec-test.patchBazaah
2023-09-09repo: add ceph-18.2.0-fix-ecode-shec-test.patchBazaah
Fixes some undefined behavior in src/test/erasure-code/TestErasureCodeShec_arguments.cc found while when attempting to cast std::initializer_list to std::array. Instead, use std::vector which has a constructor for std::initializer_list<T>. References: https://en.cppreference.com/w/cpp/container/array/to_array
2023-09-09pkgbuild: use ceph-18.2.0-fmt10-fixes.patchBazaah
2023-09-09repo: add ceph-18.2.0-fmt10-fixes.patchBazaah
This is fairly wide ranging series of patches, fixing multiple compile errors owing changes in fmtlib 9 and 10. Care was taken to attempt to not introduce #includes for fmtlib headers in the public headers of the project, largely through defining a sister <header file>_fmt.h header that just contains the necessary fmtlib definitions, along with importing these files into src/... files as needed. This appears to be the convention (at least, in some parts) of the upstream codebase. Briefly outlined, these are issues fixed: 1. Missing fmt::ostream_formatter definitions for types These used to be implicit, but now fmtlib requires that types specifically opt into this behavior. ~ src/common/LogEntry.h: clog_type, LogEntry + src/include/neorados/RADOS_fmt.hpp: neorados::Object + src/include/types_fmt.h: shard_id_t 2. Missing format_to() interface for ceph_le<T> According to the upstream docs, it should be possible to just use the explicit cast to the underlying T for formatting, but for whatever reason, this doesn't work. Therefore, define a templated format_to() for ceph_le<T> casting to the underlying T, explicitly. This is a fmtlib 10 feature -- previously format_to() was reserved for enums. However, this is the simplest method I can see to avoid needing to #include fmtlib headers in this header tree. ~ src/include/byteorder.h: ceph_le<T> 3. Make fmt::formatter.format definitions const Required since fmtlib 8, but seemingly only became an issue in 10. ~ src/osd/osd_types_fmt.h: chunk_info_t, pg_info_t, SnapSet, ScrubMap::object, ScrubMap 4. Explicitly from snapid_t to uint64_t for fmt::sprintf calls As the fmt::formatter.parse implementation for snapid_t does not handle the formatting qualifier used (or any at all). I think previously this implicitly was casted to uint64_t anyway, so we're just making the behavior explicit. ~ src/osd/SnapMapper.cc: snapid_t 5. Adding a fmt::formatter implementation for EntityName Appears to have another casualty in the "no longer try implicit casts" behavior change of fmtlib 10 ~ src/common/LogEntry.h: EntityName In addition to the above, we defer LogEntry's formatter to the ostream implementation rather than duplicating the same output, separately in the fmt::formatter.format definition. References: https://github.com/fmtlib/fmt/releases/tag/10.0.0 References: https://github.com/fmtlib/fmt/releases/tag/8.0.0
2023-09-09repo: update ceph-17.2.4-test-bluefs-split.patchBazaah
mostly fixes to line offsets, but there was one real if small change to a variable init.
2023-09-09repo: rm upstreamed iterator depreciationsBazaah
This commit removes the patches to three files from ceph-17.2.5-fix-iterator-depreciations: - src/include/xlist.h - src/include/rados/librados.hpp - src/crimson/os/seastore/omap_manager/btree/string_kv_node_layout.h As the upstream has fixed them. However, the patches to the following have not yet been applied upstream, and thus remain: - src/include/rangeset.h - src/msg/async/dpdk/circular_buffer.h Upstream-Ref: https://github.com/ceph/ceph/commit/77a3ed56a7b7326814ea5d37214bec1d88ec334e Upstream-Ref: https://github.com/ceph/ceph/commit/691119c389e119a03aea606b7c4093d46c6db43d Upstream-Ref: https://github.com/ceph/ceph/commit/905969611d256b6613bd86347bd51ddeb0603b79 Upstream-Ref: https://github.com/ceph/ceph/commit/c662ee698c6366e1b53856eb1a2c903c301a426f
2023-09-09pkgbuild: update tox-mypy-false-postive.patchBazaah
same patch as before, but context needs updating to apply correctly
2023-09-09pkgbuild: rm upstreamed gcc13 patchesBazaah
The changes within are now included in the upstream, and are no longer needed Upstream-ref: https://github.com/ceph/ceph/pull/50438
2023-09-09pkgbuild: rm delete-test-librados-asio.patchBazaah
No longer applies to the upstream
2023-09-09pkgbuild: rm -DFMT_DEPRECATED_OSTREAMBazaah
There seems to just be a large amount of effort across the entire project for this one. Not surprising, given my investigations but it does make it difficult to provide a singular upstream reference for this change. Instead I'll just link directly to all the commits involved since v17.2.0... - ceph/ceph@d8d93b0fe3b crimson/osd: correct the fmt::formatter<WatchTimeoutRequest> - ceph/ceph@71b9344f299 crimson/os: specialize fmt::formatter<> for StagedIterator - ceph/ceph@32e207da3f3 crimson/os: include fmt/os.h for printing std::error_code - ceph/ceph@85830863fa4 crimson: specialize fmt::formatter<> for formatting using {fmt} - ceph/ceph@76e4c5d83c2 test/librados/aio_cxx: use fmt formatting - ceph/ceph@2e7aea7b0fd crimson/os: print pointer using fmt::ptr() - ceph/ceph@c9569f8eb02 crimson: specialize fmt::formatter<> - ceph/ceph@01f6bef6e52 *: specialize fmt::formatter<> for formatting using {fmt} - ceph/ceph@3f67d67ede1 crimson: specialize fmt::formatter<> to print using {fmt} - ceph/ceph@42dc970392e crimson/net: print shared_ptr using fmt::ptr() - ceph/ceph@fe1e6b6c4eb neorados: compile with fmt v9 - ceph/ceph@b2c61113ffb crimson/net: define fmt::formatter for write_state_t - ceph/ceph@1f1398bc515 mon: Fix snprintf truncation warning by switching to fmtlib - ceph/ceph@93dfb7e88b9 common: improving fmtlib handling of ceph::utime_t - ceph/ceph@3d7a895d197 include/object_fmt: mark fmt::formatter<>::format() const - ceph/ceph@2901943618f common/LogEntry: specialize fmt::formatter<LogEntry> - ceph/ceph@6e223a68021 common/Journald: include msg/msg_fmt.h - ceph/ceph@c0a3d460297 mon: use fmt::format for stderr cluster logging - ceph/ceph@cef04bc4ed0 common: use fmt::format for stderr logging - ceph/ceph@31aa539f266 osd: use fmt/ranges.h for printing ranges - ceph/ceph@b7b7ff4cce3 include/types_fmt: use fmt::join() to format containers - ceph/ceph@b287fadde3e fmt: pickup v8.1.1 - ceph/ceph@3c46dd64bbc cmake: bump up required fmt version - ceph/ceph@01f9dc84826 msg/msg_type: use fmt::format to print entity_addr - ceph/ceph@ac114ad172b crimson/os: use fmt::format() instead of sstream - ceph/ceph@bb9d099ede8 crimson: specialize fmt::formatter<>() for crimson types - ceph/ceph@3fd91d7e6d9 crimson/os/seastore: drop compile-time fmt validation
2023-09-09pkgbuild: rm ceph-17.2.4.-tox-cephadm-rm.patchBazaah
Underlying issue found in f5af709 has been fixed upstream, re-enabling test. Upstream-Ref: https://github.com/ceph/ceph/commit/b5218528d63ae87ca77229bce1635c62411959e8
2023-09-09repo: revert backport-with-fmt-version.patchBazaah
This was a temporary fix for a v17 rebuild. The upstream has fixed many, many fmt issues in the new release. Reverts: 7dfdbe1 Reverts: 34d11c3