Re: [one-users] Old Vms directory not deleted - DB compromised

2012-10-11 Thread Duverne, Cyrille
Hello Carlos, This worked as a charm, but I also had to update the STATE attribute from 2 to 1, to put the image in READY state and allow me to remove it from sunstone :) Thanks a lot. Cyrille Blog : http://blog.cduverne.com Twitter : @CydsWorld "Imagination is more important than Knowledge" Alb

Re: [one-users] Old Vms directory not deleted - DB compromised

2012-10-04 Thread Carlos Martín Sánchez
Hi, The VMs themselves are not deleted, just moved to the DONE state. You can still execute a onevm show and see the information of deleted VMs. To be consistent with this, we also leave the directories and log files (note that the disks and checkpoint files are stored in the system datastore).

Re: [one-users] Old Vms directory not deleted - DB compromised

2012-10-03 Thread Duverne, Cyrille
Hello Carlos, Thanks a lot for your feedback. Regarding the Hooks, it works like a charm. But you said that it was normal to not delete the old directory of destroyed VMs, why ? Regarding the reserved image, I haven't any VM in any state which is using it... :) Kind regards CyD Blog : http://b

Re: [one-users] Old Vms directory not deleted - DB compromised

2012-10-02 Thread Carlos Martín Sánchez
Hi, On Mon, Oct 1, 2012 at 2:42 PM, Duverne, Cyrille < cyrille.duve...@euranova.eu> wrote: > > I've noticed that when I delete a VM, the directory > /var/lib/one/one-data/$VMID is left behind and never deleted. > Is this normal ? > I've seen this behaviour in 3.2, but it's still happening in 3.8 >

[one-users] Old Vms directory not deleted - DB compromised

2012-10-01 Thread Duverne, Cyrille
Hello dear community, I've noticed that when I delete a VM, the directory /var/lib/one/one-data/$VMID is left behind and never deleted. Is this normal ? I've seen this behaviour in 3.2, but it's still happening in 3.8 And on another side, I have an image that can't be deleted, Sunstone says that