Revision history [back]

click to hide/show revision 1
initial version

Additional resource required by "REPLACE" update policy

User-data update in HOT template will trigger "REPLACE" when use "heat stack-update" to take change into use. "REPLACE" policy creates a new VM before delete the old one, so it requires double CPU cores to execute "REPLACE" update policy, if the VM uses other resource, eg cinder volume, vNIC, do these resource need double for the period new VM is created but before old VM is deleted?