Re: How radosgw works ?

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

 



I'm still trying to wrap my head around the radosgw when using fastcgi on a socket file.

First the documentation is very poor. The fcgi usage is documented in the man page, but the http frontends have a dedicated section. Why ?

Next, I don't understand if they are exclusive or not. I trying to define the configuration setting, a command line argument, with or without rgw_frontends defined.

Nothing changes. And I don't see any indications in the logs about even trying. strace does not provides any help. So whatever I do, radosgw never try to use socket fcgi. Why ?

I'm running on Centos 8, with rpm from ceph: ceph-radosgw-16.2.1-0.el8.x86_64 

> Le 24 avr. 2021 à 00:00, Konstantin Shalygin <k0ste@xxxxxxxx> a écrit :
> 
> 
> 
>> On 23 Apr 2021, at 21:05, Fabrice Bacchella <fabrice.bacchella@xxxxxxxxx <mailto:fabrice.bacchella@xxxxxxxxx>> wrote:
>> 
>> Next about some naming, or binding IP. Where it's defined, and how ?
>> You have:
>> rgw_frontends = "beast ssl_endpoint=0.0.0.0:443 port=443 ..."
>> rgw_host =
>> rgw_port = 
>> rgw_dns_name =
>> 
>> That's a lot of redundancy, or contradictory informations. What is the purpose of each one ? What is the difference between
>> rgw_frontends = ".. port = ..."
>> and
>> rgw_port = 
>> 
>> ?
>> Or rgw_host and rgw_dns_name. What is the difference ?
>> 
>> The documentation provides no help at all:
>> rgw_dns_name
>> Description: The DNS name of the served domain. See also the hostnames setting within regions.
> 
> rgw_port is for fastcgi, default is unset
> rgw_frontends is civetweb or beast, for example you can configure civetweb like this:
> 
> Listen on 443 securely with cert, redirect requests from 80 to 443:
> rgw frontends = civetweb port=0.0.0.0:80r+443s ssl_certificate=/etc/pki/tls/private/example.com.pem ssl_cipher_list=ECDHE-ECDSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384
> 
> rgw_dns_name is your endpoint. For example you run 10 redundant RGW's: for each you need to define the same values of:
> rgw_zone = default
> rgw_zonegroup = default
> rgw_realm = default
> 
> For example your cert is FQDN: *.example.com <http://example.com/> and your endpoint service is: swift.example.com <http://swift.example.com/>, that
> rgw_dns_name = swift.example.com <http://swift.example.com/>
> 
> Civetweb frontend is documented all possible options [1], for Beast should be the same
> 
> 
> [1] http://civetweb.github.io/civetweb/UserManual.html <http://civetweb.github.io/civetweb/UserManual.html>
> 
> Good luck,
> k

_______________________________________________
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