[tracker] Manage everything with ci-admin
Categories
(Release Engineering :: Firefox-CI Administration, task)
Tracking
(Not tracked)
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.
Assignee | ||
Comment 1•6 years ago
|
||
- 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
Assignee | ||
Comment 2•6 years ago
|
||
- New worker-types needs secrets, but that isn't currently handled by ci-admin
Reporter | ||
Comment 3•6 years ago
|
||
- Secrets used in tasks (e.g.,
project/releng/gecko/build/level-1/gls-gapi.data
)
Assignee | ||
Comment 4•6 years ago
|
||
- service clients
Assignee | ||
Comment 5•6 years ago
|
||
- releng:nightly roles
Assignee | ||
Comment 6•6 years ago
|
||
- worker-type/worker-id roles
Assignee | ||
Comment 7•5 years ago
|
||
We have been consistently referring to the existing cluster as the legacy cluster.
Update the name to match.
Assignee | ||
Comment 8•5 years ago
|
||
Assignee | ||
Comment 9•5 years ago
|
||
Assignee | ||
Comment 10•5 years ago
|
||
Assignee | ||
Comment 11•5 years ago
|
||
Updated•5 years ago
|
Assignee | ||
Comment 12•5 years ago
|
||
Assignee | ||
Comment 13•5 years ago
|
||
Assignee | ||
Comment 14•5 years ago
|
||
Assignee | ||
Comment 15•5 years ago
|
||
Updated•5 years ago
|
Assignee | ||
Comment 16•5 years ago
|
||
Assignee | ||
Comment 17•5 years ago
|
||
This is useful for the legacy cluster, that has aws-provisioner and ec2-manager,
which don't exist in the new clusters.
Assignee | ||
Comment 18•5 years ago
|
||
Assignee | ||
Comment 19•5 years ago
|
||
Given the broad scope grants given to releng, it isn't possible
to veirfy if these restricted grants are effective or correct.
Updated•5 years ago
|
Assignee | ||
Comment 20•5 years ago
|
||
Assignee | ||
Comment 21•5 years ago
|
||
- 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.
Assignee | ||
Comment 22•5 years ago
|
||
Reporter | ||
Updated•5 years ago
|
Comment 23•5 years ago
|
||
Found in triaging: lots of good stuff landed in this bug, do we expect more work going forward or can we close this?
Updated•4 years ago
|
Comment 24•2 years ago
|
||
This appears to be all done.
Description
•