Heat template size restriction

Bug #1936677 reported by Kevin Carter
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
In Progress
Undecided
Unassigned

Bug Description

When running a deployment the heat template size could be too small to support a production set of templates. We need to increase the acceptable size and potentially add a way to arbitrarily set config within ephemeral heat so that operators can resolve these types of issues on their own without requiring changes to the core framework.

Example error: https://paste.opendev.org/show/807509

Revision history for this message
Rabi Mishra (rabi) wrote :

This restriction is intentional as we store every template in the database[1] and will have performance implications, if we allow them to be arbitrarily changed. IMO, 0.5 MB for a single template is actually on the higher side.

Just wondering as in the patch proposed by James, what has changed with ephemeral heat that template sizes have become bigger suddenly or we used to configure that before ephemeral heat?

The paste in the bug report looks like a different error.

Revision history for this message
Kevin Carter (kevin-carter) wrote :

Sorry about that - this is the correct paste which contained the error: https://paste.opendev.org/show/807367

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to python-tripleoclient (master)
Changed in tripleo:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on python-tripleoclient (master)

Change abandoned by "Bogdan Dobrelya <email address hidden>" on branch: master
Review: https://review.opendev.org/c/openstack/python-tripleoclient/+/801955

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.