3 Nov
2020
3 Nov
'20
10:11 p.m.
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.
thanks,
Wyllys Ingersoll
3 Nov
3 Nov
10:27 p.m.
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(a)ceph.io
> To unsubscribe send an email to dev-leave(a)ceph.io
>
11:44 p.m.
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(a)42on.com>
Sent: Tuesday, November 3, 2020 10:27 AM
To: Wyll Ingersoll <wyllys.ingersoll(a)keepertech.com>om>; dev <dev(a)ceph.io>
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(a)ceph.io
To unsubscribe send an email to dev-leave(a)ceph.io
5 Nov
5 Nov
12:29 a.m.
On Tue, Nov 3, 2020 at 9:44 AM Wyll Ingersoll
<wyllys.ingersoll(a)keepertech.com> wrote:
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.
That's a good point. Could you open a bug for this at
https://tracker.ceph.com/ ?
1:18 a.m.
Sure, under what project - rgw or mon (or something else)?
________________________________
From: Ken Dreyer <kdreyer(a)redhat.com>
Sent: Wednesday, November 4, 2020 12:29 PM
To: Wyll Ingersoll <wyllys.ingersoll(a)keepertech.com>
Cc: Wido den Hollander <wido(a)42on.com>om>; dev <dev(a)ceph.io>
Subject: Re: radosgw keyring configuration parameter
On Tue, Nov 3, 2020 at 9:44 AM Wyll Ingersoll
<wyllys.ingersoll(a)keepertech.com> wrote:
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.
That's a good point. Could you open a bug for this at
https://tracker.ceph.com/ ?
3:26 a.m.
I created https://tracker.ceph.com/issues/48122 and put it in the 'rgw' project.
Bug #48122: rgw cannot find keyring after config file is minimized - rgw - Ceph
<https://tracker.ceph.com/issues/48122>
Redmine
tracker.ceph.com
________________________________
From: Wyll Ingersoll <wyllys.ingersoll(a)keepertech.com>
Sent: Wednesday, November 4, 2020 1:18 PM
To: Ken Dreyer <kdreyer(a)redhat.com>
Cc: Wido den Hollander <wido(a)42on.com>om>; dev <dev(a)ceph.io>
Subject: Re: radosgw keyring configuration parameter
Sure, under what project - rgw or mon (or something else)?
________________________________
From: Ken Dreyer <kdreyer(a)redhat.com>
Sent: Wednesday, November 4, 2020 12:29 PM
To: Wyll Ingersoll <wyllys.ingersoll(a)keepertech.com>
Cc: Wido den Hollander <wido(a)42on.com>om>; dev <dev(a)ceph.io>
Subject: Re: radosgw keyring configuration parameter
On Tue, Nov 3, 2020 at 9:44 AM Wyll Ingersoll
<wyllys.ingersoll(a)keepertech.com> wrote:
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.
That's a good point. Could you open a bug for this at
https://tracker.ceph.com/ ?
1276
days inactive
1277
days old
5 comments
3 participants
participants (3)
-
Ken Dreyer -
Wido den Hollander -
Wyll Ingersoll