| Age | Commit message (Collapse) | Author |
|---|
|
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
|
|
These form the core clients for ceph; rbd (block), cephfs
(filesystem), rgw (object).
- librbd
- ceph-rbd
- libcephfs
- ceph-cephfs
- librgw
|
|
These are the core / common libraries that almost everything else will
depend on at some level.
libcephsqlite is an outlier, but is also depended on by other ceph
components despite _technically_ being a RADOS client, hence its
inclusion.
- ceph-compressor
- ceph-crypto
- ceph-erasure
- ceph-common
- librados
- ceph-rados
- libcephsqlite
|
|
The true workhorse for packaging ceph, this function is responsible for
calling make install, and _ensuring all files accounted for_ -- moved or
deleted -- before yielding.
It will contain a series of `_package` invocations, one per package,
with each actual package function being a thin wrapper around:
'mv __pkg__/$pkgname/* "$pkgdir"'
|
|
These are the beginning of a refactoring of how we handle the package_*
functions.
Currently, we run `make install` once per packaging function and attempt
to delete the bits that aren't related to the package currently running.
This has several downsides, including conflicting file owners, missed
addition(al file)s in later versions and speed.
These new functions will serve as the engine for enumerating the precise
file dependencies for each package, and provide a pretty output during
the packaging process of this list.
|
|
|
|
Rebuild for boost, thrift and some python stuff
|
|
|
|
|
|
Issue: https://github.com/bazaah/aur-ceph/issues/17
Reported-by: https://aur.archlinux.org/account/UweSauter
Reported-in: https://aur.archlinux.org/pkgbase/ceph#comment-926651
|
|
|
|
|
|
|
|
|
|
|
|
Upstream appears to have removed the test
Upstream-Ref: https://github.com/ceph/ceph/commit/62121704f019f225b1df4b0c63ba2d89fe9be9ca
|
|
As this is now backported in the upstream
Upstream-Ref: https://github.com/ceph/ceph/commit/b49753e374e0ba30e61eab0b7d88abb5104e5975
Reverts: 82a7efacca33c5640103622e251755a5523e78cd
|
|
No longer needed, as the Archlinux package has fixed this issue by
reverting to an older (?) method for building rdkafka, which doesn't
contain the bug this patch worked around.
Reverts: dd2565ded777ce438f5063d6e9cc8b2fe22244e7
Reverts: d0451743748d9c381a598fb45b658c3669ee357f
References: https://github.com/archlinux/svntogit-community/commit/924fddef74a86f020ec6813291979946f6da55da
|
|
Same patch, just updated to follow upstream changes to
src/pybind/mgr/tox.ini
|
|
|
|
|
|
|
|
|
|
Backport-to: ceph-bin
Issue: https://github.com/bazaah/aur-ceph/issues/9
Closes: #9
|
|
This fixes an unfortunate issue in the upstream's provided logrotate,
and the one which `cephadm` creates during runs.
Unfortunately, logrotate throws an error if more than one rule matches a
given file, which is the case between our '.../ceph/*.log' and the
cephadm generated one: '.../ceph/cephadm.log'.
Because the file is generated we can't really complain to the maintainer
for cephadm, and we also can't change our rule because ceph may
generate any pattern matching '<cluster>-<svc>-<id>', all of which are
user / cluster specific.
Fortunately, the most recent (as of this commit) logrotate as introduced
a workaround: 'ignoreduplicates' which does what you expect. We patch
the upstream logrotate.conf to include this keyword, fixing this
issue.
See the issue for more.
References: https://github.com/logrotate/logrotate/pull/473
References: https://github.com/ceph/ceph/blob/v17.2.5/src/cephadm/cephadm#L9408
Closes: #8
Issue: https://github.com/bazaah/aur-ceph/issues/8
Reported-by: snack@aur.archlinux.org
|
|
This patch is taken directly from an (at the time of writing) open PR of
the upstream which fixes a crash in the mgr's device_metrics module when
using a later version of the python sqlite driver.
The upstream docs for libcephsqlite specifically call out that file
based temp tables are not supported. See:
https://docs.ceph.com/en/quincy/rados/api/libcephsqlite/#temporary-tables
Closes: #5
Issue: https://github.com/bazaah/aur-ceph/issues/5
Upstream-Ref: https://github.com/ceph/ceph/pull/48449
|
|
3 is skipped to accommodate a screwup in the sister ceph-bin package
|
|
to be more in line with the new additions
|
|
This file is inspired by the upstream's 'sudoers.d/ceph-smartctl' file,
however, unlike their one; isn't a security threat if anyone nasty ever
elevates to the 'ceph' user.
We use the latest and greatest in sudo technology: regexes. Sudo is only
4 decades late to the party, and we welcome them in with open arms,
though unfortunately all the pizza has been eaten, along with most of
the soda drinks, and most of the party's participants are tired, like
this metaphor.
|
|
|
|
|
|
|
|
Upstream no longer uses deprecated headers (... here).
|
|
This was fixed a while back, and is not needed anymore.
Upstream-Ref: https://github.com/ceph/ceph/commit/42b41f897d2a0a7673ad7fb4b6d2a3426f9609c1
|
|
archlinux no longer uses python 3.9
|
|
Since 35b4e84 we no longer need to play funny games with the upstream
around zstd.
|
|
|