Currently volumes for a given VM are tied to that vm in VMOrchestrationParams. This ties the volume to the VM and as a result when we update the heat stack, the volume block gets generated again. This is not a problem, since volume sizes are not updatable; however if we ever need to add this feature, the way we write out updated heat stack should change. Namely, we should pick up the definition of the volume from the existing one, so not to re-create it.
Currently volumes for a given VM are tied to that vm in
VMOrchestrationParams. This ties the volume to the VM and as a result when we update the heat stack, the volume block gets generated again. This is not a problem, since volume sizes are not updatable; however if we ever need to add this feature, the way we write out updated heat stack should change. Namely, we should pick up the definition of the volume from the existing one, so not to re-create it.