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.
Reviewed: https:/ /review. openstack. org/348216 /git.openstack. org/cgit/ openstack/ instack- undercloud/ commit/ ?id=4ee68a5229b ed653a669826e45 108d25f207c024
Committed: https:/
Submitter: Jenkins
Branch: master
commit 4ee68a5229bed65 3a669826e45108d 25f207c024
Author: Julie Pichon <email address hidden>
Date: Thu Jul 28 10:56:01 2016 +0100
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 nts.yaml" file, compabitility reasons.
environment files together into one big "user-environme
for backwards-
Note that this Mistral value seems to affect both input and output for b659cfc65d4c370 874e87f44da.
task execution, which is why this patch was initially created as a
prerequisite for Ia9d2312e942229
Change-Id: I24453b6d831718 60065b050f43760 2e1f655d8b8
Closes-Bug: #1640815