The Sun Cluster product is an integrated hardware and software solution that you use to create highly available and scalable services. Sun Cluster Concepts Guide for Solaris OS provides the conceptual information that you need to gain a more complete picture of the Sun Cluster product. Use this book with the entire Sun Cluster documentation set to provide a complete view of the Sun Cluster software.
This chapter provides an overview of the general concepts that underlie the Sun Cluster product.
This chapter does the following:
Provides an introduction and high-level overview of the Sun Cluster software
Describes the several views of the Sun Cluster audience
Identifies key concepts that you need to understand before you use the Sun Cluster software
Maps key concepts to the Sun Cluster documentation that includes procedures and related information
Maps cluster-related tasks to the documentation that contains procedures that you use to complete those tasks
This chapter contains the following sections:
The Sun Cluster environment extends the Solaris Operating System into a cluster operating system. A cluster is a collection of one or more nodes that belong exclusively to that collection. In a cluster that runs on the Solaris 10 OS, a global cluster and a zone cluster are types of clusters.
In a cluster that runs on any version of the Solaris OS that was released before the Solaris 10 OS, a node is a physical machine that contributes to cluster membership and is not a quorum device. In a cluster that runs on the Solaris 10 OS, the concept of a node changes. In this environment, a node is a Solaris zone that is associated with a cluster. In this environment, a Solaris host, or simply host, is one of the following hardware or software configurations that runs the Solaris OS and its own processes:
A “bare metal” physical machine that is not configured with a virtual machine or as a hardware domain
A Sun Logical Domains (LDoms) guest domain
A Sun Logical Domains (LDoms) I/O domain
A hardware domain
These processes communicate with one another to form what looks like (to a network client) a single system that cooperatively provides applications, system resources, and data to users.
In a Solaris 10 environment, a global cluster is a type of cluster that is composed only of one or more global-cluster voting nodes and optionally, zero or more global-cluster non-voting nodes.
A global cluster can optionally also include solaris8, solaris9, lx (linux), or native brand, non-global zones that are not nodes, but high availability containers (as resources).
A global-cluster voting node is a native brand, global zone in a global cluster that contributes votes to the total number of quorum votes, that is, membership votes in the cluster. This total determines whether the cluster has sufficient votes to continue operating. A global-cluster non-voting node is a native brand, non-global zone in a global cluster that does not contribute votes to the total number of quorum votes, that is, membership votes in the cluster.
In a Solaris 10 environment, a zone cluster is a type of cluster that is composed only of one or more cluster brand, voting nodes. A zone cluster depends on, and therefore requires, a global cluster. A global cluster does not contain a zone cluster. You cannot configure a zone cluster without a global cluster. A zone cluster has, at most, one zone cluster node on a machine.
A zone-cluster node continues to operate only as long as the global-cluster voting node on the same machine continues to operate. If a global-cluster voting node on a machine fails, all zone-cluster nodes on that machine fail as well.
A cluster offers several advantages over traditional single-server systems. These advantages include support for failover and scalable services, capacity for modular growth, and low entry price compared to traditional hardware fault-tolerant systems.
The goals of the Sun Cluster software are:
Reduce or eliminate system downtime because of software or hardware failure
Ensure availability of data and applications to end users, regardless of the kind of failure that would normally take down a single-server system
Increase application throughput by enabling services to scale to additional processors by adding nodes to the cluster
Provide enhanced availability of the system by enabling you to perform maintenance without shutting down the entire cluster
For more information about fault tolerance and high availability, see Making Applications Highly Available With Sun Cluster in Sun Cluster Overview for Solaris OS.
Refer to High Availability FAQs for questions and answers on high availability.
This section describes three different views of the Sun Cluster software and the key concepts and documentation relevant to each view.
These views are typical for the following professionals:
Hardware installation and service personnel
System administrators
Application developers
To hardware service professionals, the Sun Cluster software looks like a collection of off-the-shelf hardware that includes servers, networks, and storage. These components are all cabled together so that every component has a backup and no single point of failure exists.
Hardware service professionals need to understand the following cluster concepts.
Cluster hardware configurations and cabling
Installing and servicing (adding, removing, replacing):
Network interface components (adapters, junctions, cables)
Disk interface cards
Disk arrays
Disk drives
The administrative console and the console access device
Setting up the administrative console and console access device
The following sections contain material relevant to the preceding key concepts:
The Sun Cluster 3.1 - 3.2 Hardware Administration Manual for Solaris OS includes procedures and information that are associated with hardware service concepts.
To the system administrator, the Sun Cluster product is a set of Solaris hosts that share storage devices.
The system administrator sees software that performs specific tasks:
Specialized cluster software that is integrated with Solaris software to monitor the connectivity between Solaris hosts in the cluster
Specialized software that monitors the health of user application programs that are running on the cluster nodes
Volume management software that sets up and administers disks
Specialized cluster software that enables all Solaris hosts to access all storage devices, even those Solaris hosts that are not directly connected to disks
Specialized cluster software that enables files to appear on every Solaris host as though they were locally attached to that Solaris host
System administrators need to understand the following concepts and processes:
The interaction between the hardware and software components
The general flow of how to install and configure the cluster including:
Installing the Solaris Operating System
Installing and configuring Sun Cluster software
Installing and configuring a volume manager
Installing and configuring application software to be cluster ready
Installing and configuring Sun Cluster data service software
Cluster administrative procedures for adding, removing, replacing, and servicing cluster hardware and software components
Configuration modifications to improve performance
The following sections contain material relevant to the preceding key concepts:
The following Sun Cluster documents include procedures and information associated with the system administration concepts:
The Sun Cluster software provides data services for such applications as Oracle, NFS, DNS, Sun Java System Web Server, Apache Web Server (on SPARC based systems), and Sun Java System Directory Server. Data services are created by configuring off-the-shelf applications to run under control of the Sun Cluster software. The Sun Cluster software provides configuration files and management methods that start, stop, and monitor the applications. If you need to create a new failover or scalable service, you can use the Sun Cluster Application Programming Interface (API) and the Data Service Enabling Technologies API (DSET API) to develop the necessary configuration files and management methods that enable its application to run as a data service on the cluster.
Application developers need to understand the following:
The characteristics of their application to determine whether it can be made to run as a failover or scalable data service.
The Sun Cluster API, DSET API, and the “generic” data service. Developers need to determine which tool is most suitable for them to use to write programs or scripts to configure their application for the cluster environment.
The following sections contain material relevant to the preceding key concepts:
The following Sun Cluster documents include procedures and information associated with the application developer concepts:
All Sun Cluster software tasks require some conceptual background. The following table provides a high-level view of the tasks and the documentation that describes task steps. The concepts sections in this book describe how the concepts map to these tasks.
Table 1–1 Task Map: Mapping User Tasks to Documentation
Task |
Instructions |
---|---|
Install cluster hardware |
Sun Cluster 3.1 - 3.2 Hardware Administration Manual for Solaris OS |
Install Solaris software on the cluster | |
SPARC: Install SunTM Management Center software | |
Install and configure Sun Cluster software | |
Install and configure volume management software |
Sun Cluster Software Installation Guide for Solaris OS Your volume management documentation |
Install and configure Sun Cluster data services |
Sun Cluster Data Services Planning and Administration Guide for Solaris OS |
Service cluster hardware |
Sun Cluster 3.1 - 3.2 Hardware Administration Manual for Solaris OS |
Administer Sun Cluster software | |
Administer volume management software |
Sun Cluster System Administration Guide for Solaris OS and your volume management documentation |
Administer application software |
Your application documentation |
Problem identification and suggested user actions | |
Create a new data service |