> On 23 Apr 2021, at 21:05, Fabrice Bacchella <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
 |