Install workflow - Revision history

Joachim at 16:38, 8 April 2009

2009-04-08T16:38:49Z

← Older revision		Revision as of 16:38, 8 April 2009
Line 1:		Line 1:
	[[Projekt_Lis.Tec_Cluster]]		[[Projekt_Lis.Tec_Cluster]]

	----		----

Joachim at 16:38, 8 April 2009

2009-04-08T16:38:07Z

← Older revision		Revision as of 16:38, 8 April 2009
Line 1:		Line 1:
			[[Projekt_Lis.Tec_Cluster]]
			----

	== main workflow ==		== main workflow ==
	* parse commandline for create/modify/reconstruct mode, config file and config file option replacements		* parse commandline for create/modify/reconstruct mode, config file and config file option replacements

Joachim: /* reconstruct workflow */

2009-04-08T16:36:59Z

reconstruct workflow

← Older revision		Revision as of 16:36, 8 April 2009
Line 49:		Line 49:
	* writes the config file		* writes the config file
	* generates the iso that must be provided to new nodes		* generates the iso that must be provided to new nodes

			----
			[[Projekt_Lis.Tec_Cluster]]

Joachim: /* modify workflow */

2009-04-08T16:35:01Z

modify workflow

← Older revision		Revision as of 16:35, 8 April 2009
Line 40:		Line 40:

	somehow it must be stored which resources are under cluster manager control, so they can be removed if they do not appear in a modified config script		somehow it must be stored which resources are under cluster manager control, so they can be removed if they do not appear in a modified config script

			it must be checked if the change is possible (i.e. rename of a vg used by the ha db2 instances)

	== reconstruct workflow ==		== reconstruct workflow ==

Joachim: /* modify workflow */

2009-04-08T16:32:41Z

modify workflow

← Older revision		Revision as of 16:32, 8 April 2009
Line 38:		Line 38:

	like create workflow except skipping the first five steps		like create workflow except skipping the first five steps

			somehow it must be stored which resources are under cluster manager control, so they can be removed if they do not appear in a modified config script

	== reconstruct workflow ==		== reconstruct workflow ==

Joachim: /* create workflow */

2009-04-08T16:29:36Z

create workflow

← Older revision		Revision as of 16:29, 8 April 2009
Line 24:		Line 24:
	* check for required vg's and lv's and create if necessary		* check for required vg's and lv's and create if necessary
	* check for required filesystems and create if necessary		* check for required filesystems and create if necessary
	* check for required drbd devices and create if necessary (define ~~primary node with valid data~~ in config file)		* check for required drbd devices and create if necessary (define in config file for each drbd device which nodes data shall be destroyed)
	* check for basic hb config and create it if necessary (use custom udp port to allow for more clusters in one subnet, use a unique cluster auth key)		* check for basic hb config and create it if necessary (use custom udp port to allow for more clusters in one subnet, use a unique cluster auth key)
	* on secondary check for db2 instances and create stubs if necessary (fail if non ha instance already exists!)		* on secondary check for db2 instances and create stubs if necessary (fail if non ha instance already exists!)

Joachim: /* create workflow */

2009-04-08T16:25:46Z

create workflow

← Older revision		Revision as of 16:25, 8 April 2009
Line 13:		Line 13:
	* generate ssh keys for inter node comm.		* generate ssh keys for inter node comm.
	* customize config file and build iso to provide it with the ssh keys, rpms and the node prep command to the new node via cd image		* customize config file and build iso to provide it with the ssh keys, rpms and the node prep command to the new node via cd image
	* start the vm's (or demand admin to start the real machines)		* start the vm's (or demand admin to start the real machines) if they can not be pinged
	* wait for callback from the new nodes (may be automatic, if an autostart mechanism for the cd isos is in place)		* wait for callback from the new nodes (may be automatic, if an autostart mechanism for the cd isos is in place)
	* new node configures ip, hostname, routing and ssh authentication according to config file in iso, if necessary		* new node configures ip, hostname, routing and ssh authentication according to config file in iso, if necessary

Joachim: /* create workflow */

2009-04-08T16:24:17Z

create workflow

Joachim: /* create workflow */

2009-04-08T16:10:22Z

create workflow

← Older revision		Revision as of 16:10, 8 April 2009
Line 14:		Line 14:
	* customize config file and build iso to provide it with the ssh keys, rpms and the node prep command to the new node via cd image		* customize config file and build iso to provide it with the ssh keys, rpms and the node prep command to the new node via cd image
	* start the vm's (or demand admin to start the real machines)		* start the vm's (or demand admin to start the real machines)
	* wait for callback from the new nodes (may be automatic ~~or by hand~~)		* wait for callback from the new nodes (may be automatic, if an autostart mechanism for the cd isos is in place)
	* new node configures ip, hostname, routing and ssh authentication according to config file in iso, if necessary		* new node configures ip, hostname, routing and ssh authentication according to config file in iso, if necessary
	* new node calls back management node with prep status		* new node calls back management node with prep status

Joachim: /* modify workflow */

2009-04-08T16:08:35Z

modify workflow

← Older revision		Revision as of 16:08, 8 April 2009
Line 38:		Line 38:
	like create workflow except skipping the first five steps		like create workflow except skipping the first five steps

	== ~~modify~~ workflow ==		== reconstruct workflow ==
	runs on a cluster node		runs on a cluster node

← Older revision		Revision as of 16:24, 8 April 2009
Line 20:		Line 20:
	* check for required packages (ntp, partitioner, lvm, drbd, heartbeat, db2) on the nodes and install/update if necessary		* check for required packages (ntp, partitioner, lvm, drbd, heartbeat, db2) on the nodes and install/update if necessary
	* check and configure ntp if necessary		* check and configure ntp if necessary
			* check and configure syslog for remote logging if necessary
	* check for required partitions and create if necessary		* check for required partitions and create if necessary
	* check for required vg's and lv's and create if necessary		* check for required vg's and lv's and create if necessary
	* check for required filesystems and create if necessary		* check for required filesystems and create if necessary
	* check for required drbd devices and create if necessary (define primary node with valid data in config file)		* check for required drbd devices and create if necessary (define primary node with valid data in config file)
	* check for hb config and create it if necessary (use custom udp port to allow for more clusters in one subnet, use a unique cluster auth key)		* check for basic hb config and create it if necessary (use custom udp port to allow for more clusters in one subnet, use a unique cluster auth key)
	* on secondary check for db2 instances and create stubs if necessary (fail if non ha instance already exists!)		* on secondary check for db2 instances and create stubs if necessary (fail if non ha instance already exists!)
	* on primary check for db2 instances and create if necessary		* on primary check for db2 instances and create if necessary
	* on primary check if db2 instances are on drbd devices and move if necessary		* on primary check if db2 instances are on drbd devices and move if necessary (includes adding hb resource config)
	* on primary check if databases exist and create if necessary		* on primary check if databases exist and create if necessary (backup or ddl from iso)
	* check for database backup tools and install if necessary		* check for database backup tools and install if necessary
	* check if databases are ~~coverd~~ by db2 backup tool config and add them if necessary		* check if databases are covered by db2 backup tool config and add them if necessary
	* wait for the other node to appear and being in sync		* wait for the other node to appear and being in sync