[Seaside] Re: [ANN] mod_cluster for Seaside

[Philippe Marschall]

2010/10/5 Philippe Marschall <philippe.marschall at gmail.com>:
> Hi
>
> Have you ever wished Apache and Seaside would know each other better?
> That Apache could tell Seaside where it was and vice versa? That
> Seaside could tell Apache the load of the image so intelligent load
> balancing decisions can be made? That you can dynamically add and
> remove Seaside images from a cluster without restarting Apache or
> messing with configuration files? The guys at JBoss though the same
> and wrote mod_cluster [1].
>
> How does this actually work? There are two Apache modules involved.
> mod_advertise sends UDP broadcasts about Apache's location, you might
> have several on different hosts in the network. mod_cluster_manager
> allows remote configuration of Apache. Seaside will connect to the
> advertised Apache instances and tell them where it is (host, port,
> protocol, urls). This is kind of schizophrenic because the backend
> makes a request to the frontend but anyway.
>
> What do you need to get started? First you need to set up the
> Smalltalk parts (not the Apache config) of mod_proxy_balancer [2]. If
> you're just using a single image mod_cluster is overkill and
> clustering without sticky session doesn't get you very far (unless
> you're on GemStone). Then you need to setup mod_cluster itself, the
> easiest way is to grab the binaries from JBoss [3] and follow the
> installation instructions [4]. And finally you need to load ModCluster
> from [5]. You start the magic with:
>
> JBPharoAdvertiseListener startOnHost: 'yourIp' jvmRoute: 'yourRoute'

I forgot to add you can check the cluster status under:

http://apache:6666/mod_cluster_manager

Cheers
Philippe