Create a test pool to run (perf) jobs directly on generic-worker
Categories
(Release Engineering :: Firefox-CI Administration, task)
Tracking
(Not tracked)
People
(Reporter: masterwayz, Unassigned)
Details
Someone asked about me this, this bug is to track the test work/patches for this.
Reporter | ||
Comment 1•3 years ago
|
||
Andrew, do you know how the GCP Linux images are created? Someone pointed at OpenCloudConfig but we have no clue how that works and if it's there.
Comment 2•3 years ago
|
||
Michelle, David is the expert on that currently. Redirecting to him.
I believe GCP images are using https://github.com/taskcluster/monopacker.
Is this to test running generic-worker on GCP instances instead of docker-worker?
I had applied the old puppet(puppetagain) configuration against cloud instances before but there were a number of pieces to disable.
For the new puppet(ronin-puppet), it may also work but I haven't tried it.
A simpler solution may be to take the generic-worker configuration and binaries and start from there. That's what I did when testing perf on cloud instances.
I'll look over my scripts from the cloud perf testing I finished last year (to make sure there are no secrets that will be exposed) and share that as an example.
Reporter | ||
Comment 4•3 years ago
|
||
Dhouse (sorry for the delay, I was out for a long weekend); this is to test the performance when running jobs directly on top of generic-worker (so not on docker-worker or docker through generic-worker), though :jmaher, correct me if I'm wrong.
Comment 5•3 years ago
|
||
I was looking to test linux in a VM instead of linux via docker. If we are moving to GCP and testing things out why not test out an upgrade. Ideally later this month when ubuntu 22.04 is released we can put that in the mix.
![]() |
||
Updated•2 years ago
|
Reporter | ||
Comment 6•2 years ago
|
||
Unused
Description
•