Difference between revisions of "GreenLight BlackBox 2.0"
(→Project Overview) |
(→Status) |
||
Line 6: | Line 6: | ||
* Load in racks/doors/waterpipes/electrical within box (separate entities) | * Load in racks/doors/waterpipes/electrical within box (separate entities) | ||
* Racks & doors interaction/animation | * Racks & doors interaction/animation | ||
− | * Populate the racks with hardware components | + | * Populate the racks with hardware components from flat files |
* (High-level) Config file mapping for components to textures -- No more need to make individual server models. | * (High-level) Config file mapping for components to textures -- No more need to make individual server models. | ||
* Update hardware data from remote site (message sending instead of file reading, no NFS delay) | * Update hardware data from remote site (message sending instead of file reading, no NFS delay) | ||
* Transparency mode for non-component entities | * Transparency mode for non-component entities | ||
− | * Read in power consumption data from remote site and display it via color | + | * Read in power consumption data from remote site, store it meaningfully, and display it via a color relative to expected value range for the component |
− | * Selection interface to target specific components in the racks | + | * Selection interface to target specific components in the racks (non-selected components are transparent) |
+ | * Selection interface extended to allow cluster selection (clusters defined by name in the config file) | ||
+ | * Heuristics for expected min/max wattage value per component in the racks | ||
+ | * Visual mouse/wand over effects: scale up components in rack | ||
+ | * Visual mouse/wand over effects: re-color doors/racks | ||
+ | * Read in power consumption data from DB over a range of time | ||
+ | * Display power consumption for a range of data via a color graph across the face of each part (via shader) | ||
+ | * Handle component transparency via shaders | ||
+ | * Legend added to 'Power Consumption' submenu which defines the color gradient and outlier cases | ||
==To-Do== | ==To-Do== |
Revision as of 10:27, 26 July 2011
Contents |
Project Overview
Recent application for the GreenLight project, allowing users to visit the BlackBox virtually while observing live data from the physical BlackBox, such as power consumption and temperature readings. This allows non-obtrusive observation of the data, which could otherwise be affected if one were to enter the actual BlackBox. Additionally, a user can look at historical data of the components, with an effective "4D" display in which a range of data (spanning many days) is shown all at once via color gradients. The 8 racks within the Sun Data Center (the BlackBox) are populated with the components/servers/computers that are actually there via querying an up-to-date database of the hardware specs, along with the up-to-date energy statistics.
Status
- Load in BlackBox
- Load in racks/doors/waterpipes/electrical within box (separate entities)
- Racks & doors interaction/animation
- Populate the racks with hardware components from flat files
- (High-level) Config file mapping for components to textures -- No more need to make individual server models.
- Update hardware data from remote site (message sending instead of file reading, no NFS delay)
- Transparency mode for non-component entities
- Read in power consumption data from remote site, store it meaningfully, and display it via a color relative to expected value range for the component
- Selection interface to target specific components in the racks (non-selected components are transparent)
- Selection interface extended to allow cluster selection (clusters defined by name in the config file)
- Heuristics for expected min/max wattage value per component in the racks
- Visual mouse/wand over effects: scale up components in rack
- Visual mouse/wand over effects: re-color doors/racks
- Read in power consumption data from DB over a range of time
- Display power consumption for a range of data via a color graph across the face of each part (via shader)
- Handle component transparency via shaders
- Legend added to 'Power Consumption' submenu which defines the color gradient and outlier cases
To-Do
- Heuristics for expected min/max wattage values per component
- Read in power consumption data over a range of time in the past and display (animate through) it
Future Work
- Auto-pilot version of plugin (for demos, especially when a wand isn't available)
- Run through OssimPlanet
- Temperature zones (pull data and display)
- Temperature zones over a range of time from the past, animate through
Participants
Software Developers:
Project Advisors:
Development Assistance:
- Philip Weber
- Andrew Prudhomme
Initial Concept Base: