> > In my case it will be used to "adopt" the services, but after that what is > its intended usage? The "orchestrator" should be used to add/remove new hosts > and to upgrade the cluster.
Cephadm *is* the orchestrator. The nomenclature may seem misleading. There’s part that runs on each node as well as a Manager module, and CLI commands. > > I'm asking this question because my upgrade path consists in multiple > consecutive upgrades and I see that for the latest version of Quincy (17.2.9) > and for newer Ceph releases there is no cephadm "package" for el8 Check the compatibility matrix in the docs. > (my cluster is 95% Rocky Linux 8). EL8 in general has been deprecated for a couple of years. Toolchain and infrastructure limitations limit the ability to support older OSes indefinitely. That package and container strategies are still both supported complicates this. > I think that for the adoption and the (concurrent?) update to Quincy the > latest provided cephadm package for el8 (cephadm-17.2.7.el8) should be > adequate (right?), I’ll have to defer to others on that. I’ve BCCd the question to the upgrade lead. > but what happens when I'll upgrade the cluster to squid/tentacle? There are > no cephadm packages for that releases for EL8... All roads lead to EL9. A typical strategy is to land on a Ceph release supported by both the current and next major OS releases, update the OS, then proceed to the desired Ceph release. Ceph upgrades themselves mostly become trivial once you’re containerized. _______________________________________________ ceph-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
