Increase Mistral Task Size limit

When selecting environments to deploy from the UI, every environment
filename gets added individually to 'environments' key in the Mistral
environment. Apparently it means we hit the Mistral execution size
limit pretty quickly.

This isn't needed for the CLI at this point because it bunches all the
environment files together into one big "user-environments.yaml" file,
for backwards-compabitility reasons.

Note that this Mistral value seems to affect both input and output for
task execution, which is why this patch was initially created as a
prerequisite for Ia9d2312e942229b659cfc65d4c370874e87f44da.

Change-Id: I24453b6d83171860065b050f437602e1f655d8b8
Closes-Bug: #1640815
(cherry picked from commit 4ee68a5229)
This commit is contained in:
Julie Pichon 2016-07-28 10:56:01 +01:00
parent a5ab73f1d6
commit 9b22c1072c
1 changed files with 1 additions and 0 deletions

View File

@ -489,6 +489,7 @@ mistral::keystone::auth::password: {{UNDERCLOUD_MISTRAL_PASSWORD}}
mistral::keystone::auth::tenant: 'service'
mistral::engine::older_than: 2880
mistral::engine::evaluation_interval: 120
mistral::engine::execution_field_size_limit_kb: 4096
# Zaqar
zaqar::keystone::authtoken::project_name: 'service'