| 2013-05-03 18:39:16 |
Clint Byrum |
description |
If I change the flavor (instance type) of my server in an update to my stack, I expect it to be replaced. However, I expect that it will be replaced by:
* create new server
* delete old server
However, Heat currently does it the other way
* delete old server
* create new server
This just seems backwards. |
If I change the flavor (instance type) of my server in an update to my stack, I expect it to be replaced. However, I expect that it will be replaced by:
* create new server
* update dependent resources
* delete old server
However, Heat currently does it the other way
* delete old server
* create new server
* update continues (thus updating dependent resources)
This is quite broken, as if a memcache server is deleted and then re-created any dependent resources will be *down* until that new memcache server reaches the 'active' state (and maybe longer if waitconditions are involved) |
|
