Re: Redeploy ceph orch OSDs after reboot, but don't mark as 'unmanaged'

Janek Bevendorff <janek.bevendorff@xxxxxxxxxxxxx> · Tue, 7 Nov 2023 11:48:03 +0100

Actually, ceph cephadm osd activate doesn't do what I expected it to do. 
It  seems to be looking for new OSDs to create instead of looking for 
existing OSDs to activate. Hence, it does nothing on my hosts and only 
prints 'Created no osd(s) on host XXX; already created?' So this 
wouldn't be an option either, even if I were willing to deploy the admin 
key on the OSD hosts.

On 07/11/2023 11:41, Janek Bevendorff wrote:
Hi,

We have our cluster RAM-booted, so we start from a clean slate after 
every reboot. That means I need to redeploy all OSD daemons as well. 
At the moment, I run cephadm deploy via Salt on the rebooted node, 
which brings the deployed OSDs back up, but the problem with this is 
that the deployed OSD shows up as 'unmanaged' in ceph orch ps afterwards.

I could simply skip the cephadm call and wait for the Ceph 
orchestrator to reconcile and auto-activate the disks, but that can 
take up to 15 minutes, which is unacceptable. Running ceph cephadm osd 
activate is not an option either, since I don't have the admin keyring 
deployed on the OSD hosts (I could do that, but I don't want to).

How can I manually activate the OSDs after a reboot and hand over 
control to the Ceph orchestrator afterwards? I checked the deployments 
in /var/lib/ceph/<FSID>, but the only difference I found between my 
manual cephadm deployment and what ceph orch does is that the device 
links to /dev/mapper/ceph--... instead of /dev/ceph-...

Any hints appreciated!

Janek 
Attachment:
smime.p7s

Description: S/MIME Cryptographic Signature
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx