Closed Bug 1585603 Opened 5 years ago Closed 5 years ago

Switch to new GCP addons workers

Categories

(Release Engineering :: Release Automation: Other, task)

task
Not set
normal

Tracking

(firefox71 fixed)

VERIFIED 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.

Switch addonworkers from AWS to GCP.

TODO - add autoscaling. We have 4 prod machines in AWS, need to know average job time, if we can save time by scaling up.

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.

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.

See Also: → 1580054

Status update:

  • Fixed breakage in k8s auto-scaling with https://bugzilla.mozilla.org/attachment.cgi?id=9099591
  • set the min-replicas to 0 in gecko-1-addon so 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
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: