Closed
Milestone
Jul 4, 2017–Jul 11, 2017
WoW ending 2017-07-11
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)
30
- Outage July 7th 9:20pm UTC
- Enabling Prometheus metrics on admin panel caused some web nodes to be unresponsive
- GitLab assets returning 404 errors + incorrect gitlab-ee version deployed on nodes
- Increase timeout for long running deploys
- Rolling restart of unicorn service in fe-git nodes
- Create the registry infrastructure in prodution
- Database goals for July 12th
- Backup Appreciation Day 2017-07-05
- Make registry01 operational in staging
- Reshape sidekiq fleet to split real-time from best-effort from remaining
- [META] Run Registry separately from the rest of the fleet
- Create Script for packagecloud db backup
- Adjust project_mirror capacity in GitLab.com
- Change Storage Class of DB WAL-E backups
- Receiving mail notifications from staging.gitlab.com
- Sidekiq stats are gone since 06/07/2016 15:45 UTC
- Clean up services after the registry isolation
- Rolling restart unicorn on web nodes
- Update unicorn memory limits
- Isolate the registry service to its own fleet
- Clean up ebs.gitlap.com
- Create AWS account for Brian
- Prometheus won't reflect alert changes unless it's reloaded (manually)
- Separate gitlab-cluster execution from the standard sidekiq fleet
- Low disk space alerts on worker-sshX nodes
- Add sidekiq_cluster for merge
- worker-api03 out of disk space in /var due to nginx logs
- Add banner to performance.gitlab.net to encourage public dashboards
- Stop running Unicorn on Sidekiq workers
- Rebuild fe-lb08
Loading
Loading
Loading