| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
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
|
|
The changes within are now included in the upstream, and are no longer
needed
Upstream-ref: https://github.com/ceph/ceph/pull/50438
|
|
No longer applies to the upstream
|
|
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
|
|
Underlying issue found in f5af709 has been fixed upstream, re-enabling
test.
Upstream-Ref: https://github.com/ceph/ceph/commit/b5218528d63ae87ca77229bce1635c62411959e8
|
|
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
|
|
As the check_generated.sh test now depends on xmlstarlet, and
`hostname` is used a bunch.
|
|
required by the upstream now
|
|
Mostly updating the pkgname array to reflect the refactoring done on
packaging, and a slight change in field ordering to move pkgdesc higher
in the file
|
|
Improve formatting, and breakup into groups (system and python,
currently), so as to escape the giant word soup that currently exists.
|
|
These are virtual (dependency only) packages that serve a couple
purposes:
1. Backwards compatibility with the existing Archlinux ceph packages.
That is:
- ceph-libs: all non-binary packages
- ceph-mgr: (same as before / not virtual)
- ceph: all binary packages
2. Stable targets for certain functionality, namely cluster components
and the `ceph` CLI utility which is used for most interactions with
a cluster.
- ceph-libs
- ceph-cluster
- ceph-cli
- ceph
|
|
These are mostly used by the upstream development team for interacting
with various internals of the cluster and live tests.
However, the impetus for this entire patchset also lurks: java-cephfs.
A package that requires we pull in the entire java runtime, likely for a
package absolutely no one uses. Good riddance.
- ceph-tools
- ceph-test
- java-cephfs
|
|
These are a couple useful utilities for interfacing with ceph, of which
ceph-volume is likely the most important, as is it responsible for
provisioning devices for use as OSDs.
cephadm is an honorable mention, being a 9k line python file used in
managing clusters... if you like the idea of having 9k lines of python
sitting between you and your entire storage backplane.
(I do not)
- ceph-volume
- cephfs-shell
- cephfs-top
- ceph-cephadm
|
|
These comprise the daemons and associated tooling that form the cluster
or "backend" of a ceph deployment.
Notably, they have a dependencies on both the core libs, python libs
_and_ librgw (a client), as despite being a backend or server component;
ceph-rgw is _actually_ a client of ceph (and librgw specifically), that
just so happens to run as a daemon -- providing object storage.
- ceph-base
- ceph-mon
- ceph-mgr
- ceph-osd
- ceph-mds
- ceph-rgw
|
|
These are python bindings to the underlying C/C++ libs, and are used for
most of the ancillary CLI tooling ceph provides, including as support
tooling for cluster components.
- python-ceph-common
- python-rados
- python-rbd
- python-cephfs
- python-rgw
|