Am 16.12.21 um 16:56 schrieb Florian Haas:
So for a 15.2.5 cluster that's being converted to Cephadm, Cephadm
should use quay.io from the get-go. And it does, but only for "cephadm
adopt".
It does because you specify the container image on the command line in
the adoption process.
When you do an "ceph orch upgrade --image
quay.io/ceph/ceph:v15.2.15" before deploying new RGWs and MDSs you
set the new default image for cephadm. No "real" upgrade will be
performered as the adopted containers already are running on this
image.
Yes, that's an idea. But it's also *very* counterintuitive, don't you
agree?
I totally agree. But containers and automation are the future. And who
could have thought about that the default container image registry would
change or that Docker hub turns into an unusable repo. Not to become
sarcastic here…
Regards
--
Robert Sander
Heinlein Consulting GmbH
Schwedter Str. 8/9b, 10119 Berlin
http://www.heinlein-support.de
Tel: 030 / 405051-43
Fax: 030 / 405051-19
Zwangsangaben lt. §35a GmbHG:
HRB 220009 B / Amtsgericht Berlin-Charlottenburg,
Geschäftsführer: Peer Heinlein -- Sitz: Berlin
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
