Closed
Milestone
Jul 12, 2017–Jul 18, 2017
WoW ending 2017-07-18
Workout of the Week
Display by
Error fetching burnup chart data
Burndown chart
Remaining
Burnup chart
Total
Completed
Unstarted Issues (open and unassigned)
0
Ongoing Issues (open and assigned)
0
Completed Issues (closed)
27
- ES log cluster outage
- NFS outage 2017-07-15
- staging.gitlab.com down
- Git09 oopsed but there was no alert
- Pages deploys are broken
- Test using a tar pipe to copy large amount of small files
- Azure Disk Resource Quota Limit
- Set up GitLab Slack App on GitLab.com
- Run mtail as git user to be able to tail omnibus logs
- Start indexing tests on ES production cluster
- Database goals for July 19th, 2017
- Terraform DNS Servers for Internal DNS
- Move the deployment rake task out of the chef-repo to a separate project without changing it
- Prometheus monitoring for backups
- Role roles/gitlab-import-node.json uses DB port 5432 but should use pgbouncer port 6432 instead
- Debug and Fix the OOM issues on the sidekiq nodes
- Remove sidekiq-realtime-0[45] nodes
- Orphaned mtail process on db1
- mtail not working properly for WALE backups
- configure repmgr on the two new staging db nodes
- restore production db to staging new staging dbs
- Build 2 new db nodes for staging with terraform
- Create a graph and ~~/or~~ alert for WAL-E backups
- Make sure database backups are encrypted
- Figure out the size of `/builds` on production
- Fix failing haproxy tests
- Move all GitLab.com instances to the new network
Loading
Loading
Loading