Closed Bug 1548336 Opened 5 years ago Closed 5 years ago

migrate beetmoverscript workers to cloudops

Categories

(Release Engineering :: General, task)

Product:
Release Engineering
Component:
General
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1579476

People

(Reporter: rail, Assigned: rail)

References

Details

We plan to migrate our signing workers to GCP/cloudops as one of the first workers.

Listing their requirements:

  1. The workers will be using the Dockerflow approach, except the health check, which will be a CLI tool, instead of an HTTP API endpoint.

  2. there will be a special docker instance to handle autoscaling for these workers (1 per cluster).

  3. Production deployemts will be done explicitly by filing bugs for the cloudops team, using unique docker tag for every deployment (probably using the version as the tag)

(In reply to Rail Aliiev [:rail] from comment #0)

We plan to migrate our signing workers to GCP/cloudops as one of the first
workers.

beetmoverscript, not signingscript, oops.

Oh, this is exciting :) Looking forward to hear about the upcoming fanciness! \o/

Depends on: 1554825
Type: defect → task
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.