Add a manual scheduling mode to the scheduler

Registered by Michael Hudson-Doyle on 2011-11-30

In some situations, for example just after a major upgrade, we might want to place the system in a mode where no jobs are run automatically but we want to run a particular job to test basic functionality.

Blueprint information

Status:
Not started
Approver:
Paul Larson
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Drafting
Series goal:
Accepted for trunk
Implementation:
Unknown
Milestone target:
milestone icon backlog

Related branches

Sprints

Whiteboard

[pwlars, 2011-12-01] Would it make more sense to just do this with priorities? i.e. system is in maint mode, send a job, bump the priority to 999999 or something, and it will be the first to get picked.
[mwhudson, 2011-12-05] IMHO not really, it's not just about making sure that the job you want goes first, but also about making sure no other jobs are processed while you're unsure of the state of the system.

Meta:
Headline:
Acceptance:

(?)

Work Items

Work items:
Decide where to store flag: TODO
Add ui for manipulating flag: TODO
Consider flag in scheduler daemon: TODO

This blueprint contains Public information 
Everyone can see this information.