- 07 Aug, 2018 1 commit
-
-
John Jarvis authored
Fixes the command that changes Shared Runners timeout. See merge request gitlab-com/migration!184
-
- 06 Aug, 2018 15 commits
-
-
Brett Walker authored
Add comms handler steps for youtube and status.io See merge request gitlab-com/migration!190
-
Dave Smith (.org) authored
-
Dave Smith (.org) authored
Move T-0 to "Prevent updates to the primary" Closes #743 See merge request gitlab-com/migration!186
-
Brett Walker authored
Fix the criteria for an alert silence See merge request gitlab-com/migration!183
-
Ahmad Sherif authored
-
Brett Walker authored
Resolve "Add step to kill queue disabling loop after sidekiq is stopped" Closes #752 See merge request gitlab-com/migration!189
-
Brett Walker authored
-
Brett Walker authored
Resolve "Update failover templates with proper script references" Closes #756 See merge request gitlab-com/migration!188
-
Brett Walker authored
-
Brett Walker authored
fix list of domains for hostinfo See merge request gitlab-com/migration!187
-
Brett Walker authored
-
Toon Claes authored
-
Nick Thomas authored
Address (some) feedback from 2018-08-02 failover attempt Closes #753 See merge request gitlab-com/migration!176
-
Nick Thomas authored
bash3.2 compatibility for hostinfo Closes #755 See merge request gitlab-com/migration!185
-
Nick Thomas authored
-
- 05 Aug, 2018 1 commit
-
-
Tomasz Maczukin authored
For the migration process we need to ensure, that during the switch moment no job on Shared Runners will be running. The baclout window was scheduled to take 1 hour, and this is the timeout that we want to enforce on Runners. While we need to update the general Shared Runners named `shared-runners-manager-X.gitlab.com` - since the timeout is currently set to 3 hours, we should not touch `gitlab-org` labelled Shared Runners named `gitlab-shared-runners-manager-X.gitlab.com`. `gitlab-org` runners already are configured with a 1 hour timeout and this is the expected timeout for them. Since it aligns with what we need for the migration, I've updated the commands that are changeing the timeout. Now we're not touching the `gitlab-org` runners at all, which means that: - there is no change during the preparation step (`gitlab-org` runners during the migration will be set to 1h timeout), - the reconfiguration step (or the failover step) will not change the expected timeout of `gitlab-org` runners, which should be left as 1h after the migration is ended.
-
- 03 Aug, 2018 21 commits
-
-
Brett Walker authored
test ssh on proper host in production See merge request gitlab-com/migration!182
-
Brett Walker authored
-
Brett Walker authored
fix references to script location See merge request gitlab-com/migration!181
-
Brett Walker authored
-
Andrew Newdigate authored
Critical typo fix See merge request gitlab-com/migration!180
-
Andrew Newdigate authored
-
Andrew Newdigate authored
Make remote rails runner commands work much better See merge request gitlab-com/migration!179
-
Andrew Newdigate authored
-
Brett Walker authored
Sidekiq Monitor Script, Mailroom Stop, Sidekiq Pullmirror Shutdown script Closes #722 See merge request gitlab-com/migration!165
-
Andrew Newdigate authored
-
Nick Thomas authored
-
Nick Thomas authored
-
Andrew Newdigate authored
More symlink fixes See merge request gitlab-com/migration!175
-
Andrew Newdigate authored
-
Andrew Newdigate authored
Harden the scripts against symlinks See merge request gitlab-com/migration!174
-
Andrew Newdigate authored
-
Andrew Newdigate authored
Structure only See merge request gitlab-com/migration!171
-
Andrew Newdigate authored
-
Nikolay authored
Revert "Merge branch 'database_wrangler_automation' into 'master'" See merge request gitlab-com/migration!172
-
Nikolay authored
This reverts merge request !170
-
Nikolay authored
Database wrangler automation See merge request gitlab-com/migration!170
-
- 02 Aug, 2018 2 commits
-
-
Matteo Melli authored
-
Matteo Melli authored
-