High availability for the Ceph Object Gateway
As a storage administrator, you can assign many instances of the Ceph Object Gateway to a
single zone. This allows you to scale out as the load increases, that is, the same zone group and
zone; however, you do not need a federated architecture to use a highly available proxy. Since each
Ceph Object Gateway daemon has its own IP address, you can use the ingress service
to balance the load across many Ceph Object Gateway daemons or nodes. The ingress
service manages HAProxy and keepalived daemons for the Ceph Object Gateway
environment. You can also terminate HTTPS traffic at the HAProxy server, and use HTTP between the
HAProxy server and the Beast front-end web server instances for the Ceph Object Gateway.
Prerequisites
-
At least two Ceph Object Gateway daemons running on different hosts.
-
Capacity for at least two instances of the ingress service running on different hosts