Closed
Bug 1596948
Opened 5 years ago
Closed 5 years ago
add firefox-ci monopacker metal worker-pools
Categories
(Release Engineering :: Firefox-CI Administration, task)
Release Engineering
Firefox-CI Administration
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: miles, Assigned: miles)
References
Details
Attachments
(2 files)
|
2.93 KB,
patch
|
Details | Diff | Splinter Review | |
|
47 bytes,
text/x-phabricator-request
|
Details | Review |
In order to resume work on switching from packet.net to AWS metal instances we need to create worker-pools in the firefox-ci taskcluster deployment that we can test against.
|
Assignee | |
Comment 1•5 years ago
|
||
I'm not able to submit this via phabricator at this time but will shortly - here's the ci-configuration diff I worked up for this.
|
|
Assignee | |
Comment 2•5 years ago
|
||
We have the worker-pool: https://firefox-ci-tc.services.mozilla.com/worker-manager/gecko-t%2Ft-linux-metal
We're running into an issue where there is no spot capacity for the metal instance type. I'm going to change the worker-pool to use on-demand instances.
|
|
Assignee | |
Comment 3•5 years ago
|
||
|
||
Comment 4•5 years ago
|
||
This got rolled back in https://bugzilla.mozilla.org/show_bug.cgi?id=1578460#c12
|
|
||
Updated•5 years ago
|
Assignee: nobody → miles
Status: NEW → ASSIGNED
|
||
Updated•5 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•