> ----- Original Message ----- > From: "Ayal Baron" <[email protected]> > Sent: Wednesday, July 4, 2012 9:29:55 AM > > ----- Original Message ----- > > On 07/03/2012 06:44 PM, Miki Kenneth wrote: > > > > > > > > > ----- Original Message ----- > > >> Hey, > > >> > > >> https://bugzilla.redhat.com/show_bug.cgi?id=828089 > > >> > > >> I would like add a search option for searching disks of a VM or > > >> Template, > > >> > > >> Please suggest a name for the search option, > > >> In the 'view' level we call it 'entity_type', but maybe 'type' > > >> is > > >> nicer ? (or not too specific?) > > > Belongs-To/Attached-To/ > > Part of? > > So what do you do with a disk that is both in a template and attached > read-only to a VM? (no, we do not currently support it, but we will > as there is no reason not to). > When a container references the disk, that is not a property of the > disk so there should be no column indicating that when looking at > the disk. > The disk is either read only or read write, that's it. The column > should state that.
I think that "read-only/read-write" is not related to "attached to Template(s)/attached to VM(s)/attached to both (not supported yet)". Moreover, wouldn't we want "read-only/read-write" to be per VM/Template, and not a property of the Disk itself (i.e. a disk can be writable in VM1 and read-only in VM2/Template1)? As opposed to the "attached to Templates/attached to VMs" information, which is clearly a property of the Disk (well, not a "real" property, as Ayal has also mentioned - it is calculated information, based on the entities to which the disk is attached to; still, it is interesting information that "deserves" a column in the Disks main-grid IMO. ["read-only/read-write" is interesting information as well, and should also be displayed - don't know if in the main grid or in the VMs/Templates sub-tabs - probably worth a separate discussion] > > > > >> > > >> > > >> Thanks, > > >> > > >> > > >> > > >> Regards, > > >> Asaf > > >> > > >> > > >> > > >> > > > _______________________________________________ > > > Engine-devel mailing list > > > [email protected] > > > http://lists.ovirt.org/mailman/listinfo/engine-devel > > > > _______________________________________________ > > Engine-devel mailing list > > [email protected] > > http://lists.ovirt.org/mailman/listinfo/engine-devel > > > _______________________________________________ > Engine-devel mailing list > [email protected] > http://lists.ovirt.org/mailman/listinfo/engine-devel > > > _______________________________________________ Engine-devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/engine-devel
