Jay Lau 4e7fc7ac56 Enable retry when there are multiple force hosts/nodes ...

Currently, when there are forced hosts/nodes in a scheduler request,
retry will be disabled. This is not right as there might be multiple
forced hosts/nodes, we should not disable retry for such case.

Closes-Bug: #1343946

DocImpact
1) If there is only one force host/node, then retry filter will not
take effect for such case.
2) If there are multiple force hosts/nodes, retry filter will help
retry on the force hosts/nodes if there are VM boot failure.

Change-Id: I6831cab70a70ebbb9609689d9132c731ff84c665

2015-02-23 04:33:24 +08:00

..

client

Merge "Create Scheduler client methods for aggregates"

2015-03-06 13:47:03 +00:00

filters

Modify filters so they can look to HostState

2015-03-06 22:38:20 +00:00

weights

Switch to using oslo_* instead of oslo.*

2015-02-06 06:03:10 -05:00

__init__.py

Improve hacking rule to avoid author markers

2014-05-05 14:35:20 +02:00

caching_scheduler.py

Add a caching scheduler driver

2014-02-26 13:53:07 +00:00

chance.py

Switch to using oslo_* instead of oslo.*

2015-02-06 06:03:10 -05:00

driver.py

Switch to using oslo_* instead of oslo.*

2015-02-06 06:03:10 -05:00

filter_scheduler.py

Display host chosen for instance by scheduler

2015-02-27 14:17:07 +00:00

host_manager.py

Replace RPC topic-based service queries with binary-based in scheduler

2015-03-09 08:21:33 -07:00

ironic_host_manager.py

Use oslo.log

2015-02-22 07:56:40 -05:00

manager.py

Add update and delete _aggregate() method to the Scheduler RPC API

2015-03-05 22:40:31 +01:00

rpcapi.py

Add update and delete _aggregate() method to the Scheduler RPC API

2015-03-05 22:40:31 +01:00

scheduler_options.py

Use oslo.log

2015-02-22 07:56:40 -05:00

utils.py

Enable retry when there are multiple force hosts/nodes

2015-02-23 04:33:24 +08:00