Difference between revisions of "Entropy"
(→Contributors) |
|||
| Line 1: | Line 1: | ||
'''Revised on:''' {{REVISIONMONTH1}}/{{REVISIONDAY}}/{{REVISIONYEAR}} by {{REVISIONUSER}} | '''Revised on:''' {{REVISIONMONTH1}}/{{REVISIONDAY}}/{{REVISIONYEAR}} by {{REVISIONUSER}} | ||
| − | == | + | == Summary == |
Entropy is a framework to write audit and repair scripts for openstack. It will allow writing cluster-check scripts, and define reactions to the errors/issues these bugs raise. | Entropy is a framework to write audit and repair scripts for openstack. It will allow writing cluster-check scripts, and define reactions to the errors/issues these bugs raise. | ||
| Line 8: | Line 8: | ||
===Conceptual Example=== | ===Conceptual Example=== | ||
| + | |||
| + | == Design == | ||
==Contributors== | ==Contributors== | ||
Revision as of 09:16, 11 February 2014
Revised on: 2/11/2014 by Pranesh Pandurangan
Summary
Entropy is a framework to write audit and repair scripts for openstack. It will allow writing cluster-check scripts, and define reactions to the errors/issues these bugs raise.
Entropy will allow developers to write health checkers without worrying about deployment, setting up a Jenkins, integrating with an emailer, etc. It also allows definition of "reaction" scripts that wait on issues and take well defined actions (file a ticket, mark a hypervisor bad, etc). This automates reacting to failure at one level, and tackles inundating SEs with emails about (probably) minor issues. A potentially more important use is to aggregate failures, notice trends in failures, and developing a database of known failures to make dealing with new ones easier.
Conceptual Example
Design
Contributors
- Pranesh Pandurangan (Yahoo!)
- Joshua Harlow (Yahoo!)
- You!!
