From dc9fcd3c4a8b3bf040c61616c689588ab6c03486 Mon Sep 17 00:00:00 2001 From: Emilien Macchi Date: Wed, 14 Feb 2018 17:38:48 -0800 Subject: [PATCH] Align zaqar max_messages_post_size with undercloud When deploying a containerized undercloud, we need the same configuration as we used to have in instack-undercloud. For max_messages_post_size, we used to have 1048576 due to the high size of the messages with config-download. Let's sync the config here, so we can deploy an overcloud with config-download when a containerized undercloud is used. Change-Id: Ib43c811d9ea4e71558c15c78cfb9999f738b8098 --- puppet/services/zaqar-api.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/puppet/services/zaqar-api.yaml b/puppet/services/zaqar-api.yaml index d48d7b9477..c002c8cbc2 100644 --- a/puppet/services/zaqar-api.yaml +++ b/puppet/services/zaqar-api.yaml @@ -117,6 +117,7 @@ outputs: zaqar::wsgi::apache::ssl: {get_param: EnableInternalTLS} zaqar::wsgi::apache::bind_host: {get_param: [ServiceNetMap, ZaqarApiNetwork]} zaqar::message_pipeline: 'zaqar.notification.notifier' + zaqar::max_messages_post_size: 1048576 zaqar::unreliable: true zaqar::wsgi::apache::servername: str_replace: