Switch to new GCP addons workers
Categories
(Release Engineering :: Release Automation, task)
Tracking
(firefox71 fixed)
| Tracking | Status | |
|---|---|---|
| firefox71 | --- | fixed |
People
(Reporter: nthomas, Assigned: nthomas)
References
Details
Attachments
(3 files)
This looks to be a release only worker, can't see anything on nightly.
|
Assignee | |
Comment 1•6 years ago
|
||
Switch addonworkers from AWS to GCP.
|
|
Assignee | |
Comment 2•6 years ago
|
||
TODO - add autoscaling. We have 4 prod machines in AWS, need to know average job time, if we can save time by scaling up.
|
|
Assignee | |
Comment 3•6 years ago
|
||
Both gecko-1-addon-dev and gecko-1-addon work on try (eg this push), but I am unsure of how to test gecko-3-addon prior to landing on beta. CoT seems to preclude that.
The jwtSecret values needed to be updated for gecko-1-addon, and there was a deploy for that. There is the possibility that gecko-3-addon was also updated but not deployed, so we should look out for 401 errors from amo prod.
|
||
Comment 4•6 years ago
|
||
We had some issues with Jenkins yesterday and couldn't land this in time for Monday betas. Will attempt to land this for Thursday betas.
|
|
||
Comment 5•6 years ago
|
||
Merged https://github.com/mozilla-releng/k8s-autoscale/pull/45 to master and production.
|
|
||
Comment 6•6 years ago
|
||
|
|
||
Comment 7•6 years ago
|
||
Status update:
- Fixed breakage in k8s auto-scaling with https://bugzilla.mozilla.org/attachment.cgi?id=9099591
- set the
min-replicasto 0 ingecko-1-addonso we have 0 wasted resources; turns out it works smoothly, we have no pods allocated - will push in-tree patch once things are stable, hopefully in time for Thursday's beta
|
|
||
Comment 9•6 years ago
|
||
| bugherder | ||
|
|
||
Comment 10•6 years ago
|
||
Addon workers worker like a charm in beta1 - see https://tools.taskcluster.net/groups/cwGZAl94Ru6DUmMGGspRgQ/tasks/LQ-zaUv8TYeGZIU5Mj3pxg/details
|
||
Comment 11•6 months ago
|
||
| uplift | ||
Description
•