2016-09-21 13:53:19 +02:00
|
|
|
# Lower the memory usage of overcloud.
|
|
|
|
parameter_defaults:
|
|
|
|
CinderWorkers: 1
|
|
|
|
GlanceWorkers: 1
|
|
|
|
HeatWorkers: 1
|
|
|
|
KeystoneWorkers: 1
|
|
|
|
NeutronWorkers: 1
|
|
|
|
NovaWorkers: 1
|
|
|
|
SaharaWorkers: 1
|
|
|
|
SwiftWorkers: 1
|
2016-09-22 13:08:58 +02:00
|
|
|
GnocchiMetricdWorkers: 1
|
2016-09-21 13:53:19 +02:00
|
|
|
|
2017-02-21 22:18:01 +02:00
|
|
|
ApacheMaxRequestWorkers: 100
|
|
|
|
ApacheServerLimit: 100
|
Increasing neutron timeout for low memory usage
We are noticing several tests failing in our low memory environment
because of timeout in neutron requests.
As an example the test
tempest.api.compute.servers.test_server_actions.ServerActionsTestJSON
fails because it requests to plug a vif, and send request to neutron,
which responds in more than neutron_url_timeout, and since the option
vif_plugging_is_fatal is set to True as default, the test fails.
Shortly thereafter, checking in neutron log you can see the request,
returning with the proper status, after more than neutron_url_timeout,
however, it's already too late once nova already marked the instance
with error status, and so the test fails.
Closes-Bug: #1641135
Change-Id: If0991c114f199490ac0deb71eb569a42d4711359
2016-10-24 16:27:11 +02:00
|
|
|
|
|
|
|
ControllerExtraConfig:
|
|
|
|
'nova::network::neutron::neutron_url_timeout': '60'
|
2017-05-09 08:46:46 +00:00
|
|
|
|
|
|
|
DatabaseSyncTimeout: 900
|
2018-02-14 18:06:28 +00:00
|
|
|
|
|
|
|
# Override defaults to get HEALTH_OK with 1 OSD (for testing only)
|
|
|
|
CephPoolDefaultSize: 1
|
|
|
|
CephPoolDefaultPgNum: 32
|