Currently we log all template resources every time any API call
happens which indirectly creates an Environment object, which
results in a lot of duplicate bloat in the heat logs (not even
at debug level..)
So, instead log all environment resources (e.g those from resource
plugins and the global environment) only when we start the
service, and log user-provided template resources only when we
do the template validation on create/update, for only the root stack,
because we pass a derived subset environment down to all children.
We also switch to using the string representation of the ResourceInfo
objects, as this contains a bit more useful info than the current
log format.
Reviewed: https:/ /review. openstack. org/227441 /git.openstack. org/cgit/ openstack/ heat/commit/ ?id=5d6234ecf64 650b0eb7bd92eb5 30e899ff061457
Committed: https:/
Submitter: Jenkins
Branch: master
commit 5d6234ecf64650b 0eb7bd92eb530e8 99ff061457
Author: Steven Hardy <email address hidden>
Date: Thu Sep 24 18:41:34 2015 +0100
Reduce frequency of logging environment resources
Currently we log all template resources every time any API call
happens which indirectly creates an Environment object, which
results in a lot of duplicate bloat in the heat logs (not even
at debug level..)
So, instead log all environment resources (e.g those from resource
plugins and the global environment) only when we start the
service, and log user-provided template resources only when we
do the template validation on create/update, for only the root stack,
because we pass a derived subset environment down to all children.
We also switch to using the string representation of the ResourceInfo
objects, as this contains a bit more useful info than the current
log format.
Change-Id: I20007c1ad6bf8b 1479c1d60a5c392 b8b9e1c06c4
Closes-Bug: #1499330