Closed Bug 1177878 Opened 9 years ago Closed 9 years ago

onyx 1.4.11 deployment to production

Categories

(Content Services Graveyard :: Tiles: Ops, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED
Iteration:
41.3 - Jun 29

People

(Reporter: kthiessen, Assigned: relud)

References

()

Details

(Whiteboard: .001)

+++ This bug was initially created as a clone of Bug #1176647 +++

onyx 1.4.8 contains changes that allow serving different sets of tiles to user agents based on their channel preferences.

The v3 API endpoint introduced the requirement for the UA to specify the channel in addition to the locale.

This release allows onyx to serve accordingly.

Quoting the CHANGELOG.md:

> * This will require a change in puppet scripts:
>  * there are additional S3 tile index origins
>  * will require puppet template changes, due to cfg change to allow for multiple indexes
>  * cron job will need to download 3 files instead of just 1

Furthermore, this depends on splice 1.1.22 to be deployed
Blocks: 1177880
Onyx wasn't working in stage, due to config problems. This revealed a bug in the test, which was finishing prematurely. Deployment is being delayed until monday, when we can fix the tests.
fixed release is 1.4.11
Status: NEW → ASSIGNED
Summary: onyx 1.4.8 deployment to production → onyx 1.4.11 deployment to production
fixed tests require new monitor server, which is currently deploying in prod.
monitor server deployed and reporting to datadog, ready for onyx deploy
deploying onyx canary to prod
canary deployed, geoip test looks good, waiting on redshift propagation test
redshift propagation test passed, scaling up new onyx to 11 nodes
new onyx scaled up, scaling down old onyx
old onyx stack scaled down, enabling auto-scaling on new onyx stack
geoip test is fully passing in prod
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
redshift propagation test passing in prod
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.