[
https://issues.apache.org/jira/browse/CLOUDSTACK-8580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14638702#comment-14638702
]
ASF GitHub Bot commented on CLOUDSTACK-8580:
--------------------------------------------
Github user wilderrodrigues commented on the pull request:
https://github.com/apache/cloudstack/pull/593#issuecomment-124075403
Creating 2 VMs via cloudmonkey
(local) 🐵 > deploy virtualmachine displayname=isovm
networkids=61fb9ffe-cf5e-4a09-9470-e0800685f74d
templateid=2853716f-311a-11e5-b59a-5254001daa61
zoneid=38d556a7-39e5-4b70-9ce2-9bed1a16abc5
serviceofferingid=5ffbfb25-7df3-4b00-b053-cda67b5b46a9
(local) 🐵 > deploy virtualmachine displayname=isovm2
networkids=61fb9ffe-cf5e-4a09-9470-e0800685f74d
templateid=2853716f-311a-11e5-b59a-5254001daa61
zoneid=38d556a7-39e5-4b70-9ce2-9bed1a16abc5
serviceofferingid=5ffbfb25-7df3-4b00-b053-cda67b5b46a9
Destroying 1 VM via cloudmonkey (no expunge)
(local) 🐵 > destroy virtualmachine id=ecaeb2f4-27fa-4d40-8a72-762232f17cc4
Recovering 1 VM via cloudmonkey
(local) 🐵 > recover virtualmachine id=ecaeb2f4-27fa-4d40-8a72-762232f17cc4
Starting 1 VM via cloudmonkey
(local) 🐵 > start virtualmachine id=ecaeb2f4-27fa-4d40-8a72-762232f17cc4
Destroying 1 VM via cloudmonkey (expunge)
(local) 🐵 > destroy virtualmachine id=ecaeb2f4-27fa-4d40-8a72-762232f17cc4
expunge=true
All L-super-GTM :+1:
Merging... :)
> 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)
