ceph.conf still *works*, though, for those with existing systems built to manage it?
While the centralized config is very handy, I’d love to find a way to tie it into external
revision control, so that settings could continue to be managed in eg. git and applied by
automation.
On Apr 30, 2020, at 5:43 AM, Gencer W. Genç
<gencer(a)gencgiyen.com> wrote:
Hi JC,
Thank you for the reply.
I believe global will override all (take precedence of) "mon.{id}" settings
right?
Thanks,
Gencer.
On 30.04.2020 02:34:18, JC Lopez <jelopez(a)redhat.com> wrote:
Hi,
later version of Ceph do not rely on the configuration file anymore but on a MON
centralized configuration which explain the lack of the config push function.
Set your option in the MON config DB and it will be picked up by the daemon or the client
upon connection
ceph config mon.{id} mon_allow_pool_delete true
ceph config client.{id} parameter value
ceph config global parameter value
Regards
JC
On Apr 29, 2020, at 16:06, Gencer W. Genç wrote:
Hi,
===
NOTE: I do not see my thread in ceph-list for some reason. I don't know if list
received my question or not. So, sorry if this is duplicate.
===
I just deployed a new cluster with cephadm instead of ceph-deploy. In tyhe past, If i
change ceph.conf for tweaking, i was able to copy them and apply to all servers. But i
cannot find this on new cephadm tool. I did few changes on ceph.conf but ceph is unaware
of those changes. How can i apply them? I've used it with docker. Thanks, Gencer.
_______________________________________________
ceph-users mailing list -- ceph-users(a)ceph.io
To unsubscribe send an email to ceph-users-leave(a)ceph.io
_______________________________________________
ceph-users mailing list -- ceph-users(a)ceph.io
To unsubscribe send an email to ceph-users-leave(a)ceph.io