OpenSSI cluster

From Skytech
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.


OpenSSI cluster

Link: http://openssi.org

Install howto for debian sarge (3.1): http://openssi.org/cgi-bin/view?page=docs2/1.2/debian/INSTALL.html (really good explanation about howto progress after mastersetup - suggest following this after the below link to setup openssi on etch)

Install howto for debian etch: http://www.atlantech.com/%7Ejohn/openssi-etch/Howto.html

Master setup

apt-sources

deb http://debianmirror.wwi.dk/debian/ etch main contrib non-free
deb-src http://debianmirror.wwi.dk/debian/ etch main contrib non-free

deb http://security.debian.org/ etch/updates main contrib
deb-src http://security.debian.org/ etch/updates main contrib

deb http://www.atlantech.com/~john/openssi-etch ./
deb-src http://www.atlantech.com/~john/openssi-etch ./

deb http://www.backports.org/debian etch-backports main contrib non-free

There are 2 ways to setup a master distribution load:

  • SMP

- Which will try to fill up a load on one node and then relay to the others - all nodes are simply seen as another CPU and for the system it thinks it's just one huge singular system. This will accept and return queries/data from the same ip.

  • IP server

- This distrubutes loads according to the scheduler chosen and thus try to distribute load evenly across all nodes. This will receive on a seperate IP specified in cvip.conf and return data directly from the nodes (unless NAT is choosing as routing)

SMP setup

  • /cluster/etc/loadlevellist

Must have all the seperate instances of applications which has to run independently - ie clamav and amavisd-new if it's a mailscanner cluster:

/usr/bin/clamd
/usr/bin/amavisd

IP server (ip loadbalancing)

  • /etc/cvip.conf template
<?xml version="1.0"?>
<cvips>
        <routing>DR</routing>
        <cvip>
                <ip_addr>172.22.0.21</ip_addr>
                <service>
                        <tcp_port>10024</tcp_port>
                        <scheduler>wlc</scheduler>
                </service>
                <director_node>
                        <node_num>1</node_num>
                        <garp_interface>eth1</garp_interface>
                        <sync_interface>eth1</sync_interface>
                </director_node>

                <real_server_node>
                        <node_num>3-10</node_num>
                        <service>
                                <tcp_port>10024</tcp_port>
                        </service>
                </real_server_node>
        </cvip>
</cvips>

Node setup