Re: [RGW][cephadm] How to configure RGW as code and independantely of daemon names ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



more a OpenStack question, but; 
may I ask why you define many rgw_keystone_ vars? 
I only set like 3 or 4 keys when I remember right. keys for cinder and Nova and one to control bucket operations. 

On 11 September 2024 20:00:56 UTC, Gilles Mocellin <gilles.mocellin@xxxxxxxxxxxxxx> wrote:
>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@xxxxxxxxxxxxxxxxx
>> 
>> 
>> 
>> 
>> On Wed, Sep 11, 2024 at 3:45 PM Gilles Mocellin <
>> 
>> gilles.mocellin@xxxxxxxxxxxxxx> 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@xxxxxxx
>> > To unsubscribe send an email to ceph-users-leave@xxxxxxx
>
>
>
>_______________________________________________
>ceph-users mailing list -- ceph-users@xxxxxxx
>To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx




[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux