Install workflow: Difference between revisions
Jump to navigation
Jump to search
(New page: == main workflow == * parse commandline for create/modify/reconstruct mode, config file and config file option replacements ** create: setup and start new vm's as cluster nodes and configu...) |
|||
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 vm via cd image | * customize config file and build iso to provide it with the ssh keys, rpms and the node prep command to vm via cd image | ||
* start vm | * start the vm's | ||
* vm configures ip, hostname, routing and ssh authentication according to config file in iso | * wait for callback from the vm's (may be automatic or by hand) | ||
* vm configures ip, hostname, routing and ssh authentication according to config file in iso, if necessary | |||
* vm calls back management node with prep status | * vm calls back management node with prep status | ||
* callback provides node prep status and triggers node customization. | * callback provides node prep status and triggers node customization. | ||
* check for required packages (partitioner, lvm, drbd, heartbeat, db2) on the nodes and install if necessary | * check for required packages (ntp, partitioner, lvm, drbd, heartbeat, db2) on the nodes and install/update if necessary | ||
* check and | * check and configure ntp if necessary | ||
* check for required partitions and create if necessary | * check for required partitions and create if necessary | ||
* check for required vm's and lv's and create if necessary | * check for required vm's and lv's and create if necessary | ||
Line 31: | Line 32: | ||
* check if databases are coverd by db2 backup tool config and add them if necessary | * check if databases are coverd 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 | ||
== modify workflow == | |||
like create workflow except skipping the first five steps |
Revision as of 15:59, 8 April 2009
main workflow
- parse commandline for create/modify/reconstruct mode, config file and config file option replacements
- create: setup and start new vm's as cluster nodes and configure them according to config file
- modify: use existing nodes
- reconstruct: generate config file from existing servers
- read config file
- validate config file
- act according to command mode
create workflow
- copy existing vm stub
- modify vm stub to contain new uuids and mac addresses
- 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 vm via cd image
- start the vm's
- wait for callback from the vm's (may be automatic or by hand)
- vm configures ip, hostname, routing and ssh authentication according to config file in iso, if necessary
- vm calls back management node with prep status
- callback provides node prep status and triggers node customization.
- 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 for required partitions and create if necessary
- check for required vm's and lv's 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 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 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 databases exist and create 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
- wait for the other node to appear and being in sync
modify workflow
like create workflow except skipping the first five steps