23 Apr
2021
23 Apr
'21
11:35 p.m.
I'm trying to understand what and where radosgw listen ?
There is a lot of contradictory or redundant informations about that.
First about the contradictory informations for the socket.
At https://docs.ceph.com/en/pacific/radosgw/config-ref/
<https://docs.ceph.com/en/pacific/radosgw/config-ref/>, it says rgw_socket_path, but
at https://docs.ceph.com/en/pacific/man/8/radosgw/
<https://docs.ceph.com/en/pacific/man/8/radosgw/> is says 'rgw socket path'
That problem is quite common in the ceph documentation. Are both value accepted ?
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.
The description says nothing new, it just repeat the field name.
Is one of them used by the manager for communication ? I already had the problem for the
entry in the certificate used by the frontend, it used an IP coming from nowhere.
If a fcgi is used, how the manager find the endpoint ?
24 Apr
24 Apr
3:30 a.m.
On 23 Apr 2021, at 21:05, Fabrice Bacchella
<fabrice.bacchella(a)orange.fr> 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
3 May
3 May
2:47 a.m.
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(a)k0ste.ru> a écrit :
On 23 Apr 2021, at 21:05, Fabrice Bacchella
<fabrice.bacchella(a)orange.fr <mailto:fabrice.bacchella@orange.fr>> 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
1088
days inactive
1097
days old
2 comments
2 participants
participants (2)
-
Fabrice Bacchella -
Konstantin Shalygin