OpenSSI cluster - Revision history

80.166.222.82 at 09:27, 2 July 2008

2008-07-02T09:27:02Z

← Older revision		Revision as of 09:27, 2 July 2008
Line 3:		Line 3:
	= OpenSSI cluster =		= OpenSSI cluster =
	Link: http://openssi.org		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 =		= Master setup =

80.166.222.82 at 09:16, 2 July 2008

2008-07-02T09:16:52Z

← Older revision		Revision as of 09:16, 2 July 2008
Line 5:		Line 5:

	= Master setup =		= Master setup =
			== apt-sources ==
			<pre>
			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
			</pre>

	There are 2 ways to setup a master distribution load:		There are 2 ways to setup a master distribution load:

80.166.222.82 at 08:31, 2 July 2008

2008-07-02T08:31:09Z

← Older revision		Revision as of 08:31, 2 July 2008
Line 7:		Line 7:
	There are 2 ways to setup a master distribution load:		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.		* 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		* 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)		- 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 ==		== SMP setup ==

80.166.222.82 at 08:30, 2 July 2008

2008-07-02T08:30:39Z

← Older revision		Revision as of 08:30, 2 July 2008
Line 5:		Line 5:

	= Master setup =		= Master setup =
			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 ==		== SMP setup ==
	* /cluster/etc/loadlevellist		* /cluster/etc/loadlevellist

80.166.222.82: /* Normal master setup */

2008-07-02T08:27:45Z

Normal master setup

← Older revision		Revision as of 08:27, 2 July 2008
Line 5:		Line 5:

	= Master setup =		= Master setup =
	== ~~Normal master~~ setup ==		== SMP setup ==
	* /cluster/etc/loadlevellist		* /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:		Must have all the seperate instances of applications which has to run independently - ie clamav and amavisd-new if it's a mailscanner cluster:

80.166.222.82 at 08:27, 2 July 2008

2008-07-02T08:27:25Z

← Older revision		Revision as of 08:27, 2 July 2008
Line 5:		Line 5:

	= Master setup =		= Master setup =
			== Normal master 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:
			<pre>
			/usr/bin/clamd
			/usr/bin/amavisd
			</pre>

	== IP server (ip loadbalancing) ==		== IP server (ip loadbalancing) ==
	* /etc/cvip.conf template		* /etc/cvip.conf template

80.166.222.82 at 08:25, 2 July 2008

2008-07-02T08:25:43Z

New page

[[Category:Linux]]

= OpenSSI cluster =
Link: http://openssi.org

= Master setup =
== IP server (ip loadbalancing) ==
* /etc/cvip.conf template
<pre>
<?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>
</pre>

= Node setup =