When configured for superconductor mode, which is the default,
nova-compute can't reach the MQ for nova-scheduler so there is
no point in even enabling the track_instance_changes code since
it's a waste of time as the scheduler will never get the message.
Change-Id: I2662ebd47323428b403d3c2236bec78f1fb1050f
... | ... |
@@ -440,6 +440,9 @@ function create_nova_conf { |
440 | 440 |
local db="nova_cell1" |
441 | 441 |
else |
442 | 442 |
local db="nova_cell0" |
443 |
+ # When in superconductor mode, nova-compute can't send instance |
|
444 |
+ # info updates to the scheduler, so just disable it. |
|
445 |
+ iniset $NOVA_CONF filter_scheduler track_instance_changes False |
|
443 | 446 |
fi |
444 | 447 |
|
445 | 448 |
iniset $NOVA_CONF database connection `database_connection_url $db` |
... | ... |
@@ -843,6 +846,9 @@ function start_nova_compute { |
843 | 843 |
cp $compute_cell_conf $NOVA_CPU_CONF |
844 | 844 |
# FIXME(danms): Should this be configurable? |
845 | 845 |
iniset $NOVA_CPU_CONF workarounds disable_group_policy_check_upcall True |
846 |
+ # Since the nova-compute service cannot reach nova-scheduler over |
|
847 |
+ # RPC, we also disable track_instance_changes. |
|
848 |
+ iniset $NOVA_CPU_CONF filter_scheduler track_instance_changes False |
|
846 | 849 |
iniset_rpc_backend nova $NOVA_CPU_CONF DEFAULT "nova_cell${NOVA_CPU_CELL}" |
847 | 850 |
fi |
848 | 851 |
|