Browse code

Cut back on the number of workers ran for neutron

The dedicated RPC worker is overkill in single or multinode
devstack deployments. Also metadata API workers was left
default, which meant they were as many as the CPU cores.

Related-bug: 1656386

Change-Id: Ibbf7787dfa48e13a51f961f3e0ee2b8f49964759

Armando Migliaccio authored on 2017/02/03 09:47:00
Showing 2 changed files
... ...
@@ -219,6 +219,7 @@ function configure_neutron_new {
219 219
 
220 220
         iniset $NEUTRON_META_CONF DEFAULT debug $ENABLE_DEBUG_LOG_LEVEL
221 221
         iniset $NEUTRON_META_CONF DEFAULT nova_metadata_ip $SERVICE_HOST
222
+        iniset $NEUTRON_META_CONF DEFAULT metadata_workers $API_WORKERS
222 223
         iniset $NEUTRON_META_CONF agent root_helper_daemon "$NEUTRON_ROOTWRAP_DAEMON_CMD"
223 224
 
224 225
         # TODO(dtroyer): remove the v2.0 hard code below
... ...
@@ -359,6 +359,10 @@ function configure_mutnauq {
359 359
     fi
360 360
 
361 361
     iniset $NEUTRON_CONF DEFAULT api_workers "$API_WORKERS"
362
+    # devstack is not a tool for running uber scale OpenStack
363
+    # clouds, therefore running without a dedicated RPC worker
364
+    # for state reports is more than adequate.
365
+    iniset $NEUTRON_CONF DEFAULT rpc_state_report_workers 0
362 366
 }
363 367
 
364 368
 function create_nova_conf_neutron {
... ...
@@ -788,6 +792,7 @@ function _configure_neutron_metadata_agent {
788 788
 
789 789
     iniset $Q_META_CONF_FILE DEFAULT debug $ENABLE_DEBUG_LOG_LEVEL
790 790
     iniset $Q_META_CONF_FILE DEFAULT nova_metadata_ip $Q_META_DATA_IP
791
+    iniset $Q_META_CONF_FILE DEFAULT metadata_workers $API_WORKERS
791 792
     iniset $Q_META_CONF_FILE AGENT root_helper "$Q_RR_COMMAND"
792 793
     if [[ "$Q_USE_ROOTWRAP_DAEMON" == "True" ]]; then
793 794
         iniset $Q_META_CONF_FILE AGENT root_helper_daemon "$Q_RR_DAEMON_COMMAND"