@resmo I think the aim of the feature was to control the use of linked clones or full clones at storage pool level at VM deployment time. If the configuration value is not set for a storage pool then the global value should be used. In case of stop/start a VM then only DB is updated to keep consistency between the storage pool configuration value for existing VMs in that storage pool.
[ Full content available at: https://github.com/apache/cloudstack/pull/2840 ] This message was relayed via gitbox.apache.org for [email protected]
