Am 5/16/25 um 08:50 schrieb Florent Carli:
So, for now, I’m stuck handling all of this myself. You can take a look at what I’ve done here if you're interested: https://github.com/seapath/ansible/blob/main/roles/cephadm/tasks/main.yml My playbook deals with all those use cases based on my ansible inventory: - boostrapping a new cluster from scratch - adding a missing node (monitor) in an already boostrapped cluster - adding missing mgrs - zapping and adding missing OSDs (based on pre-provisionned LVM volumes) - of course: doing nothing if everything is already in place But it's such a pain to maintain.
It looks like you are trying to do things yourself that the orchestrator already does.
Make yourself familiar with the service specification of the orchestrator and in the case of OSDs with the drivegroup specification.
In the "light" YAML specifications you showed the orchestrator has been told to deploy 3 MONs and 3 MGRs on arbirtrary nodes. You can change that to use e.g. labels on hosts and with them declare where you want these services to run.
Same with OSDs where you can specify how the OSDs should be deployed (size and type of disk for example).
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 -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-le...@ceph.io
