Le 19/11/2025 à 09:39:00-0500, Anthony D'Atri a écrit
Hi,
I don't need the ceph.conf for ceph himself. I «need» the ceph.conf so I can launch
ceph fsid
on any node.
I suspect that the requirement for this to be in ceph.conf may be an artifact of the days when vanity cluster names were intended for multiple logical clusters to run on the same node. One might assert today that a client should be able to get this from the mons, I would suggest entering a tracker ticket to that effect.
Ok, but just to be clear I got only [global] fsid = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX mon_host = [v2:a.b.c.10:3300/0,v1:a.b.c.10:6789/0] [v2:a.b.c.11:3300/0,v1:a.b.c.11:6789/0] [v2:a.b.c.12:3300/0,v1:a.b.c.12:6789/0] [v2:a.b.c. 13:3300/0,v1:a.b.c.13:6789/0] [v2:a.b.c.14:3300/0,v1:a.b.c.14:6789/0] [v2:a.b.c.15:3300/0,v1:a.b.c.15:6789/0] [v2:a.b.c.16:3300/0,v1:a.b.c.16:6789/0] [v2:a.b.c.17:3300/0,v1:a.b.c.17:6789/0] [v2:a.b.c.18:3300/0,v1:a.b.c.18:6789/0]
chown -R ceph:ceph /var/lib/ceph/FSID/crash/posted
so with the hability to launch ceph fsid on any node I can get that info through a «facter» in puppet so I can add this line in the crontab.
I have to ask: why not use a wildcard?
Because this is just one example of the using of fsid in puppet. But you'r right I can use a wildcard. Regards -- Albert SHIH 🦫 🐸 France Heure locale/Local time: mer. 19 nov. 2025 15:54:44 CET