From c310cd131f261c5f1f5dc27437993b2954f18cdd Mon Sep 17 00:00:00 2001 From: Radoslaw Smigielski Date: Mon, 5 Mar 2018 12:43:34 +0000 Subject: [PATCH] Increase size of Heat HeatMaxJsonBodySize Most of the HTTP servers default max body size to 1MB, Apache, Nginx. That default value is ok as long as users mostly get data from server but when something needs to be uploaded, 1MB limit is often not enough. This is what we see with Heat and some of the large templates. It's not uncommon that WSGI apps have 10MB+ body size limit, so with the current Heat default value we are still in low range sizes. Original Heat template HeatMaxJsonBodySize default value was 1M and now it will be 4M. There is aslo corresponding change in instack-undercloud where we bumped 'max_template_size' to the same value. Change-Id: I974f6d4adbc08f2960a164b90ebb784ca466e76a Closes-Bug: 1752467 --- puppet/services/heat-base.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/puppet/services/heat-base.yaml b/puppet/services/heat-base.yaml index 102d07a7ea..cb58a041ae 100644 --- a/puppet/services/heat-base.yaml +++ b/puppet/services/heat-base.yaml @@ -118,7 +118,7 @@ parameters: Cron to purge db entries marked as deleted and older than $age - Log destination default: '/dev/null' HeatMaxJsonBodySize: - default: 1048576 + default: 4194304 description: Maximum raw byte size of the Heat API JSON request body. type: number NotificationDriver: