Difference between revisions of "Entropy"
(→Conceptual Example) |
(→Conceptual Example) |
||
(2 intermediate revisions by the same user not shown) | |||
Line 11: | Line 11: | ||
We're working on uploading entropy to [http://pypi.python.org Pypi.] You'll need to run entropy manually till then. | We're working on uploading entropy to [http://pypi.python.org Pypi.] You'll need to run entropy manually till then. | ||
<pre> | <pre> | ||
+ | # install | ||
git clone https://github.com/stackforge/entropy.git | git clone https://github.com/stackforge/entropy.git | ||
+ | cd entropy | ||
+ | python setup.py install (might need sudo). | ||
− | + | # Pick out entropy/entropy/examples. The example cfgs might need a few minor changes to work for you. | |
+ | |||
+ | Terminal 1: | ||
+ | # start an engine. | ||
cd entropy/ | cd entropy/ | ||
− | + | python entropy start-engine -n test -c examples/cfg/test.cfg | |
− | |||
− | |||
− | python entropy start-engine -n test - | ||
− | + | Terminal 2: | |
− | + | tail -f examples/logs/entropy.log | |
− | tail -f entropy.log | ||
− | + | Terminal 3: | |
− | python entropy register-repair -n | + | python entropy register-repair -n demo -c examples/repair/react.json -e test |
− | python entropy register-audit -n | + | python entropy register-audit -n demo -c examples/audit/audit.json -e test |
+ | # running the above commands will create a demo.log in examples/logs | ||
+ | Terminal 4: | ||
+ | tail -f examples/logs/demo.log | ||
</pre> | </pre> | ||
Line 46: | Line 51: | ||
'''IRC:''' You will also find us in <code>#openstack-entropy</code> on [http://freenode.net/ freenode] | '''IRC:''' You will also find us in <code>#openstack-entropy</code> on [http://freenode.net/ freenode] | ||
+ | |||
+ | '''Launchpad:''' https://launchpad.net/openstack-entropy | ||
== Todo == | == Todo == |
Latest revision as of 01:19, 8 June 2014
Revised on: 6/8/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.
# install git clone https://github.com/stackforge/entropy.git cd entropy python setup.py install (might need sudo). # Pick out entropy/entropy/examples. The example cfgs might need a few minor changes to work for you. Terminal 1: # start an engine. cd entropy/ python entropy start-engine -n test -c examples/cfg/test.cfg Terminal 2: tail -f examples/logs/entropy.log Terminal 3: python entropy register-repair -n demo -c examples/repair/react.json -e test python entropy register-audit -n demo -c examples/audit/audit.json -e test # running the above commands will create a demo.log in examples/logs Terminal 4: tail -f examples/logs/demo.log
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
Launchpad: https://launchpad.net/openstack-entropy
Todo
https://etherpad.openstack.org/p/openstack-entropy