[one-users] the synchronous problem between the cancel operation and tm_delete.sh for lxc driver

[Ruben S. Montero]

Hi Simon,

You are right, probably the best way to handle this is to go for the
synchronous delete operation.

THANKS for your feedback :)

Ruben


On Mon, Dec 17, 2012 at 5:50 AM, Simon Boulet <simon at nostalgeek.com> wrote:

> One note, however, it seems the only way for a user to cancel /delete a
> Powered off VM is to issue a delete action. If we make the delete action
> ADMIN-only, we would need to make the cancel action possible for VMs in
> Poweroff state (currently not possible).
>
> Simon
>
>
> On Sun, Dec 16, 2012 at 1:10 PM, Simon Boulet <simon at nostalgeek.com>wrote:
>
>> Hi,
>>
>>
>> On Thu, Dec 6, 2012 at 1:48 PM, Ruben S. Montero <
>> rsmontero at opennebula.org> wrote:
>>
>>> This seems to be confusing, we are thinking of moving the delete
>>> operation to the ADMIN set (so you need admin permissions to delete)
>>> and so force users to use the safer cancel operation... Any thoughts?
>>>
>>
>> Not a bad idea to restrict cancel action to the ADMIN. However, I still
>> think the VMM cancel action should be executed first, before the TM delete
>> action, and the TM delete should be executed last, independently of the VMM
>> cancel success or failure.
>>
>> Simon
>>
>
>


-- 
Ruben S. Montero, PhD
Project co-Lead and Chief Architect
OpenNebula - The Open Source Solution for Data Center Virtualization
www.OpenNebula.org | rsmontero at opennebula.org | @OpenNebula
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20121220/bbc8e20a/attachment-0002.htm>