Description of problem: Following the RFE #1346918, the logic connection between disks and vm was "pulled" out from vm's disks collection to diskattachemnts, to make the connection between disks and vms to be more logical and reasonable. This connection is should be bi-directional. If a VM object "sees" a list of attachments to different disks, a Disk object should have the "ability" to "see" a list of attachments, that are applied on it, to different vms (in case the disk is shared, snapshot disk that was attached to backup vm, etc.) Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Tal - can you guestimate how much work there is here?
Not too much probably, this bug was opened after a discussion with Raz last night, I think this is quite logical to have that. Juan, what do you think?
I agree it is logical to have that, but before adding it to the API I'd like to hear what is the use case. We didn't need this before introducing the concept of "disk attachment", so why do we need it now? How are users going to take advantage of this new feature?
A good example I can think of is that when registering a disk, from an imported storage domain, that was attached to a vm before the storage domain was detached, I would expect that this disk will be registered as an attached disk to the vm (in case it is still exists in the environment). This operation can be achieved with this RFE
Closing old RFEs. If relevant, please re-open and explain why. As always- patches are welcomed!