Difference between revisions of "Entropy"
(→Conceptual Example) |
(→Conceptual Example) |
||
| Line 12: | Line 12: | ||
git clone https://github.com/stackforge/entropy.git | git clone https://github.com/stackforge/entropy.git | ||
| − | + | <pre> | |
| − | terminal 1: | + | terminal 1: |
| − | cd entropy/ | + | cd entropy/ |
| − | mkdir entropy/logs | + | mkdir entropy/logs |
mkdir entropy/audit <br/> | mkdir entropy/audit <br/> | ||
mkdir entropy/repair <br/> | mkdir entropy/repair <br/> | ||
python entropy start-engine -n test -a entropy/cfg/audit.cfg -r entropy/cfg/repair.cfg -l entropy/logs/entropy.log <br/> | python entropy start-engine -n test -a entropy/cfg/audit.cfg -r entropy/cfg/repair.cfg -l entropy/logs/entropy.log <br/> | ||
| − | + | terminal 2: | |
| − | terminal 2: | ||
cd entropy/entropy/logs | cd entropy/entropy/logs | ||
tail -f entropy.log | tail -f entropy.log | ||
| − | + | ||
| − | terminal 3: | + | terminal 3: |
python entropy register-repair -n vmbooter -c entropy/repair/vmbooter.json -e test | python entropy register-repair -n vmbooter -c entropy/repair/vmbooter.json -e test | ||
python entropy register-audit -n vmbooter -c entropy/audit/vmbooter.json -e test | python entropy register-audit -n vmbooter -c entropy/audit/vmbooter.json -e test | ||
| + | |||
| + | </pre> | ||
== Design == | == Design == | ||
Revision as of 07:37, 9 April 2014
Revised on: 4/9/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
We're working on uploading entropy to Pypi. You'll need to run entropy manually till then.
git clone https://github.com/stackforge/entropy.git
terminal 1: cd entropy/ mkdir entropy/logs mkdir entropy/audit <br/> mkdir entropy/repair <br/> python entropy start-engine -n test -a entropy/cfg/audit.cfg -r entropy/cfg/repair.cfg -l entropy/logs/entropy.log <br/> terminal 2: cd entropy/entropy/logs tail -f entropy.log terminal 3: python entropy register-repair -n vmbooter -c entropy/repair/vmbooter.json -e test python entropy register-audit -n vmbooter -c entropy/audit/vmbooter.json -e test
Design
Contributors
- Pranesh Pandurangan (Yahoo!)
- Joshua Harlow (Yahoo!)
- Mike Wilson
- Debojyoti Dutta (Cisco)
- You!!
Join us!
IRC: You will also find us in #openstack-entropy on freenode
Todo
https://etherpad.openstack.org/p/openstack-entropy
