On 30-Jul-14 23:24, Zane Bitter wrote:
On 30/07/14 02:21, Anant Patil wrote:
On 28-Jul-14 22:37, Clint Byrum wrote:
Excerpts from Zane Bitter's message of 2014-07-28 07:25:24 -0700:
On 26/07/14 00:04, Anant Patil wrote:
When the stack is updated, a diff of updated template and current
On 28-Jul-14 22:37, Clint Byrum wrote:
Excerpts from Zane Bitter's message of 2014-07-28 07:25:24 -0700:
On 26/07/14 00:04, Anant Patil wrote:
When the stack is updated, a diff of updated template and current
template can be stored to optimize database. And perhaps Heat should
have an API to
On 30/07/14 02:21, Anant Patil wrote:
On 28-Jul-14 22:37, Clint Byrum wrote:
Excerpts from Zane Bitter's message of 2014-07-28 07:25:24 -0700:
On 26/07/14 00:04, Anant Patil wrote:
When the stack is updated, a diff of updated template and current
template can be stored to optimize database.
On 26/07/14 00:04, Anant Patil wrote:
Hi,
When we do a stack update, I see that there are 2 copies of raw_template
stored in database for each update. For n updates there are 2n + 1
entries of raw_template in database. Is this expected or is it a bug?
When I dug more into it, I see that the
Excerpts from Zane Bitter's message of 2014-07-28 07:25:24 -0700:
On 26/07/14 00:04, Anant Patil wrote:
When the stack is updated, a diff of updated template and current
template can be stored to optimize database. And perhaps Heat should
have an API to retrieve this history of templates
Hi,
When we do a stack update, I see that there are 2 copies of raw_template
stored in database for each update. For n updates there are 2n + 1
entries of raw_template in database. Is this expected or is it a bug?
When I dug more into it, I see that the deep copy of template is not
copying the