summaryrefslogtreecommitdiffstats
path: root/environments/low-memory-usage.yaml
AgeCommit message (Collapse)AuthorFilesLines
2017-05-21Change database sync timeout from 300 to 900 in low-memory-usage environment ↵Or Idgar1-0/+2
file. During a deployment on lower spec systems, the "db sync" can take longer than five minutes. The solution is to increase the default value of DatabaseSyncTimeout from 300 to 900 by using the environment file "low-memory-usage.yaml". Change-Id: I6463dbdd4dfe1d6f2dd283211cc496fe3a628fb0 Closes-bug: #1689318
2017-02-22Increase apache ServerLimit and workers to 100Sagi Shnaidman1-2/+2
Increase apache serverlimit and maxrequestworkers to 100 in low-memory-usage template. We have been reaching the limit with all the OpenStack services that we run in WSGI. Increasing the number will help us to promote packages in TripleO CI. Change-Id: I3f71f279a8dfaee9db5f5d1091ad079d9170de1f
2016-11-11Increasing neutron timeout for low memory usageArx Cruz1-0/+3
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-09-26Add metricd workers support in gnocchiCarlos Camacho1-0/+1
Depending on the environment, gnocchi workers uses several controller resources RAM/CPU, this option makes it configurable. Also, configured to 1 in environments/low-memory-usage.yaml which will reduce the service footprint in i.e. CI Change-Id: Ia008b32151f4d8fec586cf89994ac836751b7cce Closes-bug: #1626473
2016-09-21Provide for RAM-constrained environmentsJiri Stransky1-0/+14
We hit problems in environments which don't have a lot of RAM (e.g. dev envs, could be also CI) that Apache ate too much memory due to too many worker processes being spawned. This commit allows customizing the Apache MaxRequestWorkers and ServerLimit directives via Heat parameters. The default stays 256 as that's the default in the Puppet module, to be suited for production environments with powerful machines. Also low-memory-usage.yaml environment file is added, which can be used to make dev/test/CI overclouds less memory hungry, where the limits are now set to 32. Change-Id: Ibcf1d9c3326df8bb5b380066166c4ae3c4bf8d96 Co-Authored-By: Carlos Camacho <ccamacho@redhat.com> Closes-Bug: #1619205