On Wed, Apr 21, 2021 at 3:55 PM Chris Adams <cma@cmadams.net> wrote:
Once upon a time, Gianluca Cecchi <gianluca.cecchi@gmail.com> said:
But some of these VMs had disk with storage allocation of type "Thin" on their related template. So I was both unable to move these templates and VMs disks...
You can copy (rather than move) a template to the new storage domain, then any thin-provisioned disks that rely on the template can be moved.
-- Chris
Thank, Chris! I didn't notice this. So I can select in Storage --> DIsks the disk corresponding to a template, then I see I can copy it to another storage domain. And then the template continues to be one, but in Compute --> Templates select template, DIsks I see now one disk with a "+" sign and expanding it I see the two domains. Great! This means that if I do this I create a break in the dependency of the VM from the particular storage domain, correct? And what if later I go and edit the template, changing its properties? I think they are only metadata that doesn't imply any modification of the disk itself, that is now present in more than one domain, correct? Gianluca