Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Fri, 14 Aug 2015 09:06:46 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12839841.1435064927000.65750.1439543206148@Atlassian.JIRA>
In-Reply-To: <JIRA.12839841.1435064927000@Atlassian.JIRA>
References: <JIRA.12839841.1435064927000@Atlassian.JIRA>
 <JIRA.12839841.1435064927742@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-8580) Users should be able to
 expunge VMs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-8580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14696736#comment-14696736 ] 

ASF GitHub Bot commented on CLOUDSTACK-8580:
--------------------------------------------

Github user DaanHoogland commented on a diff in the pull request:

    https://github.com/apache/cloudstack/pull/680#discussion_r37060382
  
    --- Diff: server/src/com/cloud/server/ManagementServerImpl.java ---
    @@ -3378,6 +3379,10 @@ private String signRequest(final String request, final String key) {
             final Integer apiLimitInterval = Integer.valueOf(_configDao.getValue(Config.ApiLimitInterval.key()));
             final Integer apiLimitMax = Integer.valueOf(_configDao.getValue(Config.ApiLimitMax.key()));
     
    +        // Check if users can view destroyed vm's, expunge and/or recover them. Admins can always do so.
    --- End diff --
    
    not really a comment that enlightens us beyond the naming of the variables, so could be omitted.


> 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)