#532: BibSched: new motd-like facility for task queue monitor
--------------------------+-----------------
Reporter: simko | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: BibSched | Version:
Resolution: | Keywords:
--------------------------+-----------------
Comment (by simko):
Yes, it may be perhaps good to have a new mode that will make this
even more explicit. I would picture it as follows: (i) for continuity
reasons, the bibsched daemon would still be switching between AUTO and
MANUAL modes, as is the case now; (ii) only humans would be permitted
to switch from MANUAL to the new HALTED or maybe better said LOCKED
mode, and this operation that would require to fill in the reason for
this, and this reason will be stored as motd; (iii) when a new
supporter logs in to check the queue and the queue is in the LOCKED
mode, the monitor would display only a big red screen containing the
motd warning and a possibility to unlock it in order to switch back to
MANUAL mode, but no other queue operations besides unlocking; (iv) in
usual situations when the queue is not locked, the supporters will be
permitted to put up an optional motd in any mode, which would be
displayed then even if the queue is in the automatic mode, that would
be used for alert-like situations such as "Watch out today at 16:00
big user storm expected" or "Lengthy indexing going on to fix foo" and
the like.
Nevertheless, a new bibsched mode is not really required; I think it
should be fully sufficient to have a nice prominent motd display and
two AUTO and MANUAL modes only, so that people are informed about what
is going on when the queue is on MANUAL so that they would not operate
the queue by mistake. It should not be really necessary to go into
the locking/halting stuff... so I'd avoid doing so unless it is really
ultra cheap to add this feature alongside implementing motd.
(E.g. the bibsched code should ideally not change too much bearing in
mind pending Pablo's quarantined records branch that we should
stress-test and put to at least to `next`.)
--
Ticket URL: <http://invenio-software.org/ticket/532#comment:2>
Invenio <http://invenio-software.org>
