Projekt KVM Cluster - Revision history

Joachim: Joachim moved page Projekt IDG Cluster to Projekt KVM Cluster without leaving a redirect: better desc

2022-05-05T12:59:40Z

Joachim moved page Projekt IDG Cluster to Projekt KVM Cluster without leaving a redirect: better desc

← Older revision	Revision as of 12:59, 5 May 2022
(No difference)

2022-05-05T12:52:30Z

← Older revision		Revision as of 12:52, 5 May 2022
Line 1:		Line 1:
	= ~~IDG~~ Cluster =		= KVM Cluster =

	The IDG cluster is a 2 node heartbeat/drbd cluster running on sles		The IDG cluster is a 2 node heartbeat/drbd cluster running on sles

2014-03-11T16:19:54Z

Setup host networking

← Older revision		Revision as of 16:19, 11 March 2014
Line 130:		Line 130:
	** vmnet3 -> virbr3 (same subnet and type, here 192.168.102.0/24 isolated)		** vmnet3 -> virbr3 (same subnet and type, here 192.168.102.0/24 isolated)
	** vmnet4 -> virbr4 (same subnet and type, here 192.168.103.0/24 isolated)		** vmnet4 -> virbr4 (same subnet and type, here 192.168.103.0/24 isolated)
	* enable access to bridges for qemu in /etc/qemu/bridge.conf (e.g. ad line allow all)		* enable access to bridges for qemu in /etc/qemu/bridge.conf (e.g. add line allow all)
	* enable ip forwarding on the host to let the vm's access the outside world (if wanted)		* enable ip forwarding on the host to let the vm's access the outside world (if wanted)

2014-03-11T16:14:10Z

Todo

@@ Line 295: / Line 295: @@
 Enable proxy: In /etc/sysconfig/apache2 add " proxy proxy_http" to MODULES variable
 == Todo ==
 * Maybe update selfcompiled 0.7 drbd to 0.8 which is available as a distro rpm

2014-02-28T17:27:10Z

Setup host networking

← Older revision		Revision as of 17:27, 28 February 2014
Line 132:		Line 132:
	* enable access to bridges for qemu in /etc/qemu/bridge.conf (e.g. ad line allow all)		* enable access to bridges for qemu in /etc/qemu/bridge.conf (e.g. ad line allow all)
	* enable ip forwarding on the host to let the vm's access the outside world (if wanted)		* enable ip forwarding on the host to let the vm's access the outside world (if wanted)

			Warning: do not restart networking on the vm host because that destroys the bridge config and isolates the vm's

	=== Make kvm startup script ===		=== Make kvm startup script ===

2014-02-28T17:25:56Z

Image config

← Older revision		Revision as of 17:25, 28 February 2014
Line 182:		Line 182:
	** change sda to hda everywhere		** change sda to hda everywhere
	* edit /etc/resolv.conf		* edit /etc/resolv.conf
	** use the vm ~~host as~~ nameserver (or none)		** use the vm hosts nameserver (or none if you disabled ip forwarding on the host)
	* edit /etc/ntp.conf		* edit /etc/ntp.conf
	** use a valid reachable ntp server (usually ~~only~~ host works: 192.168.1.1)		** use a valid reachable ntp server (usually at least the vm host works: 192.168.1.1)
	* collect syslog warnings on host		* collect syslog warnings on host
	** edit /etc/syslog-ng/syslog-ng.conf.in: add udp(...);		** edit /etc/syslog-ng/syslog-ng.conf.in: add udp(...);

2014-02-28T17:24:22Z

Setup host networking

← Older revision		Revision as of 17:24, 28 February 2014
Line 131:		Line 131:
	** vmnet4 -> virbr4 (same subnet and type, here 192.168.103.0/24 isolated)		** vmnet4 -> virbr4 (same subnet and type, here 192.168.103.0/24 isolated)
	* enable access to bridges for qemu in /etc/qemu/bridge.conf (e.g. ad line allow all)		* enable access to bridges for qemu in /etc/qemu/bridge.conf (e.g. ad line allow all)
			* enable ip forwarding on the host to let the vm's access the outside world (if wanted)

	=== Make kvm startup script ===		=== Make kvm startup script ===

2014-02-28T17:01:25Z

Image config

← Older revision		Revision as of 17:01, 28 February 2014
Line 181:		Line 181:
	** change sda to hda everywhere		** change sda to hda everywhere
	* edit /etc/resolv.conf		* edit /etc/resolv.conf
	** use the ~~hosts~~ nameserver		** use the vm host as nameserver (or none)
	* edit /etc/ntp.conf		* edit /etc/ntp.conf
	** use a valid ntp server ~~if necessary~~ (e.g. ~~fritz~~.~~box~~)		** use a valid reachable ntp server (usually only host works: 192.168.1.1)
	* collect syslog warnings on host		* collect syslog warnings on host
	** edit /etc/syslog-ng/syslog-ng.conf.in: add udp(...);		** edit /etc/syslog-ng/syslog-ng.conf.in: add udp(...);

2014-02-28T16:24:43Z

Web Status

@@ Line 248: / Line 248: @@
 How about querying the cluster status via a browser?
 * Install apache2, apache2-worker (or prefork) on each node
@@ Line 263: / Line 265: @@
 * Optional: Make clone resource with one floating ip. Then we can use the same url while cluster has quorum.
 * Optional: Make a default welcome page with a link to the status page
 If you want to use apache as a clone resource (only active if heartbeat is active!)
@@ Line 271: / Line 275: @@
 * Enable server-status page (in /etc/syscongig/apache2 add module status and define STATUS)
 * Disable apache autostart on boot
 == Todo ==

2014-02-28T16:16:02Z

Testcluster

← Older revision		Revision as of 16:16, 28 February 2014
Line 9:		Line 9:
	It was originally setup as suse 9.3 vmware images.		It was originally setup as suse 9.3 vmware images.
	I transfered this to kvm since vmware on linux is a pain (kernel updates)		I transfered this to kvm since vmware on linux is a pain (kernel updates)
	Cluster status can be accessed here (if it is running): https://banzhaf.chickenkiller.com:444/job1/jobs1/~~crm_mod~~.cgi		Cluster status can be accessed here (if it is running): https://banzhaf.chickenkiller.com:444/job1/jobs1/crm_mon.cgi

	=== vmware files ===		=== vmware files ===