2018-06-07 staging failover test plan
Failover Test Plan
README
If you are volunteering, please make yourself available to join the GCP Migration Rehearsal call. Ping @andrewn or @meks for an invite.
- Zoom link: https://gitlab.zoom.us/j/859814316
- Slack channel: #gcp_migration
High-level Overview
This test plan requires some manual testing as well as some automated testing using GitLab QA.
The automated and manual QA processes can be conducted in parallel with one another.
The plan will also involve testing during two distinct phases of the failover plan:
-
During the Blackout (inside the maintenance window period):
- All the tests conducted during this period are related to features critical to the operation of GitLab.com.
- The maintenance window cannot be closed until these tests pass.
-
After the Blackout (after the maintenance window period):
- These tests are non-critical, but, in order to keep the maintenance window as short as possible, should be conducted after the new failover GitLab instance is public.
Automated QA
During the Blackout
@remy to run GitLab QA against failed-over environment.
Important: Until https://gitlab.com/gitlab-org/gitlab-qa/issues/258 is fixed, we will not be showing gitlab-qa console logs in the recording.
-
Make sure to export the following environment variables export GITLAB_USERNAME=gitlab-qa GITLAB_PASSWORD=xxx GITLAB_QA_ACCESS_TOKEN=xxx
-
Automated QA complete with 100% pass gitlab-qa Test::Instance::Any EE 11.0.0-rc5.ee.0 https://staging.gitlab.com
Put the results of Gitlab QA run here
Manual QA
Manual test plan: https://docs.google.com/spreadsheets/u/1/d/1TquRG_RSOFPR8vM8ZsI3GVzDzkQ4A-QO85M78Q-bdHU/edit