Ceph radosgw supports [0] the swift health check endpoint
"/swift/healthcheck". This change adds the haproxy
configuration [1] necessary to take the response of "GET
/swift/healthcheck" into account when determining the health
of a radosgw service.
For testing, I verified that:
- HAProxy starts and responds to requests normally with this
configuration.
- Servers with status != 2xx or 3xx are removed from the
backend.
- Servers that take too long to respond are also removed
from the backend. The default timeout value is 2s.
Tox 4.0.0 was recently released and it has several breaking changes.
We pin to < 4.0.0 here. We are planning to move forward only on the
master charm branches.
Tox is also pinned to < 4.0.0 for stable branches in upstream
openstack-zuul-jobs as well as in zosci-config. However, the
requires= section in the charm's tox.ini file ends up installing
tox>4, wiping out the zuul-pinned tox<4 that was already installed
installed. This patch fixes that.
The Ceph RADOS Gateway uses some unusual URI's for multisite
replication; ensure that mod_proxy passes the 'raw' URI down
to the radosgw http endpoint so that client and server side
signatures continue to match.
This seems quite Ceph specific so the template is specialised
into the charm rather than updated in charm-helpers.
Change-Id: Iede49ba8904500076d53388345e154a3ed18e761
Closes-Bug: 1966669
(cherry picked from commit 7907fa96e93085e114fb42f2dc547963938498fb)
Migration ceph stable charms to charmhub - octopus
This is the stable/octopus branch of the ceph charms. It tests against
{focal,bionic}-ussuri (validates octopus) and bionic-train
(validates nautilus).
Change-Id: Ic9fa430b5b62bf045c4d7c89371f359b429c1ba2
(cherry picked from commit c105015a6692f6571d54dcab09f6811997ac725b)
* use stable/21.10 libraries
* use zaza/zaza-openstack-tests at stable/21.10
* build.lock files for reactive charms
* bundles refer to ~openstack-charms candidate channel