Matt Riedemann 276130c6d1 Add note about reschedules and num_attempts in filter_properties ... The "retry" entry in filter_properties is not set if reschedules are disabled, which happens in these cases: 1. [scheduler]/max_attempts=1 2. The server is forced to a specific host and/or node. More times than I'd like to admit, I've had to re-learn that filter_properties['retry']['num_attempts'] will always be >1 in conductor build_instances during a reschedule because if reschedules are disabled, the compute service aborts the build on failure and we don't even get back to conductor. This change adds a note since it's hard to keep in your head how the retry logic is all tied together from the API, superconductor, compute and cell conductor during a reschedule scenario. Change-Id: I83536b179000f41f9618a4b6f2a16b4440fd61ba Related-Bug: #1781286		2018-07-14 12:38:04 +00:00
..
tasks	Add user_id to RequestSpec	2018-05-01 11:08:43 -04:00
__init__.py	Remove conductor local api:s and 'use_local' config option	2016-10-18 14:26:06 +02:00
api.py	Merge "conf: Remove '[conductor] topic' opt"	2018-03-13 08:00:43 +00:00
manager.py	Add note about reschedules and num_attempts in filter_properties	2018-07-14 12:38:04 +00:00
rpcapi.py	Merge "conf: Remove '[conductor] topic' opt"	2018-03-13 08:00:43 +00:00