This is a multi-part message in MIME format. --------------070407050209030401020600 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 01/09/2012 11:21 AM, Michael Kublin wrote:
Hi, the follow link is providing a low level design for HotPlug/HotUnplug feature : http://www.ovirt.org/wiki/Features/DetailedHotPlug .
The feature is simple and design is short
Regards Michael _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
1. Corrected some typos, spelling, backend->engine, 'REST API' -> 'API', etc. (didn't fix ' storage procedures' - but I think you've meant 'stored procedures' ?). 2. Missing/questions: - Permissions? Quota? - Explain how disk is created in the first place. - Database (tables, etc.) - Which cluster level is required? - Is it an async or sync task? - Can you plug a system disk? - Can you unplug multiple at a time? - What happens when you plug too many? - How do you determine where (PCI bus-wise) to plug them? - Any CanDoAction to allow/disallow plug/unplug from specific systems? - I suspect we'd be happier with some agent cooperation before unplugging - is this done by QEMU? Not detailed anywhere. - Link to KVM/QEMU feature description for it, if such exist, would be nice. - Does it affect taking a snapshot? Live or not? - Does it affect exporting a VM? I reckon you export with all disks, with their plug/unplug status? Y. --------------070407050209030401020600 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> On 01/09/2012 11:21 AM, Michael Kublin wrote: <blockquote cite="mid:a326aab2-28ec-4147-9265-9554cc356077@zmail14.collab.prod.int.phx2.redhat.com" type="cite"> <pre wrap="">Hi, the follow link is providing a low level design for HotPlug/HotUnplug feature : <a class="moz-txt-link-freetext" href="http://www.ovirt.org/wiki/Features/DetailedHotPlug">http://www.ovirt.org/wiki/Features/DetailedHotPlug</a> . The feature is simple and design is short Regards Michael _______________________________________________ Engine-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:Engine-devel@ovirt.org">Engine-devel@ovirt.org</a> <a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/engine-devel">http://lists.ovirt.org/mailman/listinfo/engine-devel</a> </pre> </blockquote> <br> 1. Corrected some typos, spelling, backend->engine, 'REST API' -> 'API', etc. (didn't fix ' <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> storage procedures' - but I think you've meant 'stored procedures' ?).<br> 2. Missing/questions:<br> - Permissions? Quota? <br> - Explain how disk is created in the first place.<br> - Database (tables, etc.)<br> - Which cluster level is required?<br> - Is it an async or sync task?<br> - Can you plug a system disk?<br> - Can you unplug multiple at a time?<br> - What happens when you plug too many?<br> - How do you determine where (PCI bus-wise) to plug them?<br> - Any CanDoAction to allow/disallow plug/unplug from specific systems?<br> - I suspect we'd be happier with some agent cooperation before unplugging - is this done by QEMU? Not detailed anywhere.<br> - Link to KVM/QEMU feature description for it, if such exist, would be nice.<br> - Does it affect taking a snapshot? Live or not?<br> - Does it affect exporting a VM? I reckon you export with all disks, with their plug/unplug status?<br> <br> Y.<br> <br> <br> <br> <br> </body> </html> --------------070407050209030401020600--