The new template is defined in line 4 as an extension to the previous template.
It is run on an Agilent 2100 Bioanalyzer both with and without previous template switching amplifications.
Specifically, a resource which is in previous template and is not in new template is deleted, a resource which is not in previous template and is in new template is created, a resource which is changed from previous template to new template is created after deletion or updated.
When users call a stack update API, Heat checks a difference between a new template and a previous template.
When we update a stack, orchestration functions check a difference between previous template and new template, then create, delete or update resources to fill up the difference.
In case of stack update, orchestration functions check a difference between previous template and new template, then create, delete or update virtual resources to fill up the difference.
But in this example case, an actual environment is different from a previous template, so that there is a possibility of unexpected behavior.
- Differences between a previous template and a new template: virtual resources numbers are same but 1 VM, 1 virtual Layer 2 network and 1 logical router in a previous template are removed and 1 VM, 1 virtual Layer 2 network and 1 logical router are newly added.
Current SearchMonkey developers and partners will be happy to know that apps built using the previous template will automatically work with the new template, but a one-page best practices document will accompany developer materials to help them provide an optimal user experience.
These suggestions are consistent with the results in previous template process studies using SU-8 to obtain nanoshell-based 2D inverse patterns [43, 44], which have reported that the 2D inverse structural features can be changed depending on an intentional load and how the template was removed during baking process.
