Managing the Cluster
In general, an appliance that simplifies the creation of a cluster in a computing environment has a fairly straightforward user interface that abstracts out many of the complexities of the typical configuration processes, thereby significantly simplifying the deployment process. By using such appliance, system administrators can deploy an almost turn-key cluster and have the confidence of knowing that the cluster is well tuned for the application/environment that it supports. In addition, the present disclosure allows for configurations and integrations of specialty engines, such as Q processors or J processors, into the cluster. The disclosure provides systems and methods for configuring a cluster, managing a cluster, managing an MQ in a cluster, a user interface for configuring and managing the cluster, an architecture for using specialty engines in a cluster configuration, and interconnect between cluster components, and a file system for use in a cluster.
1 . A computer-implemented method for managing a cluster, the method comprising:
in a first operating system, monitoring the health of individual components within a cluster of at least a first server and a second server running a second operating system different than the first operating system;
presenting to a user the status of the health of the individual components;
presenting a set of fixed options for user selection to manage the cluster;
receiving input from the user in response to the set of fixed options; and
running scripts in response to the input, wherein the scripts reconfigure the cluster.
2 . The method according to claim 1 , further comprising:
reassigning resources to the second server, if individual components within the first server fail.
3 . The method according to claim 2 , wherein reassigning includes starting and stopping resources.
4 . A method according to claim 1 , wherein monitoring includes monitoring the health of individual components at user selected intervals, timeout values, or failure actions.
5 . A method according to claim 1 , wherein individual components include a network, DRBD, MQ file system, or STONITH device.
6 . A method according to claim 1 , wherein the first and second servers are Q processors.
7 . A method according to claim 1 , wherein the first server is an active node and the second server is a passive node.
8 . A method according to claim 1 , further comprising:
presenting advanced features beyond the fixed options for user selection.
9 . A method according to claim 1 , wherein the running scripts configure the cluster by providing a highly available set of MQ resources in a MQ daemon along with the requisite dependencies and constraints for proper functioning.
10 . A method according to claim 1 , wherein receiving input form the user includes receiving input from the user that add pre-defined MQ queue managers, brokers, triggers, channels, or listeners to a resource list.
11 . A method according to claim 1 , wherein presenting a set of fixed options includes presenting a set of fixed options in a graphical user interface running in a first operating system.
12 . A method according to claim 1 , wherein running scripts includes running scripts in the second operating system.
13 . A method according to claim 12 , wherein the second operating system is Linux.
14 . A computer-implemented method for managing a cluster, the method comprising:
in a first operating system, monitoring the health of individual components within a cluster of at least a first QProcessor and a second QProcessor;
presenting to a user the status of the health of the individual components;
presenting a set of fixed options for user selection to manage the cluster;
receiving input from the user in response to the set of fixed options; and
running scripts in response to the input in Linux, wherein the scripts reconfigure the cluster.
15 . The method according to claim 14 , further comprising:
reassigning resources to the second server, if individual components within the first server fail.
16 . The method according to claim 15 , wherein reassigning includes starting and stopping resources.
17 . A method according to claim 14 , wherein monitoring includes monitoring the health of individual components at user selected intervals, timeout values, or failure actions.
18 . A software appliance for managing a cluster, the software appliance comprising:
a first administrative console running on a first server;
a second administrative console running on a second server; and
an administrative module running in an operations server that presents a graphical user interface to a user for monitoring the health of a high availability cluster and for managing the cluster by connecting to the first administrative console and the second administrative console.
19 . A software appliance according to claim 18 , wherein the graphical user interface presents a fixed set of options and receives input from a user.
20 . A software appliance according to claim 19 , wherein the first and second administrative consoles run scripts in response to the input from the user.
21 . A software appliance according to claim 20 , wherein the first and second administrative consoles run in a first operating system and the administrative module runs in a second operating system.
22 . A software appliance according to claim 21 , wherein the first operating system is Linux.