[pve-devel] template considerations

[Dietmar Maurer]

> No, it is not needed. I just thought it is good to know?
> 
> > With your proposal,how do you do if a base volume is also a clone of
> > another volume ?
> 
> >>What problem do you see?
> 
> Oh, you want only it in config file ? (not in directory structure, or volume
> name)

yes.

> base volume clone of another base volume :
> local:base/test.raw/base/test2.raw
> local volume clone of a base volume : local:base/test.raw/100/vm-100-
> disk1.raw
> 
> I think it should be ok. But we can also simply use a hint,like for size,
> parent=base/test.raw (files) or parent=base-test (sheepdog,rbd,..)

IMHO that is more complex. And you can lose that information easily
if you pass the volume name around.

Note: extending the volume name parse should be really easy?

For now, we just need to consider that our clone() method (can) return a new
volume name. We can decide later if we use that feature.