Right, if you want to bootstrap a cephadm cluster, you don't need to
worry too much about the package versions on the host. Although we do
recommend to keep them somewhat aligned. But there's also an option
for the cephadm bootstrap command:
--allow-mismatched-release
allow bootstrap of ceph that doesn't match
this version of cephadm
I used that many times on openSUSE hosts where the latest available
version was Pacific (there are packages available again with Reef and
Squid from openSUSE Leap 16, Tumbleweed probably too, haven't
checked). Last week I also bootstrapped a Squid cluster like that on a
Debian Trixie where the host package versions are 18.2.7.
Zitat von Robert Sander via ceph-users <[email protected]>:
Am 18.02.26 um 5:53 PM schrieb Albert Shih via ceph-users:
2/ Install a Debian 13 and use the Debian ceph pkg.
This is the way.
The client code does not need to match the cluster version.
I usually install ceph-common from the distribution.
Just make sure you have a cephadm binary matching the desired Ceph
version before bootstrapping the cluster.
Regards
--
Robert Sander
Linux Consultant
Heinlein Consulting GmbH
Schwedter Str. 8/9b, 10119 Berlin
https://www.heinlein-support.de
Tel: +49 30 405051 - 0
Fax: +49 30 405051 - 19
Amtsgericht Berlin-Charlottenburg - HRB 220009 B
Geschäftsführer: Peer Heinlein - Sitz: Berlin
_______________________________________________
ceph-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
ceph-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
