Use preemptible instances in GCP
Categories
(Release Engineering :: Firefox-CI Administration, defect)
Tracking
(Not tracked)
People
(Reporter: coop, Assigned: coop)
References
Details
Attachments
(6 files, 1 obsolete file)
We've been running on on-demand instances in GCP rather than preemptible. We need to change this before we migrate any further workloads or we'll end up paying too much.
It's a pretty simple addition to the ci-configs, the equivalent of:
"scheduling": {
"onHostMaintenance": "TERMINATE",
"automaticRestart": false,
"preemptible": true
},
Patch incoming.
|
Assignee | |
Comment 1•5 years ago
|
||
|
|
Assignee | |
Comment 2•5 years ago
|
||
Depends on D56045
|
||
Comment 3•5 years ago
|
||
Deployed.
|
||
Comment 4•5 years ago
|
||
We should not set these options per-instance, but rather globally.
|
|
||
Comment 5•5 years ago
|
||
|
|
||
Comment 6•5 years ago
|
||
We initially filtered out some worker-pools from worker-manager providers
in the legacy cluster that didn't exist in the firefox-ci cluster. Now
that those have been removed, we can stop filtering them out.
|
|
||
Comment 7•5 years ago
|
||
These worker pools have never been used in the firefox-ci cluster. They were
test workers in the legacy cluster with provider ids that are not in the new
cluster.
|
|
||
Comment 8•5 years ago
|
||
These worker pools have never been used in the firefox-ci cluster. They were
test workers in the legacy cluster with provider ids that are not in the new
cluster.
|
|
||
Comment 9•5 years ago
|
||
These are hard-coded in ci-admin (and if we ever need non-prememtible workers
we can add a setting to control that there).
Backed out changeset 45c9502ffe23 (bug 1601736)
Backed out changeset cf2dffcf28c6 (bug 1601736)
|
||
Updated•5 years ago
|
|
|
||
Updated•5 years ago
|
Description
•