JoaoJandre commented on PR #11177: URL: https://github.com/apache/cloudstack/pull/11177#issuecomment-3139825845
> > It is not marked in the database currently, do you see a reason to do this? > > @JoaoJandre in any case, if the user or operator wants to know if the volume is a full clone or not (can get it through list volumes response?), and later point of time, if any operation on the volume depends on full clone factor. Currently no operation is affected by having a full clone or linked clone. There is a possible optimization to be done where we save whether a volume is full or linked clone and, during migration, check this information to know if we must have the template on the destination or not. But the process works 100% as it does now even without this optimization. In any case, I would like to point out that if we take a snapshot of a linked clone volume and restore it, the volume will be "full clone" (it will not depend on the template anymore), and everything works as normal. We could map an issue to show whether a volume depends on a template or not, although I don't see much need for it. And it would have to contemplate cases like the one I pointed regarding snapshot restoration. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
