On Thu, Aug 11, 2011 at 12:09 PM, Patrick J. LoPresti <lopresti at gmail.com> wrote: > First, thank you for your reply. > > On Thu, Aug 11, 2011 at 12:00 PM, Mohit Anchlia <mohitanchlia at gmail.com> wrote: >> >> Assuming these bricks can be in different volumes. > > Sorry, I should have mentioned... ?I want them to be part of the same > (distributed) volume. If it's same volume then I am not sure if it will work but you can try it out :) > >> I haven't done it yet, somone else might have more experience, but I >> think if you created 2 storage trusted pools on separate IPs it should >> work. > > So specifically... > > Run one glusterd on server1. ?Have "server1-eth1" and "server1-eth2" > refer to the two interfaces. ?Use "gluster peer probe server1-eth1" > AND "gluster peer probe server1-eth2" (?) > > My concern is that this will be attempting to add the same server to Don't they have different IP unless I misunderstood your configuration. Are the NIC bonded? > the trusted pool twice, which seems like a strange thing to do. > > Or did you just mean to add the server once, but then use the > multi-home addresses when I create the volume? ?As in: > > ?gluster volume create my-vol transport tcp server1-eth1:/data1 > server1-eth2:/data2 > If you want to try out you will also need to do peer probe with eth1 and eth2 IPs. > ? > > I guess I can just try any or all of these, but it would be nice to > know what the gluster developers would actually expect to work... > Since upgrades do happen. > > ?- Pat >
