----- Original Message -----
From: "Itamar Heim" <iheim(a)redhat.com>
To: "Eli Mesika" <emesika(a)redhat.com>
Sent: Sunday, January 1, 2012 11:08:18 PM
Subject: Re: [Engine-devel] Stable Device Addresses HLD/LLD for tomorrow meeting (15:00
On 12/28/2011 06:52 PM, Eli Mesika wrote:
> High level design :
> Low level design :
> (probably will be modified until the meeting)
1. " hash -- holds the md5 like encryption indicating a change "
I don't think "encryption" is relevant here.
right , replaced with
how will we know/flag when we expect it can be deleted?
("Old" is relative. what if you will need to create another OldOld
class? maybe something more specific like 3_0, so you know you can
delete it when you no longer have 3_0 clusters supported?)
3. "Addresses are kept in the database as a plain-text strings"
at some point we will want to expose this to users. maybe a better
representation would be in order (could be handled later as part of
upgrade process i guess).
will ne handled later (when needed)
4. video cards
you mention only spice - what happens to VNC monitors?
Handled already, look on HLD
'qxl' - spice device, 'cirrus' - vnc device
expect there will be more than one cd-rom (looks as the most probably
solution to user data injection afaiu)
sure, we assume that those can be multiple
you mention it in the beginning, but not afterwards wrt
details. there may be multiple of these (qemu-ga, ovirt-guest-agent,
I think those will be handled as (un-managed) vm-device abd by definition can have
> Engine-devel mailing list