PaulAngus commented on issue #4902: URL: https://github.com/apache/cloudstack/issues/4902#issuecomment-901013593
As mentioned by Wido and myself, data disks are considered first-class citizens. Therefore the first step when destroying a VM which has data disks attached, is to detach them. Obviously it is perfectly valid for the user to destroy them as well, either via an argument in the initial API command, as a separate API command, or via an option in the UI which calls the appropriate API(s). Therefore, scenarios (1) and (2) should start 'detach data disks, destroy VM ... '. Scenario (3) is then simply 'Expunge VM'. There then are four more actions: - destroy data disk(s) - recover data disks(s) - expunge data disk(s) - attach data disk(s) (to recovered VM or some other VM) As Daan notes, 'As Is' VMs are a special case, where the data disk will often be considered a part of the VM. One could argue either way. One way of 'solving it' is to make it the operator's problem and add a global or even account setting to choose whether data disks are automatically destroyed for an 'As Is' VM or not. -- 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]
