atb at uvm
Jul 28, 2003, 2:50 PM
Views: 748
Permalink
|
--CE+1k2dSO48ffgeK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Hello,
I am hoping to use wackamole in a cluster of machine which have=20
2 interfaces. eth0 I hope to be the public service interface, while=20
eth1 is connected to a private network.
I have been doing some experimenting with the spread.conf and=20
wackamole.conf to get the behavior I desire with very limited success,=20
so I thought I would come here and see what I could learn.
My hope:
Boot box, eth0 gets upped with no address (ifconfig eth0=20
0.0.0.0) eth1 receives a private address (10.0.0.211) Start spread,=20
start wackamole -- machine receives 1 or more public addresses on eth0. =20
I am hoping to not have to have an address in the public network for=20
every machine, for we don't really have that many addresses left.
Here are my two current config attempts and what they do:
Attempt1:
/usr/local/etc/spread.conf:
Spread_Segment 10.0.0.255 {
p1 10.0.0.211
p2 10.0.0.212
p3 10.0.0.213
p4 10.0.0.214
p5 10.0.0.215
p6 10.0.0.216
}
wackamole.conf:
VirtualInterfaces {
{ eth0:132.198.101.211/24 }
{ eth0:132.198.101.212/24 }
{ eth0:132.198.101.213/24 }
{ eth0:132.198.101.214/24 }
{ eth0:132.198.101.215/24 }
{ eth0:132.198.101.216/24 }
}
Notify {
eth1:10.0.0.0/24 throttle 128
arp-cache
}
Behavior: Semi works if I am very careful to already have eth0=20
up with no address. 1 machine of the 6 invariably doesn't receive an=20
address properly for reasons I do not understand.
Attempt 2:
spread.conf:
Spread_Segment 10.0.0.255 {
penguin1 132.198.101.211 {
D 10.0.0.211
C 132.198.101.211
}
penguin2 132.198.101.212 {
D 10.0.0.212
C 132.198.101.212
}
penguin3 132.198.101.213 {
D 10.0.0.213
C 132.198.101.213
}
penguin4 132.198.101.214 {
D 10.0.0.214
C 132.198.101.214
}
penguin5 132.198.101.215 {
D 10.0.0.215
C 132.198.101.215
}
penguin6 132.198.101.216 {
D 10.0.0.216
C 132.198.101.216
}
}
wackamole.conf:
VirtualInterfaces {
{ eth0:132.198.101.211/24 }
{ eth0:132.198.101.212/24 }
{ eth0:132.198.101.213/24 }
{ eth0:132.198.101.214/24 }
{ eth0:132.198.101.215/24 }
{ eth0:132.198.101.216/24 }
}
Notify {
eth1:10.0.0.0/24 throttle 128
arp-cache
}
Behavior: Does not seem to work at all. I am not sure why. I=20
haven't been receiving notifications of new nodes joining the group, and=20
when I start wackamole the eth0 interface (which I suspect unwisely)=20
brought up with its default address gets lost.
Suggestions? Would it be easy/possible to hack wackamole to=20
check to see if the default address is already up and not attempt to add=20
vip?
Thank you very much for your time,
-Trey
--
Ashton Trey Belew
http://www.uvm.edu/~atb
You will gain money by a speculation or lottery.
--CE+1k2dSO48ffgeK
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE/JZqOF9UIceSIYeoRAsLwAJ4gmgPgouauf9MXEYIYHUkuvX3JjgCgulBf
vGF84+jXTloE45QgpLk3peE=
=NexI
-----END PGP SIGNATURE-----
--CE+1k2dSO48ffgeK--
|
wackamole query
