Closed
Bug 1343575
Opened 7 years ago
Closed 7 years ago
ramp up more beetmoverworker instances to handle increasing tcmigration load
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Infrastructure & Operations Graveyard
CIDuty
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mtabara, Assigned: mtabara)
References
Details
We need to ramp up more instances to handle the beetmoverworker load.
|
Assignee | |
Comment 1•7 years ago
|
||
Used: * https://wiki.mozilla.org/ReleaseEngineering/How_To/Loan_a_Slave#AWS_machines (existing configuration) * http://scriptworker.readthedocs.io/en/latest/chain_of_trust.html#new-scriptworker-gpg-keys * https://github.com/mozilla-releng/cot-gpg-keys/pull/19 * https://github.com/mozilla-releng/cot-gpg-keys/releases/tag/production-20170301233719 * https://wiki.mozilla.org/ReleaseEngineering/PuppetAgain/Secrets#Using_EYAML * pinning via https://wiki.mozilla.org/ReleaseEngineering/PuppetAgain/HowTo/Set_up_a_user_environment#Pinning We now have additional workers: beetmoverworker-3.srv.releng.use1.mozilla.com beetmoverworker-4.srv.releng.usw2.mozilla.com
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
|
||
Updated•6 years ago
|
Product: Release Engineering → Infrastructure & Operations
|
|
||
Updated•4 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•