Closed
Bug 664745
Opened 14 years ago
Closed 10 years ago
Operation "operationalize dirty profile crontasks"
Categories
(Release Engineering :: General, defect, P5)
Release Engineering
General
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.
| Reporter | ||
Comment 1•14 years ago
|
||
(to be clear, this does *not* block bug 600980 - the ideas just arose out of that bug)
Updated•13 years ago
|
Component: Release Engineering → Release Engineering: Machine Management
QA Contact: release → armenzg
Whiteboard: [cleanup]
| Assignee | ||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
Comment 3•12 years ago
|
||
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
Updated•11 years ago
|
Whiteboard: [cleanup] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2004] [cleanup]
Updated•11 years ago
|
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2004] [cleanup] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2012] [cleanup]
| Reporter | ||
Comment 6•10 years ago
|
||
I suspect we'll find out when it fails!
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
| Assignee | ||
Updated•7 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•