Closed Bug 664745 Opened 14 years ago Closed 10 years ago

Operation "operationalize dirty profile crontasks"

Categories

(Release Engineering :: General, defect, P5)

defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: dustin, Unassigned)

Details

(Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2012] [cleanup])

This is running out of a home directory on cruncher right now, which is functional but not quite production-worthy. We should * run this as a common system user (cltbld?) * in a well-documented fashion (add to the releng Applications page) * with some monitoring (pynsca and a passive nagios service) This will probably feed into a greater operationalize-cruncher project, which will involve things like unifying all of the crontasks (maybe with anacron?), moving tasks to other systems where necessary, etc.
(to be clear, this does *not* block bug 600980 - the ideas just arose out of that bug)
set to p5 in triage.
Priority: -- → P5
Component: Release Engineering → Release Engineering: Machine Management
QA Contact: release → armenzg
Whiteboard: [cleanup]
Product: mozilla.org → Release Engineering
So this still needs a supported and documented run location, and an way to have reporting if it stops running or fails. Still P5 for now, but not buildduty work
Component: Buildduty → General Automation
QA Contact: armenzg → catlee
Whiteboard: [cleanup] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2004] [cleanup]
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2004] [cleanup] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2012] [cleanup]
Anyone know if this is still a problem?
Flags: needinfo?(bugspam.Callek)
I know nothing about these...
Flags: needinfo?(bugspam.Callek)
I suspect we'll find out when it fails!
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.