[
https://issues.apache.org/jira/browse/CLOUDSTACK-8580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14692393#comment-14692393
]
ASF GitHub Bot commented on CLOUDSTACK-8580:
--------------------------------------------
GitHub user borisroman opened a pull request:
https://github.com/apache/cloudstack/pull/680
Interface changes related to CLOUDSTACK-8580
See issue CLOUDSTACK-8580 and individual commits.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/borisroman/cloudstack CLOUDSTACK-8580
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/680.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #680
----
commit 53e6551dee27ed41ec729746e305f1c3f43ce7ee
Author: Boris Schrijver <bo...@pcextreme.nl>
Date: 2015-08-11T21:45:16Z
Added responses to ListCapabilities to reflect CLOUDSTACK-8580 changes.
This to add these options to the gui. See issue CLOUDSTACK-8580.
commit 8d8b6f85a85021841c06aae1cb2e1a71a3d08fc7
Author: Boris Schrijver <bo...@pcextreme.nl>
Date: 2015-08-11T22:28:36Z
Made interface changes related to CLOUDSTACK-8580
https://github.com/kevindierkx/cloudstack/commit/3be14e978aa0c9b286d9f57bf1fc60ebe50990c7
----
> Users should be able to expunge VMs
> -----------------------------------
>
> Key: CLOUDSTACK-8580
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8580
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Lennert den Teuling
> 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
(v6.3.4#6332)
