caudy at jhu
Jul 28, 2003, 3:09 PM
Post #2 of 5
(726 views)
Permalink
|
The first configuration you've sent looks much more reasonable (as far
as Spread is concerned). It should work properly as a spread.conf. For
the problems you were describing, I'd suggest first running Spread and
observing the messages printed to make sure that each daemon correctly
installs a configuration with all six, and maybe trying to send messages
using the spuser program.
When you say "default address" I assume you mean one of the vips. If
this is the behavior you desire, have Wackamole handle it using "Prefer"
statements, don't let the OS bring the interface up (although I'm not
sure you want to do this, Prefer None seems good here). The other issue
I'd mention is that there have been problems with some platforms in the
past where you needed to have an address already on eth0 in order for
Wackamole to correctly function, so 0.0.0.0 might not be enough.
Let me know if this is any help,
Ryan
Ashton Trey Belew wrote:
> Hello,
> I am hoping to use wackamole in a cluster of machine which have
> 2 interfaces. eth0 I hope to be the public service interface, while
> eth1 is connected to a private network.
>
> I have been doing some experimenting with the spread.conf and
> wackamole.conf to get the behavior I desire with very limited success,
> 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
> 0.0.0.0) eth1 receives a private address (10.0.0.211) Start spread,
> start wackamole -- machine receives 1 or more public addresses on eth0.
> I am hoping to not have to have an address in the public network for
> 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
> up with no address. 1 machine of the 6 invariably doesn't receive an
> 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
> haven't been receiving notifications of new nodes joining the group, and
> when I start wackamole the eth0 interface (which I suspect unwisely)
> brought up with its default address gets lost.
>
> Suggestions? Would it be easy/possible to hack wackamole to
> check to see if the default address is already up and not attempt to add
> 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.
--
Ryan W. Caudy
Center for Networking and Distributed Systems
Department of Computer Science
Johns Hopkins University
|
