Oh ! Thank you ! I'll try tomorrow. Is there some documentation I didn't find, or is this the kind of detail only a developper can find ? PS: A still which we can configure services via spec files for a DevOps / good Infra as Code approach. Very respectfully, -- Gilles Le mercredi 11 septembre 2024, 21:48:59 CEST Wesley Dillingham a écrit :
"ceph config set client.rgw some_config_key some_config_value"
should apply for all rgws using default naming scheme.
Respectfully,
*Wes Dillingham* LinkedIn <http://www.linkedin.com/in/wesleydillingham> wes@wesdillingham.com
On Wed, Sep 11, 2024 at 3:45â¯PM Gilles Mocellin <
gilles.mocellin@nuagelibre.org> wrote:
Hello Cephers,
In our journey to migrate to cephadm, I face a problem with RGW: We use Ceph with OpenStack, so we have to configure keystone authentification, with many rgw_keystone_* variables in /etc/ceph/ceph.conf.
It's easy with ceph-ansible, and the section in ceph.conf has always the same name, constructed from the inventory.
With cephadm, daemon names for RGW contain random characters, and change at every redeploy. As we dont't have ceph.conf anymore, the configuration should be in ceph config.
But how can we have it set once, and preserved between name changes ?
I wish I could set thoses config vars in the RGW spec file, having a good "as code" approach, but no, extra params are only for the radosgw binary.
It would also be fine if we could have defined ceph confg keys with wildcards, but no.
How do you handle rados GW config, with cephadm and ceph config ?
-- Gilles
_______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io