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 template.id resulting in it being stored when we do backup_stack.store and new_stack.store.
Ideally, we should be keeping one copy of old template when the stack is updated. With this we have the history of templates updated over time. 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 for inspection etc. when the stack admin needs it. Please share your thoughts! - Anant _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
