Make heat max_json_body_size configurable
authorDan Prince <dprince@redhat.com>
Fri, 24 Feb 2017 14:51:36 +0000 (09:51 -0500)
committerDan Prince <dprince@redhat.com>
Fri, 24 Feb 2017 15:11:37 +0000 (10:11 -0500)
We need to bump this a bit for the overcloud containers
jobs. This patch makes it configurable and increases the
size for the undercloud.

Related-bug: #1667697

Change-Id: I79319f051747b381f5fa36f8a7fc7f31020bc245

environments/undercloud.yaml
puppet/services/heat-base.yaml

index 0fd0192..2540fbe 100644 (file)
@@ -16,3 +16,4 @@ parameter_defaults:
   NeutronDhcpAgentsPerNetwork: 2
   HeatConvergenceEngine: false
   HeatMaxResourcesPerStack: -1
+  HeatMaxJsonBodySize: 2097152
index b4d314f..e83a9ed 100644 (file)
@@ -99,6 +99,10 @@ parameters:
     description: >
         Cron to purge db entries marked as deleted and older than $age - Log destination
     default: '/dev/null'
+  HeatMaxJsonBodySize:
+    default: 1048576
+    description: Maximum raw byte size of the Heat API JSON request body.
+    type: number
 
 outputs:
   role_data:
@@ -142,6 +146,7 @@ outputs:
         heat::cron::purge_deleted::age: {get_param: HeatCronPurgeDeletedAge}
         heat::cron::purge_deleted::age_type: {get_param: HeatCronPurgeDeletedAgeType}
         heat::cron::purge_deleted::destination: {get_param: HeatCronPurgeDeletedDestination}
+        heat::max_json_body_size: {get_param: HeatMaxJsonBodySize}
       service_config_settings:
         keystone:
           tripleo::profile::base::keystone::heat_admin_domain: 'heat_stack'