[Engine-devel] Low Level design for HotPlug/HotUnplug feature
Ayal Baron
abaron at redhat.com
Sun Jan 15 09:50:51 UTC 2012
----- Original Message -----
>
> <snip>
>
> >>>> - Database (tables, etc.)
> > They are in design
> >>>> - Which cluster level is required?
> > Added to design , it is 3.1
>
> 3.1 cluster or DC?
>
> Ayal - is there a storage limitation or can we activate this feature
> for
> any 3.1 cluster?
3.1 cluster
>
> >>>> - Does it affect exporting a VM? I reckon you export with all
> >>>> disks,
> >>>> with their plug/unplug status?
> > This one I need to check
>
> Export includes all (non-shared) disks and their status.
How would one export a shared disk?
[snip]
> >>> - How do you define a system disk? Some VM may boot from
> >>> pxe/nfsroot/etc
> > I had a property on the disk which means System, also I have a
> > property that means bootable. I suppose that
> > disk can not be plugged/unplugged with any of them
I thought we're making 'system disk' devoid of meaning and not adding any logic to such annotations...
[snip]
More information about the Engine-devel
mailing list