With Ceph Quincy, the "ceph" package does not include ceph-volume anymore
Hi all, Until Ceph Pacific, installing just the "ceph" package was enough to get everything needed to deploy Ceph. However, with Quincy, ceph-volume was split off into its own package, and it is not automatically installed anymore. Here we can see it is not listed as a dependency: $ rpm -q --requires ceph binutils ceph-mds = 2:17.2.5-0.el8 ceph-mgr = 2:17.2.5-0.el8 ceph-mon = 2:17.2.5-0.el8 ceph-osd = 2:17.2.5-0.el8 rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(PayloadIsXz) <= 5.2-1 systemd Should I file a bug for this? Best regards, Geert Kloosterman
Den tors 23 mars 2023 kl 15:18 skrev Geert Kloosterman <gkloosterman@nvidia.com>:
Hi all, Until Ceph Pacific, installing just the "ceph" package was enough to get everything needed to deploy Ceph. However, with Quincy, ceph-volume was split off into its own package, and it is not automatically installed anymore.
Should I file a bug for this?
I would be surprised if I installed "ceph-osd" and didn't get ceph-volume, but I never thought about if "only" installing "ceph" did or did not provide it. (from one of the remaining non-container ceph users) -- May the most significant bit of your life be positive.
Until Ceph Pacific, installing just the "ceph" package was enough to get everything needed to deploy Ceph. However, with Quincy, ceph-volume was split off into its own package, and it is not automatically installed anymore.
Should I file a bug for this?
I would be surprised if I installed "ceph-osd" and didn't get ceph-volume, but I never thought about if "only" installing "ceph" did or did not provide it.
(from one of the remaining non-container ceph users)
Ideally you want your orchestrator to supply volumes to the containers. I guess ceph-adm is slowly evolving to this concept. And on newer distributions I have noticed the feature where you type a non-existing command, the os if offering you to install it. Looks to me as intended.
I would be surprised if I installed "ceph-osd" and didn't get ceph-volume, but I never thought about if "only" installing "ceph" did or did not provide it.
I — perhaps naively - think of `ceph` as just the CLI, usually installing `ceph-common` too.
(from one of the remaining non-container ceph users)
More out there than we realize
Ideally you want your orchestrator to supply volumes to the containers. I guess ceph-adm is slowly evolving to this concept. And on newer distributions I have noticed the feature where you type a non-existing command, the os if offering you to install it. Looks to me as intended.
Ew, David! I would disable that if I came across it. Too much risk of: * Divergent versions * Getting the package from the wrong repository * Filesystem fillage
On Fri, 2023-03-24 at 08:43 +0100, Janne Johansson wrote:
Den tors 23 mars 2023 kl 15:18 skrev Geert Kloosterman <gkloosterman@nvidia.com>:
Hi all, Until Ceph Pacific, installing just the "ceph" package was enough to get everything needed to deploy Ceph. However, with Quincy, ceph-volume was split off into its own package, and it is not automatically installed anymore.
Should I file a bug for this?
I would be surprised if I installed "ceph-osd" and didn't get ceph-volume, but I never thought about if "only" installing "ceph" did or did not provide it.
In the following commit "ceph-volume" was split from "ceph-osd" https://github.com/ceph/ceph/commit/8e0e9ef382c5749954eb416107e4a7d22f92d41c There is no dependency from "ceph-osd" on "ceph-volume". Adding this dependency to "ceph-osd" would prevent your surprise and also indirectly solve things for the "ceph" package.
participants (4)
-
Anthony D'Atri
-
Geert Kloosterman
-
Janne Johansson
-
Marc