Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
From: serg38 <git@git.apache.org>
To: dev@cloudstack.apache.org
Reply-To: dev@cloudstack.apache.org
References: <git-pr-2044-cloudstack@git.apache.org>
In-Reply-To: <git-pr-2044-cloudstack@git.apache.org>
Subject: [GitHub] cloudstack issue #2044: CLOUDSTACK-9877 Cleanup unlinked templates
Content-Type: text/plain
Message-Id: <20170414161233.5C14CDFFAB@git1-us-west.apache.org>
Date: Fri, 14 Apr 2017 16:12:33 +0000 (UTC)
archived-at: Fri, 14 Apr 2017 16:12:40 -0000

Github user serg38 commented on the issue:

    https://github.com/apache/cloudstack/pull/2044
  
    @DaanHoogland Not for us since we still use link clones but I am sure tons of other might be affected. Interestingly enough that with PR 1773 merged the default behavior in API is not to allow template deletion if there are active VMs and only if 'forced' flag is used it will be executed
    # c is an option already but I suggest one of the following
    #d introduce another global config with default value = false e.g. vmware.cleanup.fullclonedtemplate that would be a switch old/new behaviur in combination with storage.template.cleanup.enabled
    #e make 0 as a default value for vmware.full.clone.template.cleanup.period and when you  interpret 0 it means that full clone cleanup thread thread never
    
    #e seems to be a good compromise that doesn't require too many changes


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---