On 12/30/2011 04:25 PM, Yair Zaslavsky wrote:
On 12/29/2011 09:32 PM, Eli Mesika wrote:
> The following summarizes the DR meeting from today
> Attendees: Backend Team + Moran& Haim from QA
> => marks responsibility for action items.|
> Issues/Action Items:
> 1) Video - memory allocation logic, check again why the logic of how much memory to
allocate to a video device should move to backend. => (Eli, Igor)
> 2) Generic-device - rename to vm_device (Eli)
> 3) Verify hash is only on devices (not on all domxml) , check if can be expanded to
VM scope (app list etc.) => (Eli, Igor)
> 4) Floppy/CD - should be handled as vm_device that means we have to add to it also
boot order => (Eli, Igor)
> 5) Hot plug - need to check for added/deleted devices, Open issue how to handle
for managed device.
> same for any other device that is changed not via backend => (Eli,
About this issue - a question I asked at the meeting is whether disks
have some sort of unique identifier as MAC address in case of NIC. If
such info can be obtained by engine-core, we will be able to handle a
scenario of plugging back a managed disk that got plugged out.
Disks have UUID and kvm supports it for its devices (virtio uuid is
> 6) How boot order affects GUI (order of NICs) - check with Einav if support can be
added for that in UI (for disks use only 1) (Eli,Einav)
How does boot order correlates to stable device address?
Note that KVM supports boot order priority setting per device basis.
> 7) OVF - add new devices , addresses , coordinate with V2V
> 8) Live snapshot , check if affects design => (Eli, Igor)
> 9) Review class diagram of detailed design => (Eli)
> 10) Do we have to persist indexes ? check if addresses are respected in spite of
indexes.... => (Eli, Igor)
> 11) Update wiki pages => (Eli)
> Engine-devel mailing list
Engine-devel mailing list