Open Stack

After looking into Nova code base, I found there is surely a soft_delete() method in the ComputeDriver() class. Furthermore,
Xenapi (and only Xenapi) has implemented this method, which finally applies a hard_shutdown_vm() operation to the instance to be deleted.
If I understand it correctly, it means the instance is in fact shutdown, instead of being deleted. Later, the user can decide whether to restore it or not.

My question is that, when and how is the soft_deleted instance truly deleted? A user needs to trigger a real delete operation on it explicitly, doesn't he?

Not for sure why other drivers, especially libvirt, did not implement such a feature...

Thanks~

-----Original Message-----
From: John Garbutt [mailto:john at johngarbutt.com] 
Sent: Thursday, March 06, 2014 8:13 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Nova][Cinder] Feature about volume delete protection

On 6 March 2014 08:50, zhangyu (AI) <zhangyu11 at huawei.com> wrote:
> It seems to be an interesting idea. In fact, a China-based public 
> IaaS, QingCloud, has provided a similar feature to their virtual 
> servers. Within 2 hours after a virtual server is deleted, the server owner can decide whether or not to cancel this deletion and re-cycle that "deleted" virtual server.
>
> People make mistakes, while such a feature helps in urgent cases. Any idea here?

Nova has soft_delete and restore for servers. That sounds similar?

John

>
> -----Original Message-----
> From: Zhangleiqiang [mailto:zhangleiqiang at huawei.com]
> Sent: Thursday, March 06, 2014 2:19 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: [openstack-dev] [Nova][Cinder] Feature about volume delete 
> protection
>
> Hi all,
>
> Current openstack provide the delete volume function to the user.
> But it seems there is no any protection for user's delete operation miss.
>
> As we know the data in the volume maybe very important and valuable.
> So it's better to provide a method to the user to avoid the volume delete miss.
>
> Such as:
> We can provide a safe delete for the volume.
> User can specify how long the volume will be delay deleted(actually deleted) when he deletes the volume.
> Before the volume is actually deleted, user can cancel the delete operation and find back the volume.
> After the specified time, the volume will be actually deleted by the system.
>
> Any thoughts? Welcome any advices.
>
> Best regards to you.
>
>
> ----------
> zhangleiqiang
>
> Best Regards
>
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev