Package Details: ceph-volume 19.2.1-2

Git Clone URL: https://aur.archlinux.org/ceph.git (read-only, click to copy)
Package Base: ceph
Description: Ceph Storage utility for preparing block devices for use as OSDs
Upstream URL: https://ceph.com/
Licenses: GPL-2.0-or-later OR LGPL-2.1-or-later OR LGPL-3.0-or-later
Submitter: foxxx0
Maintainer: pbazaah
Last Packager: pbazaah
Votes: 7
Popularity: 0.051259
First Submitted: 2022-08-08 09:09 (UTC)
Last Updated: 2025-02-18 14:41 (UTC)

Required by (2)

Sources (34)

Pinned Comments

pbazaah commented on 2022-10-05 13:03 (UTC) (edited on 2022-10-05 13:03 (UTC) by pbazaah)

For future commenters:

TLDR:

https://aur.archlinux.org/pkgbase/ceph | From source build (slow)

https://aur.archlinux.org/pkgbase/ceph-bin | Pre-built binaries (fast)

Unlike the original community version, this repo builds ceph from source. Ceph is a large, complicated project so this takes several hours on a good build server.

To get a similar experience to how community/ceph worked (pre-built binaries) use ceph-bin instead.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 .. 13 Next › Last »

insanemal commented on 2025-02-18 01:39 (UTC)

Just a heads up but the fix for entry_points from importlib no longer works.

The try: except: block doesn't throw an import error it throws an Attribute error and isn't caught at all by the try: except: block

I had to basically just cut it out and go with the 'except' code path always, to get my cluster back up as it killed ceph-volume.

Not sure if this is a 19.x change or something added due to python3.13 and/or the importlib deprecation, or a combination of all of the above.

Basically anywhere there is a test for importlib behavior it should be removed and just the exception path taken on Arch anyway.

Thanks for your great work!

pbazaah commented on 2025-02-13 18:51 (UTC)

v19.2.1-1 has been released.

Important caveats first:

  • I recommend you disable the restful mgr module before upgrading, and/or if you require it, add ceph packages to HoldPkg for the moment.

You can do this via ceph mgr module disable restful.

This module has become another casualty in the pyo3 mess, which still has no resolution.

  • Avoid using the new MDS quiesce functionality

I am very certain there are multiple bugs hiding in this new set of functionality. Fair warning.

This is, overall, a smaller release; bringing improvements mostly for SSD/NVME OSDs. It also brings a tech preview of the next generation OSDs (code-named Crimson) that are optimized for SSD / NVME / PMEM hardware, which may be of interest.

There is some minor movement upstream in fixing the dashboard / pyo3 related woes, but nothing yet merged to the development trunk, so dashboard (and now, restful) modules remain broken.

Links:

pbazaah commented on 2025-02-08 18:49 (UTC)

I am currently working on the update to v19.2.1 (https://ceph.io/en/news/blog/2025/v19-2-1-squid-released/) which should void the need for a 6th pkgrel on v18.

brody commented on 2025-02-08 15:49 (UTC)

Since the last boost update the package ist not buildable anymore.

make[2]: Leaving directory '/build/ceph/src/ceph-18.2.4/src/pmdk/src/librpmem'
make[1]: Leaving directory '/build/ceph/src/ceph-18.2.4/src/pmdk/src'
ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in build().
    Aborting...
==> ERROR: Build failed, check /home/db1000/chroot/db1000/build

pbazaah commented on 2025-01-20 11:43 (UTC)

@brody Ceph doesn't do X.3.0 versions.

See: https://docs.ceph.com/en/latest/releases/general/

Once the initial stable release is made (x.2.0), there are semi-regular bug-fix point releases with bug fixes and (occasionally) feature backports. Bug fixes are accumulated and included in the next point release.

(https://github.com/ceph/ceph/compare/v19.2.0..v19.3.0)

I have intentionally not upgraded to v19 yet because there are serious issues that I'm waiting for 19.2.1 to fix

pbazaah commented on 2025-01-05 15:12 (UTC)

v18.2.4-5 has been released.

Bringing a rebuild for python 3.13. I spent more time than normal making sure the src/pybind tests pass (excluding openapi definitions) so hopefully I caught everything, but there maybe issues still.

pbazaah commented on 2024-12-21 14:05 (UTC)

I will continue at least through 2025.

Hopefully Archlinux doesn't push py3.13 before the new year, because I will not be around do a pkgrel for that.

insanemal commented on 2024-12-21 03:34 (UTC)

I was just seeing if you were continuing the maintenance on this? I do not mean to pressure you just to ask. Thanks for your work

pbazaah commented on 2024-05-25 16:44 (UTC) (edited on 2024-05-25 16:45 (UTC) by pbazaah)

v18.2.2-3 has been released.

Bringing small fixes to the ceph-volume utility, and usage of python 3.12

The dashboard (and cephadm) functionality remain broken, though there was been some minor movement in PyO3 towards supporting subinterpreters. See {1} for more.

{1}: https://github.com/PyO3/pyo3/issues/3451#issuecomment-2096539900

pbazaah commented on 2024-03-23 11:18 (UTC)

v18.2.2-1 has been released.

The most important aspect of this release is the work done to bypass this mgr issues described in {1}.

With this release we reenable the mgr/dashboard module, and prevent the catastrophic failures from python-bcrypt upgrading to >=0.17 of pyo3.

Unfortunately, the mgr/orch (used by and for cephadm) module remains broken, as I cannot safely patch python-cryptography in a similar fashion to python-bcrypt, as they actually store py objects in global state, making them actually UB in subinterpreters.

One side note for anyone building ceph: the check() is broken for mgr tests at the moment. I'll fix this in a future pkgrel

{1}: https://github.com/bazaah/aur-ceph/issues/20

« First ‹ Previous 1 2 3 4 5 6 7 .. 13 Next › Last »