This repository was archived by the owner on Jan 29, 2025. It is now read-only.
This repository was archived by the owner on Jan 29, 2025. It is now read-only.
Normandy CDN Migration #2341
Description
Migrate over to GCP
- Use nginx/varnish to replicate the exact same responses we serve now, as an interim solution, as a diff dns first
- Have QA do a sanity check by setting desktop to point to diff dns, run test suite for normandy
-
Use uptake telemetry to get healthy baseline of normandy calls
Start with a 20% switch over and look at uptake telemetry after a day to ensure normandy calls are as expected - Switch over to original dns(100% if previous step is fine)
Note: for the interest of time and cost and deciding it was somewhat low risk, we rolled out incrementally throughout a single day - Roll out 1.45.1 to prod which include caching changes to the v1 endpoint
Follow up work.....
-
Identify consumers of Normandy
- Analyze user agents to understand the distribution of clients/versions/domains calling/being called
- identify all the remote calls made by Normandy desktop client
-
Make the code changes for headers that we can get rid of
- Run a dummy experiment to get baseline
- Explore making server side changes to deprecate the dependency on certain headers ref:docs
- Implement changes to remove headers from investigation (Normandy Server)
- Implement changes (if any) to Normandy Client
- Migrate CDN again to reflect code changes
- Run a dummy experiment to ensure there are no breaking changes
- Setup manual QA process to test clients explicitly hitting old and new CDN
-
Identity which endpoints are no longer used and which arent for deprecation plan