2020-03-12 - Feature flag toggle for namespaces

Production Change

Change Summary

Infra will make sure the feature flag related to deployment of gitlab-org/gitlab!56360 (merged) is done before the weekend of March 13,14 starts.

Change Details

1. Services Impacted - ServiceAPI , ServiceWeb
2. Change Technician - @ggillies or @T4cC0re
3. Change Criticality - C3
4. Change Type - changescheduled
5. Change Reviewer - @dawsmith
6. Due Date - 2021-03-12 or 2021-03-13 depending on time of deploy to staging and prod.
7. Time tracking - 10 minutes
8. Downtime Component - no downtime

Detailed steps for the change

Pre-Change Steps - steps to be completed before execution of the change

Estimated Time to Complete (mins) - 0

• None

Change Steps - steps to take to execute the change

Estimated Time to Complete (mins) - 5

• For Staging: in #production channel - chatops: /chatops run feature set top_level_group_creation_enabled false --staging
• in #production - chatops: /chatops run feature set top_level_group_creation_enabled false

Post-Change Steps - steps to take to verify the change

Estimated Time to Complete (mins) - 20

• Watch dashboards and error logs.
• Post-Change Step 2
• Post-Change Step 3

Rollback

Rollback steps - steps to be taken in the event of a need to rollback this change

Estimated Time to Complete (mins) - 10

• in #production - chatops: /chatops run feature set top_level_group_creation_enabled true

Monitoring

Key metrics to observe

• Metric: Overall web and api status
  • Location: https://dashboards.gitlab.net/d/general-public-splashscreen/general-gitlab-dashboards?orgId=1
  • What changes to this metric should prompt a rollback: Any significat drop in appdex or increase in error ratio.

Summary of infrastructure changes

• Does this change introduce new compute instances?
• Does this change re-size any existing compute instances?
• Does this change introduce any additional usage of tooling like Elastic Search, CDNs, Cloudflare, etc?

n/a - no changes relevant here.

Changes checklist

• This issue has a criticality label (e.g. C1, C2, C3, C4) and a change-type label (e.g. changeunscheduled, changescheduled) based on the Change Management Criticalities.
• This issue has the change technician as the assignee.
• Pre-Change, Change, Post-Change, and Rollback steps and have been filled out and reviewed.
• Necessary approvals have been completed based on the Change Management Workflow.
• Change has been tested in staging and results noted in a comment on this issue.
• A dry-run has been conducted and results noted in a comment on this issue.
• SRE on-call has been informed prior to change being rolled out. (In #production channel, mention @sre-oncall and this issue and await their acknowledgement.)
• There are currently no active incidents.