Fwd: [Spread-users] spread on ec2

[Jake Luciani]

Hi Alex,

I've deployed it on ec2, not yet automated but I'm working on it. Heres my
current spread.conf (2 nodes)

#####################################
Spread_Segment 10.252.41.255:4803 {
  s1 10.252.41.242
}

Spread_Segment 10.252.46.255:4803 {
  s2 10.252.46.161
}

SocketPortReuse = AUTO
EventLogFile = /mnt/log/spread_%h.log
EventTimeStamp
DaemonUser = spread
DaemonGroup = spread
#####################################

There are 2 big issues here: First, ec2 doesn't allow multicast so you must
put each instance in its own segment.
Second, is the ec2 internal domain name is too long for spread to handle.
So I shortened them so s1 and s2.

Ideally this config would be dynamically generated based on the instances
available and instance user-data.

Other spread users have any suggestions or ideas? Is it a performace hit to
increase the allowed domain length?

-Jake


On Nov 10, 2007 9:27 PM, Alex Jacobson < alex at alexjacobson.com> wrote:

> Is anyone deploying spread on ec2?  If so, how are you configuring given
> that you don't get visibility on whether your servers are actually in
> the same data center or not?
>
> -Alex-
>
> _______________________________________________
> Spread-users mailing list
> Spread-users at lists.spread.org
> http://lists.spread.org/mailman/listinfo/spread-users
>

-- 
------------------------------------------------
http://3.rdrail.net/blog - my blog
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.spread.org/pipermail/spread-users/attachments/20071111/a57b0e2e/attachment.html