|
OK that makes sense.
It would have been nice if "ceph config generate-minimal-conf" would not have deleted the parameters that are still needed, or at least given a warning that they were not able to be converted or removed.
From: Wido den Hollander <wido@xxxxxxxx>
Sent: Tuesday, November 3, 2020 10:27 AM To: Wyll Ingersoll <wyllys.ingersoll@xxxxxxxxxxxxxx>; dev <dev@xxxxxxx> Subject: Re: radosgw keyring configuration parameter On 03/11/2020 16:11, Wyll Ingersoll wrote: > In Nautilus 14.2.13, we have converted to the minimized ceph.conf file > and are now storing our config in the monitors. Previously, radosgw was > getting its keyring from /etc/ceph/ceph.client.radosgw.keyring, but now > that the ceph.conf has been minimized, the keyring value was not > converted into the monitor k/v store under the radosgw client > configuration options and radosgw is looking for the keyring in > /var/lib/ceph/radosgw/ceph-radosgw.gw01/keyring instead. > > Attempting to put the keyring location into the monitor configuration > with "ceph config set ..." fails because it says the keyring value > cannot be stored in the monitor config settings. Is there a way to > store an alternate keyring location without putting it in ceph.conf? > It's easy enough to work around the issue by using a link or just > copying the keyring to the new location, but I was wondering if there is > a way to specify the keyring location in the monitor K/V storage. No. Because the client needs to authenticate prior to being able to access the K/V storage. These options will need to go into the ceph.conf Wido > > thanks, > Wyllys Ingersoll > > > _______________________________________________ > Dev mailing list -- dev@xxxxxxx > To unsubscribe send an email to dev-leave@xxxxxxx > |
_______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
