Geo: Document installation tests
Background
It would be awesome if we had CI attempt:
- installing
- upgrading
- downgrading
for every major/minor/patch version, for every possible deployment configuration, including using Geo.
Currently, we at least have Geo running on staging, so it is always upgraded to the latest release. If an upgrade breaks GitLab significantly, we should know about it. We plan to constantly run Geo QA tests on staging soon too.
I think we might be doing some other automated tests as well, but we are far from testing all scenarios.
We occasionally manually setup and test significant changes, for example running Geo with PostgreSQL 11.
Proposal
-
Add a document that lists the issues where we've done significant manual testing, and a brief summary.
I think customers (and our own support team, etc) would find it valuable to see:
- what we personally validated
- the problems we ran into and how we resolved them
- the issues that we created
I'm suggesting a "journal log" style, to keep the document simple and flexible, because I don't want to add more than an hour of work to every validation test we do. Old tests quickly becomes irrelevant, and the tests are highly variable in intention and context, so they don't need all need to fit into a table. At a minimum, I think it's acceptable to drop in just an issue link (with title). If you want, you can add additional context, or easy-to-consume tables.
Example
## 2020-04-10
[PostgreSQL 11 upgrade procedure for GEO installations](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/4975): Prior to making PostgreSQL 11 the default version of PG in GitLab 12.10, we tested upgrading to PG 11 in Geo deployments on GitLab 12.9.
## 2020-04-07
[Verify GEO installation with PostgreSQL 11](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/4971): Prior to making PostgreSQL 11 the default version of PG in GitLab 12.10, we tested fresh installations of GitLab 12.9 with Geo, installed with PG 11.
## 2020-02-18
[Test and validate PostgreSQL 10.0 upgrade for Geo](https://gitlab.com/gitlab-org/gitlab/issues/12092)