nodepool/nodepool
Tobias Henkel e4f245eb13
Add extra safety belt when reusing a node
When reusing a node we lock it but don't check if the state is still
ready. There are probably few to no possibilities how this can happen.
But it's better to guarantee this condition than to think that this
should be ok.

Change-Id: I365de6accb28b538dae5ff1dfb6c4a9966e50b01
2018-11-26 19:38:10 +01:00
..
cmd status: add pool column to nodepool list output 2018-07-15 23:07:22 +00:00
driver Add extra safety belt when reusing a node 2018-11-26 19:38:10 +01:00
tests Update node during lockNode 2018-11-26 19:37:41 +01:00
__init__.py Initial commit 2013-08-15 09:47:23 -07:00
builder.py Add metric for image build result 2018-09-05 09:39:47 +02:00
config.py Merge "builder: support setting diskimage env-vars in secure configuration" 2018-07-23 16:04:00 +00:00
exceptions.py Fix relaunch attempts when hitting quota errors 2018-07-06 08:41:02 +02:00
launcher.py Update node during lockNode 2018-11-26 19:37:41 +01:00
logconfig.py Replace shade and os-client-config with openstacksdk. 2018-07-14 08:44:03 -05:00
nodeutils.py Reduce socket connect timeout in nodescan 2018-10-09 11:17:51 +02:00
provider_manager.py builder: do not configure provider that doesn't manage images 2018-07-15 23:10:05 +00:00
stats.py Support node caching in the nodeIterator 2018-11-08 11:01:06 +01:00
status.py status: add pool column to nodepool list output 2018-07-15 23:07:22 +00:00
task_manager.py Use openstacksdk submit_task 2018-11-09 07:28:38 +11:00
version.py Fix nodepool --version 2015-02-06 12:09:52 -08:00
webapp.py webapp: fix browser return 2018-06-07 18:47:06 +10:00
zk.py Update node during lockNode 2018-11-26 19:37:41 +01:00