Re: [Engine-devel] Floating Disk feature description

On 02/01/2012 07:04 PM, Daniel Erez wrote: some questions/notes: 1. why do you need a floating/not floating state? isn't a disk floating if it was detached from all VMs? or is that only a helper property to optimize lookups? 2. you mention fields of disks (Floating/Shared/Managed) 2.1 do we have a definition of "Managed" disk somewhere? I assume unmanaged would be a direct LUN, but i think we need a better terminology here. 2.2 same goes for "floating" actually... do we really want to tell the user the disk is "floating"? I guess suggestion welcome for a better name. 2.3 finally, for shared, maybe more interesting is number of VMs the disk is connected to, rather than just a boolean (though i assume this increases complexity for calculation, or redundancy of data, and not a big issue) 3. List of Storage Domains in which the selected Disk resides. this is only relevant for template disks? maybe consider splitting the main grid if looking at tempalte disks or vm disks, and show for vm disks the storage domain in main grid? maybe start with vm disks only and not consider template disks so much? 4. "Templates (visible for disks that reside in templates) List of Templates to which the selected Disk is attached. " same comment as above of maybe consider only vm disks for now. and also a question - how can a template disk belong to more than a single template? which again hints for a template disk you would want another view, with the template name in the main grid 5. Tree: 'Resources' vs. 'free disks' while i understand why separating them - naming is very confusing. maybe a single node in tree and a way to filter the search from the right side grid in some manner for known lookups (relevant to other main tabs as well?) 6. permissions not available for disks? at all? what do you mean power user would be able to attach them by their type? does it mean they can associate any shared disk in the system? I hope i'm misunderstanding, as doesn't make sense to me. or is this caveat specific to the user portal and not the admin? not allowing creating a floating disk from user portal is not a problem in my view for this phase. I assume anyone can add a disk on a storage domain they have quota to. who can edit a disk? remove a disk? attach disk to VM (which gives them ability to edit the disk) (attach disk to VM obviously requires permission on both disk and VM) 7. related features - data ware house may be affected by disks being unattached, or shared between multiple disks.