Age | Commit message (Collapse) | Author |
|
|
|
note this is a bit more complicated than the normal use-patch commit, as
part of the changes in fmt-formatter-const.patch were previously made in
fmt10-fixes.patch.
We remove those from fmt10-fixes, ensure the patch _we_ produce uses
const (...oops) and fixup file hashes
|
|
fmt11 has moved the definition of FMT_VERSION from core.h to base.h, so
we adjust the cmake function the upstream uses.
This isn't a patch because the next major version completely changes how
they look up fmt (and a lot of other things)
References: https://github.com/fmtlib/fmt/releases/tag/11.0.0
|
|
|
|
|
|
|
|
Its somewhat unclear how exactly ceph is licensed overall, and I think
my choice of licenses is not *wrong*, but may be incomplete.
References: https://gitlab.archlinux.org/archlinux/rfcs/-/blob/master/rfcs/0016-spdx-license-identifiers.rst
References: https://github.com/ceph/ceph/blob/v18.2.4/COPYING-LGPL3
References: https://github.com/ceph/ceph/blob/v18.2.4/COPYING-LGPL2.1
References: https://github.com/ceph/ceph/blob/v18.2.4/COPYING-GPL2
|
|
New systemd unit file for the 'ceph-exporter' daemon. There is
seemingly no official documentation for this service but I think its an
inhouse prometheus exporter that runs per node... though unclear if
'node' means 'osd' or 'mon' or something else.
References: https://github.com/ceph/ceph/tree/v18.2.4/src/exporter
|
|
This is seemingly something to do with cephadm and (Dell?) hardware
metrics using the RedFishAPI... api. Apparently it was split out because
the upstream 'needed' it in v18 but the rest of the changes around it
from v19 weren't going to be backported.
Seems fairly worthless for ArchLinux but who can say.
References: https://github.com/ceph/ceph/commit/e1630fb8fcfa4460306b5e506c6a436f68c505a8
|
|
Upstream-ref: https://github.com/ceph/ceph/commit/33d8befcabe3e60d9ccf6e4fdc2598c4db22934b
|
|
Upstream-ref: https://github.com/ceph/ceph/commit/50cdc0b66ce87888f1e634ed4323d91bd7273dcb
|
|
Since 14aff06 we now completely disable mypy, so this patch is irrelevant
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Basically, we add the initialization for the mgr's test suite to a
location that *all* mgr module test suites include in their PYTHONPATH
I'm not sure why this worked before, when it stopped exactly, and what
changed to make it stop. Yay python.
This shouldn't be copied into the CMAKE_INSTALL_DIR, but we should
double check the built packages to be 100% sure.
|
|
This doesn't work. Or rather it does, but badly and for reasons I didn't
understand.
To set the stage.
1. All mgr modules in src/pybind/mgr/*/module.py import a 'mgr_module'
2. This module is located at src/pybind/mgr_module.py
3. It imports a module, 'ceph_module' that **does not exist.**
I didn't understand how this could work, as the file even remotely
similiar is src/pybind/mgr/ceph_module.pyi -- note the 'i'. This is what
is called a "python interface file" and basically isn't something the
python runtime is aware of. It's only use is by static code checkers
like mypy (and presumably the IDEs of people that work in this code).
I, naively assumed that somehow previous python versions had mistaken
this file for a real module hence the previous patch, where I just
define the various symbols referenced from other modules.
This isn't the case. Instead, the C++ mgr daemon _at runtime_ injects
what is effectively a bridge module into the C++ defined ceph data
structures.
This, obviously doesn't work during testing, but the upstream does have
some interesting machinery in src/pybind/mgr/tests/__init__.py, though I
don't understand how it would propagate to other test suites, and very
clearly it hasn't worked for at least since 18.2.0 for our builds.
A future commit will properly fix this issue
|
|
We use --file-links to hint to python that it should consider more
locations for package lookups.
Could be useful if python-xmlsec ever rears its ugly head again
|
|
|
|
|
|
|
|
|
|
For our internal ceph fork of python-bcrypt
|
|
So that we can introduce non ceph patches in future commits
|
|
|
|
|
|
and remove the now unneeded py deps:
- python-pyjwt
- python-cryptography
|
|
Dropped to AUR and I believe unneeded?
|
|
|
|
|
|
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
|
|
|
|
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.
|
|
The build is in a good enough spot now that the extra verbosity is
unneeded for most operations.
|
|
|
|
Minor updates to the installed files for:
- ceph-common
- librbd
- librgw
- ceph-cephadm
|
|
- 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/
|
|
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.
|
|
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
|
|
Was switched to default disabled, reenabling it here for our builds.
Upstream-Ref: https://github.com/ceph/ceph/commit/90662cad562fffbdeac33f3b79eac6a02eff8c2a
|
|
|
|
|
|
|
|
mostly fixes to line offsets, but there was one real if small change to
a variable init.
|
|
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
|
|
same patch as before, but context needs updating to apply correctly
|