[Pacemaker] adding ldirectord resource to pacemaker

[Jayakrishnan]

Hello Geek,

I just stared the same project in el5 itself yesterday. I wonder if we could
go on as explained in Andrew's 'Cluster from scratch', it will give you an
active/active cluster. Wouldn't it gives you loadbalancing.

Pardon me if this is a stupid suggestion!!

-- 
Regards,

Jayakrishnan. L

Visit:
www.foralllinux.blogspot.com
www.jayakrishnan.bravehost.com


On Wed, Apr 7, 2010 at 7:51 PM, <geek at lenux.mine.nu> wrote:

> Hello
>
> I have installed pacemaker and corosync on my redhat el5 with the
> clusterlabs repository:
> http://clusterlabs.org/rpm/epel-5/clusterlabs.repo
>
> The installation worked fine, just needed to install some dependencies but
> all ok :)
>
> So now my question. I need the build a high-available web cluster with
> loadbalancing,
> on my old machines I used heartbeat version 1, ldirectord and ipvsadm,
> works great :)
> Now I need to replace heartbeat version 1 with corosync+pacemaker (please
> don't ask why)
>
> Here more details about my infrastructure
>
> The 2 loadbalancer that I need to configure with pacemaker/corosync
> pacemaker1.lenux.local IP: 192.168.33.210 (live)
> pacemaker2.lenux.local IP: 192.168.33.211 (stand-by)
> virtual IP: 192.168.33.240
>
> 3 webserver (are in the same network)
> www1.lenux.local IP: 192.168.33.241 (virtual IP: 192.168.33.240)
> www2.lenux.local IP: 192.168.33.242 (virtual IP: 192.168.33.240)
> www3.lenux.local IP: 192.168.33.243 (virtual IP: 192.168.33.240)
>
> Ok, installed pacemaker and corosync on both loadbalancer..after that I
> configure corosync like this (also on both loadbalancer):
>
> aisexec {
>        user:   root
>        group:  root
>  }
>
> totem {
>
>        version: 2
>        token:          5000
>        token_retransmits_before_loss_const: 20
>        join:           1000
>        consensus:      7500
>        vsftype:        none
>        max_messages:   20
>        secauth:        off
>        threads:        0
>        clear_node_high_bit: yes
>
>        interface {
>                ringnumber: 0
>
>                bindnetaddr: 192.168.33.0
>                mcastaddr: 226.94.1.1
>                mcastport: 5404
>        }
>  }
>
>  logging {
>        fileline: off
>        to_syslog: no
>        to_stderr: no
>        debug: on
>        timestamp: on
>  }
>
>  service {
>        # Load the Pacemaker Cluster Resource Manager
>        name: pacemaker
>        ver:  0
>  }
>
>
>
> now I need to add the ldirectord (already configured and located in
> /etc/ha.d/ldirectord.cf) resource to pacemaker with the crm tool...but I
> don't know how? I need to add the virtual IP and the ldirectord service
> that can swap to the other loadbalancer on failure. I read the hole wiki
> without finding the right answear..I hope someone can help me!
>
> Thanks
>
> Regards
> Juan
>
> _______________________________________________
> Pacemaker mailing list
> Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20100408/f61c3552/attachment-0002.htm>