Eliminate or tune apache
Bug #1942643 reported by
James Troup
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ceph RADOS Gateway Charm |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
The current stack for Ceph radosgw in Charmed OpenStack appears to be:
haproxy -> apache -> radosgw
It's not clear to me what value Apache provides; modern haproxy can terminate ssl and that's all the Apache seems to do here. If we can, we should remove Apache and reduce the number of moving parts.
If we can't remove it for some reason, then we need to do a better job of tuning it in the charm. No MPM tuning is provided and that means it will rapidly become the bottleneck in any high RPS scenario.
Revision history for this message
| James Page (james-page) wrote | #1 |
| Changed in charm-ceph-radosgw: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
To post a comment you must log in.
Apache is only used for SSL termination and was selected in preference to haproxy to ensure end-to-end encryption of data on the wire.
That said the radosgw process itself is more than capable of performing the SSL termination eliminating the need for apache and still supporting end-to-end encryption of data on the wire so I think that would make sense.