GitHub user rohityadavcloud added a comment to the discussion: How CloudStack handles multiple NFS type Primary Storage
@shaerul It follows a lazy deployment strategy, i.e. it copies the templates (images) to a primary storage only when it needs to create a VM's root disk on a pool. There's also a [prepareTemplate API](https://cloudstack.apache.org/api/apidocs-4.19/apis/prepareTemplate.html) that can load a template across pools to do this ahead of time. In terms of using storage pool upon VM deployment or volume creation, it depends what deployment planning algorithm is used, pl search for these global settings (for tuning and configuration): image.store.allocation.algorithm [1], vm.allocation.algorithm [2]. [1] Image store allocation algorithm (image.store.allocation.algorithm) firstfitleastconsumed','random' : Order in which hosts within a cluster will be considered for VM/volume allocation [2] Vm allocation algorithm (vm.allocation.algorithm) 'random', 'firstfit', 'userdispersing', 'userconcentratedpod_random', 'userconcentratedpod_firstfit', 'firstfitleastconsumed' : Order in which hosts within a cluster will be considered for VM/volume allocation. GitHub link: https://github.com/apache/cloudstack/discussions/9073#discussioncomment-9426611 ---- This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
