is clustering and that is probably outside of this scope. Even if I
> was going to do some kind of OS upgrade and wanted to reuse the data disk on
> another instance I would probably detach, then reattach to the new instance.
> Just seems like it can get messy quick, if a lot of users d
if I
was going to do some kind of OS upgrade and wanted to reuse the data disk on
another instance I would probably detach, then reattach to the new instance.
Just seems like it can get messy quick, if a lot of users delete their
instances and leave all these orphaned data disks behind.
It wou
wrote:
> What was the logic behind leaving the disks orphaned?
>
>> From: sanjeev.neelar...@citrix.com
>> To: dev@cloudstack.apache.org
>> Subject: RE: Orphaned Data Disks
>> Date: Thu, 29 Jan 2015 05:30:49 +
>>
>> That is expected behavior. Right now
What was the logic behind leaving the disks orphaned?
> From: sanjeev.neelar...@citrix.com
> To: dev@cloudstack.apache.org
> Subject: RE: Orphaned Data Disks
> Date: Thu, 29 Jan 2015 05:30:49 +
>
> That is expected behavior. Right now there is no option to chang
: Orphaned Data Disks
Has anyone noticed that after destroying and expunging an instance that has a
data disk attached, cloudstack leaves the datadisk orphaned? If so is this
expected behavior, and if so is there an option to change it?
Has anyone noticed that after destroying and expunging an instance that has a
data disk attached, cloudstack leaves the datadisk orphaned? If so is this
expected behavior, and if so is there an option to change it?
