Hi,
Let me drop into this discussion.
I have been running iSCSI on the dom0 for about 2 years now and that
works fine.
Making your iSCSI Target High Available can be done by using DRBD and
Heartbeat, i have written a small howto (in Dutch), if you would to have
this, contact me.
Failovers on the iSCSI Target side go without notice of the domU, on the
dom0 you get a iSCSI connection error, but that's it.
This whole setup can be created with Open-iSCSI, iSCSI Enterprise
Target, DRBD and Heartbeat.
-
Met vriendelijke groet,
Wido den Hollander
Hoofd Systeembeheer / CSO
Telefoon Support Nederland: 0900 9633 (45 cpm)
Telefoon Support België: 0900 70312 (45 cpm)
Telefoon Direct: (+31) (0)20 50 60 104
Fax: +31 (0)20 50 60 111
E-mail: support@xxxxxxxxxxxx
Website: http://www.pcextreme.nl
Kennisbank: http://support.pcextreme.nl/
Netwerkstatus: http://nmc.pcextreme.nl
On Fri, 2009-03-13 at 09:37 -0400, John Madden wrote:
> > I think that we would have to reboot each domU in this case after a
> > failure, isn't it? The goal is to have domUs which would not be affected
> > by failure of one storage servers.
>
> Ideally, the initiator in dom0 would handle the failover of the target
> successfully and domU would never know anything had happened. I've done
> things like entirely restart the target daemon without initiators
> caring, but if it's gone long enough while i/o is going on, bad things
> will happen.
>
> > > Abstract your disks and iscsi exports; then use ZFS on two pools this will
> > > minimize the administration.
> >
> > ZFS seems to be very nice, but sadly we are not using Solaris and don't
> > want to use it with FUSE under Linux. Nevertheless does anyone use ZFS
> > under Linux and can share his/her experiences?
>
> I wouldn't pay too much attention to the ZFS fanboi's anyway. It's does
> good things but hardly anything truly useful that you can't find in LVM
> and doesn't really change anything in this case.
>
> John
>
>
>
signature.asc
Description: This is a digitally signed message part
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|