Hi,
Please note that there are cases where the use of ceph.conf inside a
container is justified. For example, I was unable to set monitor's
mon_rocksdb_options by any means except for providing them in monitor's own
ceph.conf within the container, all other attempts to pass this settings
were igno
Le 23/11/2023 à 15:35:25+0100, Michel Jouvin a écrit
Hi,
>
> You should never edit any file in the containers, cephadm takes care of it.
> Most of the parameters described in the doc you mentioned are better managed
> with "ceph config" command in the Ceph configuration database. If you want
> t
>>>
>>> Should I modify the ceph.conf (vi/emacs) directly ?
>>
>> vi is never the answer.
>
> WTF ? You break my dream ;-) ;-)
Let line editors die.
>>
> You're right.
>
> Currently I'm testing
>
> 17.2.7 quincy.
>
> So in my daily life how I would know if I should use ceph config or
>
Le 23/11/2023 à 09:32:49-0500, Anthony D'Atri a écrit
>
Hi,
Thanks for your answer.
>
> > to change something in the /etc/ceph/ceph.conf.
>
> Central config was introduced with Mimic. Since both central config and
> ceph.conf work and are supported, explicitly mentioning both in the docs
Hi Albert,
You should never edit any file in the containers, cephadm takes care of
it. Most of the parameters described in the doc you mentioned are better
managed with "ceph config" command in the Ceph configuration database.
If you want to run the ceph commnand on a Ceph machine outside a
c
> to change something in the /etc/ceph/ceph.conf.
Central config was introduced with Mimic. Since both central config and
ceph.conf work and are supported, explicitly mentioning both in the docs every
time is a lot of work (and awkward). One day we’ll sort out an effective means
to generali
