[Xen-users] AoE LVM2 DRBD Xen Setup

[Bjoern Metzdorf <bm@xxxxxxxxxxxxxxxxxxxxxxx>]

Hello everybody,

I am in the process of setting up a really cool xen serverfarm. Backend 
storage will be an LVMed AoE-device on top of DRBD.
The goal is to have the backend storage completely redundant.

Picture:

|RAID|         |RAID|
|DRBD1| <----> |DRBD2|
       \      /
        |VMAC|
       | AoE  |
    |global LVM VG|
      /   |    \
|Dom0a| |Dom0b| |Dom0c|
   |      |        |
   |      |        |
|LVMLV1| |LVMLV2|  |LVMLV3|
|DomU1|  |DomU2|   |DomU3|

Each Dom0 has the global LVM VG visible but only uses the relevant LVs 
for its DomUs.
There are two open questions for me:

1. Is is possible to failover AoE from drbd1 to drbd2? Did anyone try 
this yet? Normal drbd-setups use heartbeat with a virtual IP for 
failover, but in this case I need a virtual Mac, since AoE is layer2.
Does an AoE-Client recognize mac-changes automatically (I don't think 
so), or do I have to "failover" a custom virtual mac with "ip set 
hwaddr" or such?
In the archives I didn't find anything close to it.

2. Do I need the Redhat-Cluster-framework for this to work? If I make 
changes to the shared LVM VG (e.g. create a new LV for a new DomU), I 
have to execute vgscan on all Dom0s.
This would not be necessary if I would use the cluster framework. But I 
don't need GFS or such, so I don't want to add additional complexity. 
But perhaps I have overseen some metadata problems here? Anyone? :)
Regards,
Bjoern




_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users