cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-8580) Users should be able to expunge VMs
Date Fri, 14 Aug 2015 09:49:47 GMT


ASF subversion and git services commented on CLOUDSTACK-8580:

Commit 0fcc7297e0b519ffc5ebb8df1d3ab16659bd18fd in cloudstack's branch refs/heads/master from
[;h=0fcc729 ]

Merge pull request #680 from borisroman/CLOUDSTACK-8580

Interface changes related to CLOUDSTACK-8580See issue CLOUDSTACK-8580 and individual commits.

* pr/680:
  Made interface changes related to CLOUDSTACK-8580

Signed-off-by: Remi Bergsma <>

> Users should be able to expunge VMs
> -----------------------------------
>                 Key: CLOUDSTACK-8580
>                 URL:
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Lennert den Teuling
>            Assignee: Boris Schrijver
>            Priority: Minor
> When automating deployments of CloudStack (with for example Terraform) there are situations
where VMs get recreated with the same name (and hostname). When VMs are destroyed by a user,
the name will be reserved on the network until the VM truly gets expunged (depending on expunge.delay).
Because of this, some automation tools cannot work because a new deployment with the same
name gives an error.  
> Users do not have the ability to directly expunge VMs (Only admin and domain-admins can),
but they can destroy them and the admin can configure the expunge.delay where VMs truly get
removed (expunged). 
> Working with the expunge delay is very safe in case users accidentally remove a VM, but
in some cases (when users know what they are doing) there should also be a option to completely
remove the VM when destroying it (expunge). 
> Ideally the admin should be able to configure this behavior trough the global settings,
cause i believe the admin deliberately needs to turn it on (off by default).
> We have looked into making our clients domain-admin by default, but that gives them abilities
we do not want to give, so we see no other way then just enabling expunge for the user. 

This message was sent by Atlassian JIRA

View raw message