Den ons 18 aug. 2021 kl 08:41 skrev Christian Rohmann <christian.rohmann@xxxxxxxxx>: > > On 17/08/2021 13:37, Janne Johansson wrote: > > Don't forget that v4 auth bakes in the clients idea of what the > > hostname of the endpoint was, so its not only about changing headers. > > If you are not using v2 auth, you will not be able to rewrite the > > hostname on the fly. > > Thanks for the heads up in this regard. > > > How would one achieve the idea of having two distinct sites, i.e. > > * s3-az1.example.com > * s3-az2.example.com > > each having their own rgw_dns_name set and doing mult-site sync, but > also having a generic hostname, s3.example.com, > that I can simply reconfigure to point to the master? > > From what you said I read that I cannot: > > a) use an additonal rgw_dns_name, as only one can be configured (right?) > b) simply rewrite the hostname from the frontend-proxy / lb to the > backends as this will invalidate the sigv4 the clients do? I haven't tried adding multiple names to the zone(group), that might work out fine. It would just be a matter of reading the request and using this dnsname if it appears in the list of possible names, so it's not a hard problem to solve on the RGW side to own N+1 DNS names, even if you didn't read the request, one could just loop over them one by one and see if any works. -- May the most significant bit of your life be positive. _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |