As in T387833: Gerrit switchover process we'll need to document and automate the process of switching secondary roles (replica/spare)
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T407557 OpenSSH 10.1+ warns that Wikimedia SSH does not use post-quantum key exchange algorithm | |||
| Open | None | T407844 Gerrit ssh daemon does not offer post-quantum kex leading to a warning with OpenSSH 10 | |||
| Open | None | T392448 Upgrade to Gerrit 3.12 | |||
| Open | None | T379714 Upgrade to Gerrit 3.11 | |||
| Open | None | T392465 Switch Gerrit from Java 17 to Java 21 | |||
| Open | None | T384595 Upgrade Collab hosts to Bookworm | |||
| Open | None | T392464 Upgrade Gerrit hosts from Bullseye to Bookworm | |||
| Open | None | T387831 Standardize failover procedures for Collab services | |||
| Resolved | None | T393239 ProbeDown | |||
| In Progress | ABran-WMF | T387833 Gerrit switchover process | |||
| Open | ABran-WMF | T406334 Gerrit switchover between secondary instances |
Event Timeline
Comment Actions
This would only be a thing though if we permanently keep 3 or more gerrit servers around.
So far we have one prod and one replica and once old hardware is replaced we would be back to exactly 2 machines in production with one extra as standby for gerrit and phab. And that one we would only use if one of the 2 prod machines dies.
So then it would be more like "how to spin up a new replica" rather than failing over from one working one to another. right?