Difference between revisions of "CDOT Dashboard"
Cadecairos (talk | contribs) |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 8: | Line 8: | ||
* Base the hardware on a PandaBoard | * Base the hardware on a PandaBoard | ||
* Purchase a large (32"?) display for the wall you face as you enter CDOT and/or the window facing the TEL southeast entrance | * Purchase a large (32"?) display for the wall you face as you enter CDOT and/or the window facing the TEL southeast entrance | ||
| − | * Use a passive infrared detector to detect when people are present, and make the display sleep until someone approaches | + | * Use a passive infrared detector to detect when people are present, and make the display sleep until someone approaches (Perhaps a Kinect?) |
== Version 0.1 Overview (Due Tuesday May 10th)== | == Version 0.1 Overview (Due Tuesday May 10th)== | ||
| Line 23: | Line 23: | ||
* Number of packages built (daily/weekly/monthly numbers) | * Number of packages built (daily/weekly/monthly numbers) | ||
* Machines free and waiting for build jobs | * Machines free and waiting for build jobs | ||
| − | * Downtime amount per machine (could be an interesting stat indicating some sort of failure pattern) | + | * Downtime amount per machine (date/time) (could be an interesting stat indicating some sort of failure pattern) |
Latest revision as of 21:55, 5 May 2011
Contents
Software
See https://github.com/jbuck/CDOT-Dashboard/wiki
Hardware
Implement a 'green' hardware display of the current dashboard. Ideas:
- Base the hardware on a PandaBoard
- Purchase a large (32"?) display for the wall you face as you enter CDOT and/or the window facing the TEL southeast entrance
- Use a passive infrared detector to detect when people are present, and make the display sleep until someone approaches (Perhaps a Kinect?)
Version 0.1 Overview (Due Tuesday May 10th)
- PandaBoard configured with F13 + kernel + video drivers
- FF3.6 compiled and optimized for the PandaBoard (plan for FF4 for later releases)
Version 0.2 Overview
- Firefox 4
Stats
- System up times
- Current processor loads
- Present RAM/HDD usage
- Number of packages built (daily/weekly/monthly numbers)
- Machines free and waiting for build jobs
- Downtime amount per machine (date/time) (could be an interesting stat indicating some sort of failure pattern)
