DaanHoogland commented on pull request #5457: URL: https://github.com/apache/cloudstack/pull/5457#issuecomment-1035025681
> What do you think? Should we return to the initial idea? And just block the deletion of the VM, until we have a solution to de-assign the VM from a backup offering without removing the backups? Yes, sorry to have been a hassle. I think backups should be first class citizens that can be saved, moved around, started as VM or deleted independent of the initial VM they where a backup of, and I thought that was the case. This is why I was inclined on the assigning on delete scheme. If that is not possible preventing the deletion of a VM makes sense. I do think it is prone to improvement though. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
