Needed because of the instance types + images feature. Currently, if the VM attaches a disk, there is no way to tell if I want to be dependent on this specific version of disk image or on a the latest possible. The RFE is to be able to create new Disks either as a base version or as a new version of some already existing disk. In case the disk is made as a new version of an existing one, all VMs which are based on the latest version of the base disk have to be updated. The behavior should be exactly as the one with template versions but in a granularity of specific disks.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
This request is equal to requesting snapshotting on floating\shared disks, no?
No, the new version can be something completely different. Same as for template versions.
(In reply to Tomas Jelinek from comment #3) > No, the new version can be something completely different. Same as for > template versions. So why complicate with versions and not allow replacing the disk used in the instance type?
Because the instance types are not having disks.
(In reply to Tomas Jelinek from comment #5) > Because the instance types are not having disks. Why not add disk definition as part of this, if this is different disks?
OK, the original idea was to have the VM composed as instance type + image similar to amazon EC2. And also, to have the disks versionable similar to templates. This RFE has been opened in time when this had some priority. I believe this is not the case anymore, so feel free to close this RFE.