lp://staging/openstack-entropy
- Get this branch:
- bzr branch lp://staging/openstack-entropy
Branch information
Import details
This branch is an import of the HEAD branch of the Git repository at https://github.com/stackforge/entropy.git.
Last successful import was .
Recent revisions
- 85. By Robert Collins <email address hidden>
-
Next version is 0.2
pbr pre-versioning causes current sdist to have versions leading up to 0.1, but
that is already released - we should be leading up to 0.2.Change-Id: Ia7860bf4588dae
b19fc0a75c7f914 e6b11c4ccae - 84. By Pranesh
-
Add unittests for entropy
Added run_tests.sh, taken shamelessly from taskflow.
Change-Id: I39b9cfa106c062
96b917077cc3ef9 3dbf5a9a03b - 83. By Pranesh
-
Finish changes to stop an engine
Added a call to stop all react scripts, by passing all known routing
keys to the react_killer function. Then stop the threadpool executor.
Finally, Raise a known exception to stop the watchdog thread. This
will throw an ugly traceback, but will shutdown the engine
gracefully.Also made minor changes to the example react.json, to change the log
format. Knowing the time a log was printed is useful.Change-Id: Ibed06f79547312
d188feb499f937e b5390d60c3e - 82. By Pranesh
-
Add callbacks for futures
Added callbacks for the known futures (react scripts, scheduler,
serializer). This will help us debug known long-lasting futures
easily. Define one function called future_callback, and use
functools to pass arguments to the callbacks to determine type
of future, etcChange-Id: I579a41e9273656
8535ce3f64c5507 ac5224d5a62 - 81. By Pranesh
-
Add logic to stop repair scripts
When watchdog detects that repair script(s) have been killed, get
a list of scripts to nuke and pass to stop_repair_scripts. Then,
get its routing key(s), and send a message from a special user to
any queue listening on those keys.Modified an example repair script to show how it could be killed,
but need a more concrete way that that. For now, messages from
'react_killer' will raise the RepairStoppedException, which will
stop react scriptsModified the example engine cfg to have some details about the
kombu connection to use.Implements blueprint kill-repair-scripts
Change-Id: I67e15e9b9ebb5d36c5cb0e01995bc 95f7a73b3dd - 80. By Pranesh
-
Store routing_keys in a dict instead of set
This will let us keep track of which react script uses what routing
key. We will lose the set property, but that is immaterial because
the system will be in trouble anyway, if there are duplicate keysChange-Id: I89299fcb7dfbe7
ab4d7b2d1df9c1c b001489fd5f - 79. By Pranesh
-
Separate out adding and deleting repair scripts
Currently, any change in the repair cfg is considered as a new
react script being registered. To change that add a _get_repairs
function, and form a list of audits to create/nuke.Change-Id: I5c039f0fee3ef7
9e864493ace9cde 366dc87a381 - 78. By Pranesh
-
Add an unregister repair option
Added a parser and function to unregister repair scripts. Remove
the repair script from the backend repair cfg, and watchdog will
catch it in the engine.Change-Id: I7b93ca7e5eb443
0b7c9502c8dd84a f75b2a9fae3 - 77. By Pranesh
-
Add some exceptions and logging around serializer
Added a serializer exception to raise if the serializer fails, to
replace the generic Exception we raise now.Added a logging statement to another exit point to provide some
more informationChange-Id: I20d58ce8d9d943
f957f491fdf2c01 516d3975870
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)