Closed Bug 1566931 Opened 6 years ago Closed 2 years ago

[tracker] Manage everything with ci-admin

Categories

(Release Engineering :: Firefox-CI Administration, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dustin, Assigned: tomprince)

References

Details

Attachments

(16 files)

47 bytes, text/x-phabricator-request
Details | Review
47 bytes, text/x-phabricator-request
Details | Review
47 bytes, text/x-phabricator-request
Details | Review
47 bytes, text/x-phabricator-request
Details | Review
47 bytes, text/x-phabricator-request
Details | Review
47 bytes, text/x-phabricator-request
Details | Review
47 bytes, text/x-phabricator-request
Details | Review
47 bytes, text/x-phabricator-request
Details | Review
47 bytes, text/x-phabricator-request
Details | Review
47 bytes, text/x-phabricator-request
Details | Review
47 bytes, text/x-phabricator-request
Details | Review
47 bytes, text/x-phabricator-request
Details | Review
47 bytes, text/x-phabricator-request
Details | Review
47 bytes, text/x-phabricator-request
Details | Review
47 bytes, text/x-phabricator-request
Details | Review
47 bytes, text/x-phabricator-request
Details | Review

We currently manage some roles, some hooks, and aws-provisioner worker types in ci-admin. To redeploy cleanly to a new cluster, we'll need to manage all of the required resources.

The first order of business is to figure out what those are, then parcel out the work of managing those things.

  • manual cron tasks hooks (e.g. trigger nightlies for sherrifs)
  • all scheduled tasks for mobile projects
  • granting project-releng:ci-group roles to various other roles/users
  • New worker-types needs secrets, but that isn't currently handled by ci-admin
  • Secrets used in tasks (e.g., project/releng/gecko/build/level-1/gls-gapi.data)
Blocks: 1573977
  • service clients
  • releng:nightly roles
  • worker-type/worker-id roles
Depends on: 1586895

We have been consistently referring to the existing cluster as the legacy cluster.
Update the name to match.

Attachment #9105624 - Attachment description: Bug 1566931: Add support for assigning scopes to arbitrary roles. → Bug 1566931: Add support for assigning scopes to arbitrary roles;
Depends on: 1593461
Depends on: 1593468
Depends on: 1593470
Depends on: 1593471
Attachment #9106003 - Attachment description: Bug 1566931: Fix grant tests for supporting per-environment grants; r?Callek → Bug 1566931: Fix grant tests now that the current environment is queried; r?Callek
Depends on: 1593488
Depends on: 1593489
Depends on: 1593494
Depends on: 1593495
Depends on: 1593496
Depends on: 1593498

This is useful for the legacy cluster, that has aws-provisioner and ec2-manager,
which don't exist in the new clusters.

Given the broad scope grants given to releng, it isn't possible
to veirfy if these restricted grants are effective or correct.

Attachment #9106343 - Attachment description: Bug 1566931: Move sherrif scopes to ci-admin; r?Callek → Bug 1566931: Move sheriff scopes to ci-admin; r?Callek
  • Staging should not have always-running workers, since there is not the demand
    for it.
  • firefox-ci should not currently have non-aws workers, as the currently expected
    providers don't exist in non-legacy clusters. We will adjust the config and then
    remove this modifier after the TCW.
Component: Operations and Service Requests → Firefox-CI Administration
Product: Taskcluster → Release Engineering

Found in triaging: lots of good stuff landed in this bug, do we expect more work going forward or can we close this?

Flags: needinfo?(mozilla)
Flags: needinfo?(mozilla)

This appears to be all done.

Status: NEW → RESOLVED
Closed: 2 years ago
QA Contact: mgoossens
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: