cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From DaanHoogland <>
Subject [GitHub] cloudstack issue #2044: CLOUDSTACK-9877 Cleanup unlinked templates
Date Fri, 14 Apr 2017 14:58:51 GMT
Github user DaanHoogland commented on the issue:
    ad 1. yes they can, if you look in the ticket there is a part of description that describes
this possibility. But that said I don't see how restore is going to be hindered if the vm
was created using a full clone. The image is not deleted.
    ad 2. No it is only marking templates for gc and not touching any cleanup process, it
relies on the regular process to do the actual cleanup. The benefit is that short lived templates
that will be replaced by cron jobs for instance will be cleaned without having to wait until
the VMs cloned from it are all gone (on a per primary store basis btw)
    ad 3. Yes so far it is I have not studied other hypervisors on this area. The code is
now in the vmware plugin but not tightly coupled to the vmware API so generalizing it shoud
be rather trivial.
    ad 4. the host scan task was an empty placeholder with only todo. The vcente clusters
are not scanned for new hosts atm. If you look at the old code you can find that the task
consists of only a comment:
        private Runnable getHostScanTask() {
            return new Runnable() {
                public void run() {
                    // TODO scan vSphere for newly added hosts.
                    // we are going to both support adding host from CloudStack UI and
                    // adding host via vSphere server
                    // will implement host scanning later

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 or file a JIRA ticket
with INFRA.

View raw message