Closed
Bug 1399437
Opened 7 years ago
Closed 6 years ago
Turn off scheduler-taskcluster-net Heroku app
Categories
(Taskcluster Graveyard :: Scheduler, enhancement, P4)
Taskcluster Graveyard
Scheduler
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: pmoore, Assigned: dustin)
References
Details
Now that releng are no longer using it (bug 1259627) we should be able to remove all traces of it.
Reporter | ||
Comment 1•7 years ago
|
||
Things I can think of:
* remove scheduler/schedulerevents from https://references.taskcluster.net/manifest.json (done)
* regenerate all clients
* remove all scopes that refer to scheduler from roles/clients
* update github repo to say it is no longer in service
* update doc references, in our schemas/references, in the docs site, and in anything that uploads docs
* terminate heroku dynos
* delete/release any persistent storage the service used
* delete heroku app
* send out communication about sunset
* close all open issues/PRs/bugzilla bugs related to scheduler
* mark bugzilla component as obsolete so no new bugs land there
* sing songs by candlelight to commemorate our sunken hero
* check nothing in tools.taskcluster.net hits any scheduler endpoint
I no doubt missed other things, pitch in if you think of something!
Reporter | ||
Comment 2•7 years ago
|
||
This is now the only open bug in Taskcluster :: Scheduler - I've closed/moved all the others.
Reporter | ||
Comment 3•7 years ago
|
||
(In reply to Pete Moore [:pmoore][:pete] from comment #1)
> * remove all scopes that refer to scheduler from roles/clients
I found these in the Scope Inspector (https://tools.taskcluster.net/auth/scopes/):
scheduler:*
scheduler:create-task-graph
scheduler:extend-task-graph
scheduler:extend-task-graph:*
scheduler:route:gaia-taskcluster
scheduler:route:taskcluster-github.*
Comment 4•7 years ago
|
||
Commit pushed to master at https://github.com/taskcluster/taskcluster-client-java
https://github.com/taskcluster/taskcluster-client-java/commit/13d3b6368ae8a4bb3c5d9cffe2fa092e1a9d7333
Bug 1399437 - don't generate scheduler classes
Reporter | ||
Comment 5•7 years ago
|
||
Removed scheduler from taskcluster-client-go and taskcluster-client-java
Reporter | ||
Comment 6•7 years ago
|
||
(In reply to Pete Moore [:pmoore][:pete] from comment #5)
> Removed scheduler from taskcluster-client-go and taskcluster-client-java
Also updated github pages:
* http://taskcluster.github.io/taskcluster-client-go
* http://taskcluster.github.io/taskcluster-client-java
Assignee | ||
Comment 7•7 years ago
|
||
I think we can check back in a few days and see that nothing is using the scheduler, at which point we can turn it off. We should leave it installed in Heroku until esr52 is out the door, though (in August).
Assignee | ||
Comment 8•7 years ago
|
||
(topic updated to increase likelihood of finding this bug if someone decides to clean up idle Heroku apps)
Summary: Sunset the scheduler → Turn off scheduler-taskcluster-net Heroku app
Assignee | ||
Comment 9•7 years ago
|
||
No hits in the last 3 days per logs.
Assignee | ||
Comment 10•7 years ago
|
||
OK, all resources are set to 0 dynos. I'll leave it installed as suggested in comment 7, though (and still in the TLS cert, etc.)
Updated•7 years ago
|
Priority: -- → P4
Assignee | ||
Comment 11•6 years ago
|
||
I've requested a cert without scheduler.taskcluster.net in it.
QA Contact: dustin
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → dustin
Assignee | ||
Comment 12•6 years ago
|
||
scheduler is dead, long live scheduler
I removed it from the TLS certs everywhere.
I deleted the Heroku app.
All that remains is to remove the CNAME from DNS.
Assignee | ||
Comment 13•6 years ago
|
||
well, I guess there's nothing left here but the blocking bug so ...
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 14•6 years ago
|
||
TC client deleted, too.
Updated•6 years ago
|
Product: Taskcluster → Taskcluster Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•