documentation.suse.com › Documentazione di SUSE Linux Enterprise High Availability Extension › Administration Guide › About This Guide

Administration Guide

Navigation←→

Applies to SUSE Linux Enterprise High Availability Extension 15 SP1

About This Guide #

Abstract#

This guide is intended for administrators who need to set up, configure, and maintain clusters with SUSE® Linux Enterprise High Availability Extension. For quick and efficient configuration and administration, the product includes both a graphical user interface and a command line interface (CLI). For performing key tasks, both approaches are covered in this guide. Thus, you can choose the appropriate tool that matches your needs.

Available Documentation
Feedback
Documentation Conventions
About the Making of This Documentation

This guide is divided into the following parts:

Installation, Setup and Upgrade: Before starting to install and configure your cluster, make yourself familiar with cluster fundamentals and architecture, get an overview of the key features and benefits. Learn which hardware and software requirements must be met and what preparations to take before executing the next steps. Perform the installation and basic setup of your HA cluster using YaST. Learn how to upgrade your cluster to the most recent release version or how to update individual packages.
Configuration and Administration: Add, configure and manage cluster resources with either the Web interface (Hawk2), or the command line interface (crmsh). To avoid unauthorized access to the cluster configuration, define roles and assign them to certain users for fine-grained control. Learn how to use load balancing and fencing. If you consider writing your own resource agents or modifying existing ones, get some background information on how to create different types of resource agents.
Storage and Data Replication: SUSE Linux Enterprise High Availability Extension ships with the cluster-aware file systems OCFS2 and GFS2, and the Cluster Logical Volume Manager (Cluster LVM). For replication of your data, use DRBD*. It lets you mirror the data of a High Availability service from the active node of a cluster to its standby node. Furthermore, a clustered Samba server also provides a High Availability solution for heterogeneous environments.
Appendix: Contains an overview of common problems and their solution. Presents the naming conventions used in this documentation with regard to clusters, resources and constraints. Contains a glossary with HA-specific terminology.

1 Available Documentation #

Note: Online Documentation and Latest Updates

Documentation for our products is available at http://www.suse.com/documentation/, where you can also find the latest updates, and browse or download the documentation in various formats. The latest documentation updates can usually be found in the English language version.

The following documentation is available for this product:

Installation and Setup Quick Start: This document guides you through the setup of a very basic two-node cluster, using the bootstrap scripts provided by the ha-cluster-bootstrap package. This includes the configuration of a virtual IP address as a cluster resource and the use of SBD on shared storage as a node fencing mechanism.
Administration Guide: This guide is intended for administrators who need to set up, configure, and maintain clusters with SUSE® Linux Enterprise High Availability Extension. For quick and efficient configuration and administration, the product includes both a graphical user interface and a command line interface (CLI). For performing key tasks, both approaches are covered in this guide. Thus, you can choose the appropriate tool that matches your needs.
Highly Available NFS Storage with DRBD and Pacemaker: This document describes how to set up highly available NFS storage in a two-node cluster, using the following components: DRBD* (Distributed Replicated Block Device), LVM (Logical Volume Manager), and Pacemaker as cluster resource manager.
Pacemaker Remote Quick Start: This document guides you through the setup of a High Availability cluster with a remote node or a guest node, managed by Pacemaker and pacemaker_remote. Remote in pacemaker_remote does not refer to physical distance, but to the special status of nodes that do not run the complete cluster stack and thus are not regular members of the cluster.
Geo Clustering Quick Start: Geo clustering protects workloads across globally distributed data centers. This document guides you through the basic setup of a Geo cluster, using the Geo bootstrap scripts provided by the ha-cluster-bootstrap package.
Geo Clustering Guide: This document covers the setup options and parameters for Geo clusters and their components, such as booth ticket manager, the specific Csync2 setup, and the configuration of the required cluster resources (and how to transfer them to other sites in case of changes). Learn how to monitor and manage Geo clusters from command line or with the Hawk2 Web interface.

2 Feedback #

Several feedback channels are available:

Bugs and Enhancement Requests

For services and support options available for your product, refer to http://www.suse.com/support/.

To report bugs for a product component, go to https://scc.suse.com/support/requests, log in, and click Create New.

User Comments

We want to hear your comments about and suggestions for this manual and the other documentation included with this product. Use the User Comments feature at the bottom of each page in the online documentation or go to http://www.suse.com/doc/feedback.html and enter your comments there.

Mail

For feedback on the documentation of this product, you can also send a mail to doc-team@suse.com. Make sure to include the document title, the product version and the publication date of the documentation. To report errors or suggest enhancements, provide a concise description of the problem and refer to the respective section number and page (or URL).

3 Documentation Conventions #

The following notices and typographical conventions are used in this documentation:

```
tux > command
```
Commands that can be run by any user, including the root user.
```
root # command
```
Commands that must be run with root privileges. Often you can also prefix these commands with the sudo command to run them.
```
crm(live)# 
```
Commands executed in the interactive crm shell. For details, see Chapter 8, Configuring and Managing Cluster Resources (Command Line).
/etc/passwd: directory names and file names
PLACEHOLDER: replace PLACEHOLDER with the actual value
PATH: the environment variable PATH
ls, --help: commands, options, and parameters
user: users or groups
packagename: name of a package
Alt, Alt–F1: a key to press or a key combination; keys are shown in uppercase as on a keyboard
File, File › Save As: menu items, buttons
amd64, em64t, ipf This paragraph is only relevant for the architectures amd64, em64t, and ipf. The arrows mark the beginning and the end of the text block.
Dancing Penguins (Chapter Penguins, ↑Another Manual): This is a reference to a chapter in another manual.
Notices
Warning
Vital information you must be aware of before proceeding. Warns you about security issues, potential loss of data, damage to hardware, or physical hazards.
Important
Important information you should be aware of before proceeding.
Note
Additional information, for example about differences in software versions.
Tip
Helpful information, like a guideline or a piece of practical advice.

For an overview of naming conventions with regard to cluster nodes and names, resources, and constraints, see Appendix B, Naming Conventions.

4 About the Making of This Documentation #

This documentation is written in GeekoDoc, a subset of DocBook 5. The XML source files were validated by jing (see https://code.google.com/p/jing-trang/), processed by xsltproc, and converted into XSL-FO using a customized version of Norman Walsh's stylesheets. The final PDF is formatted through FOP from Apache Software Foundation. The open source tools and the environment used to build this documentation are provided by the DocBook Authoring and Publishing Suite (DAPS). The project's home page can be found at https://github.com/openSUSE/daps.

The XML source code of this documentation can be found at https://github.com/SUSE/doc-sleha.

Print this page