Feature #50500
closedStart to build packages for Debian 11?
0%
Description
Debian 11 is in late stages of development (hard freeze for the last few weeks), with release expected in the new few months.
I usually start giving upcoming Debian releases some attention around this time in the release cycle, and whilst bullseye packages Ceph Nautilus, I'm already using Ocotopus on my test ceph cluster, so it would be nice to be able to use:
deb http://download.ceph.com/debian-pacific bullseye main
I've not build Ceph from source before, so I'll check if any modifications are need for the documented steps for building Debian packages at https://docs.ceph.com/en/latest/install/build-ceph/.
Tim.
Updated by Tim Small almost 3 years ago
Changes needed:
Add:
[Service]
ProtectClock=false
to: /etc/systemd/system/ceph-osd
.service.d/override.conf@ (see #50381 ) and remove cyphon
and dh-systemd
from the Build-Depends:
section of debian/control
Updated by Tim Small almost 3 years ago
Tentative release date for Debian 11 is 31-July-2021 https://lists.debian.org/debian-release/2021/06/msg00199.html
Updated by Tim Small over 2 years ago
Officially announced Debian 11 release date is 2021-Aug-14 https://wiki.debian.org/DebianBullseye
Updated by Aggelos Avgerinos over 2 years ago
Debian Bullseye has been officially released on 14/8/2021. Will there be a pacific build for Bullseye soon?
Updated by Xen Gi over 2 years ago
Same here also for pacific. I'm running a v16 cluster using cephadm on debian 11 but my debian 11 clients can only use v14 from the debian repos.
Are there any plans to change this? Does someone know where one can find the ceph roadmap?
Updated by Greg Farnum over 2 years ago
We'll be discussing in this week's Ceph Leadership Team meeting.
We as a project don't have much process around switching which releases we build for, so this is pretty ad-hoc right now; sorry for the lack of clarity.
Updated by Xen Gi over 2 years ago
Thx for the reply. Please keep us updated about the results.
Updated by Greg Farnum over 2 years ago
Our upstream lab admin/release engineer is out on vacation right now so we're expecting this to get done when he returns next week.
Updated by Thomas Goirand over 2 years ago
Hi,
It'd be nice if you guys, from upstream Ceph, decided to just collaborate with Debian in order to build Ceph packages. We're very much open to help, and it would be a way more productive than doing this on your own. FYI, our packaging is done over here:
https://salsa.debian.org/ceph-team/ceph
Just get in touch on IRC (I'm zigo on many channel, noticeably #debian-openstack), or email (you can send me a mail to zigo at debian dot org) and we can grant you access to the Gitlab project, for example. Note that I'm also on the #ceph channel on OFTC...
Cheers,
Thomas Goirand (zigo)
Updated by Jonas A over 2 years ago
Hi,
The ProxMox project already builds Ceph Pacific packages for Debian Bullseye!
I installed them from
deb http://download.proxmox.com/debian/ceph-pacific bullseye main
Updated by Xen Gi over 2 years ago
Good to know, but I would prefer the original source. Do they build them the same way or are there proxmox specific things baked in?
Updated by David Galloway over 2 years ago
Here's my first attempt:
The following packages have unmet dependencies: pbuilder-satisfydepends-dummy : Depends: cython which is a virtual package and is not provided by any available package Depends: dh-systemd which is a virtual package and is not provided by any available package Unable to resolve dependencies! Giving up...
Updated by Aggelos Avgerinos over 2 years ago
David Galloway wrote:
Here's my first attempt:
[...]
Yes David, python 2.x has been removed from Debian Bullseye. Now it ships only with python3.
You definitely need to build python3 only packages and remove all python2 dependencies (e.g. instead of depending on cython it must depend on cython3 etc.)
Updated by David Galloway over 2 years ago
Updated by David Galloway over 2 years ago
Tim Small wrote:
Changes needed:
Add:
[...]
to:
/etc/systemd/system/ceph-osd
.service.d/override.conf@ (see #50381 ) and removecyphon
anddh-systemd
from theBuild-Depends:
section ofdebian/control
Any chance you filed a Pull Request for these changes?
Updated by Tim Small over 2 years ago
David Galloway wrote:
Tim Small wrote:
remove
cyphon
anddh-systemd
from theBuild-Depends:
section ofdebian/control
Any chance you filed a Pull Request for these changes?
I didn't because, I didn't have a huge amount of confidence in the changes, and also I didn't know how you manage different debian build files across different releases of Debian (and derivatives). Also the change was literally just removing those two lines as described:
tim@cephbuild:~/ceph$ git diff diff --git a/debian/control b/debian/control index 4ca0caa76d..82eb26de13 100644 --- a/debian/control +++ b/debian/control @@ -12,13 +12,13 @@ Build-Depends: automake, cmake (>= 3.10.2), cpio, cryptsetup-bin | cryptsetup, - cython, +# Tim cython, cython3, debhelper (>= 9), default-jdk, dh-exec, dh-python, - dh-systemd, +# Tim dh-systemd, # Jaeger flex, git, gperf,
The resulting binaries appeared to mostly work, but I couldn't get the dashboard working correctly (I think). I also saw an issue with a monitor failing on one machine, but I didn't manage to debug that fully, and it was just once machine so it could have been a configuration or hardware issue with that box. Since this was about 6 months ago, and soon after Pacific was released I also thought it possible that these issues were general ones rather than Debian 11.
I'm happy to run tests etc. if that would be helpful.
HTH,
Tim.
Updated by David Galloway over 2 years ago
- Status changed from New to In Progress
https://github.com/ceph/ceph/pull/43134 for the debhelper change. Will need to backport that to the pacific branch.
https://github.com/ceph/ceph/pull/43131 is a backport to remove cython
We're releasing the next point release of Pacific soon. No guarantees these will make it in unfortunately as our QA was almost done.
Updated by Tim Small over 2 years ago
Thanks for the work on this - I'll give the packages a spin later today...
Updated by Tim Small over 2 years ago
Whilst I don't use all components and features (just rbd and dashboard, with ansible deployment), this is working well for me.
Happy to close this bug now if you are in agreement?
Thanks!
Tim.
Updated by David Galloway over 2 years ago
- Status changed from In Progress to Resolved
Updated by Nathan Revo almost 2 years ago
Xen Gi wrote:
Looks good thx everyone!
This did not seem to include arm64. the packages are there but the Packages manifest is incomplete.