[
https://issues.apache.org/jira/browse/VCL-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15139232#comment-15139232
]
ASF subversion and git services commented on VCL-912:
-----------------------------------------------------
Commit 1729416 from [email protected] in branch 'vcl/trunk'
[ https://svn.apache.org/r1729416 ]
VCL-912
Added subroutines to utils.pm:
get_provisioning_table_info
get_vmhost_assigned_vm_provisioning_info
These are not being called yet. They may be used in the future to try to
dynamically determine which provisioning module to use for a VM host.
VCL-844
Added $no_cache argument to get_vmhost_assigned_vm_info.
> Add volume cleanup options for KVM provisioning module
> ------------------------------------------------------
>
> Key: VCL-912
> URL: https://issues.apache.org/jira/browse/VCL-912
> Project: VCL
> Issue Type: New Feature
> Components: vcld (backend)
> Reporter: Andy Kurth
>
> It would be useful to add _vcld -setup_ options the *libvirt.pm* and/or
> *KVM.pm* module similar to the ones which exist in the *VMware.pm* module
> which automate the purging of images from a repository and disk image volumes
> residing on KVM hosts.
> Much of the code which currently exists in *VMware.pm* could be used --
> especially the logic which determines which images that exist in the
> repository could be purged from an disk image datastore. Since code
> duplication should always be avoided, some code should probably be reworked
> and moved up to *Provisioning.pm*.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
