Long-Term Supported Versions

    Innovation Versions

      Installing and Deploying an HA Cluster

      This section describes how to install and deploy an HA cluster.


      Installation and Deployment

      Preparing the Environment

      At least two physical machines or virtual machines (VMs) installed with openEuler 21.03 are required. This section uses two physical machines or VMs as an example. For details about how to install openEuler 21.03, see the installation guide.

      Modifying the Host Name and the /etc/hosts File

      Note: You need to perform the following operations on both hosts. The following uses one host as an example. The IP address used in this section is for reference only.

      Before using the HA software, ensure that the host name has been changed and all host names have been written into the /etc/hosts file.

      1. Run the following command to change the host name:

        hostnamectl set-hostname ha1
      2. Edit the /etc/hosts file and write the following fields: ha1 ha2

      Configuring the Yum Source

      After the system is successfully installed, the Yum source is configured by default. The file location is stored in the /etc/yum.repos.d/openEuler.repo file. The HA software package uses the following sources:


      Installing the Components of the HA Software Package

      yum install -y corosync pacemaker pcs fence-agents fence-virt corosync-qdevice sbd drbd drbd-utils

      Setting the hacluster User Password

      passwd hacluster

      Modifying the /etc/corosync/corosync.conf file

      totem {
              version: 2
              cluster_name: hacluster
               crypto_cipher: none
              crypto_hash: none
      logging {         
              fileline: off
              to_stderr: yes
              to_logfile: yes
              logfile: /var/log/cluster/corosync.log
              to_syslog: yes
              debug: on
             logger_subsys {
                     subsys: QUORUM
                     debug: on
      quorum {
                 provider: corosync_votequorum
                 expected_votes: 2
                 two_node: 1
      nodelist {
             node {
                     name: ha1
                     nodeid: 1
              node {
                     name: ha2
                     nodeid: 2

      Managing Services

      Disabling the Firewall

      1. Run the following command to disable the firewall:

        systemctl stop firewalld
      2. Change SELinux to disabled in the /etc/selinux/config file.

        # SELINUX=disabled

      Managing the pcs Service

      1. Run the following command to start the pcs service:

        systemctl start pcsd
      2. Run the following command to query the pcs service status:

        systemctl status pcsd

        The service is started successfully if the following information is displayed:

      Managing the Pacemaker Service

      1. Run the following command to start the Pacemaker service:

        systemctl start pacemaker
      2. Run the following command to query the Pacemaker service status:

        systemctl status pacemaker

        The service is started successfully if the following information is displayed:

      Managing the Corosync Service

      1. Run the following command to start the Corosync service:

        systemctl start corosync
      2. Run the following command to query the Corosync service status:

        systemctl status corosync

        The service is started successfully if the following information is displayed:

      Performing Node Authentication

      Note: Perform this operation on either node.

      pcs host auth ha1 ha2

      Accessing the Front-End Management Platform

      After the preceding services are started, open the browser (Chrome or Firefox is recommended) and enter https://localhost:2224 in the address box.

      • The following figure shows the native management platform:

      For details about how to install the management platform newly developed by the community, see https://gitee.com/openeuler/ha-api/blob/master/docs/build.md.

      • The following is the management platform newly developed by the community:

      Note: only the Chinese version is available.

      Bug Catching

      Buggy Content

      Bug Description

      Submit As Issue

      It's a little complicated....

      I'd like to ask someone.


      Just a small problem.

      I can fix it online!

      Bug Type
      Specifications and Common Mistakes

      ● Misspellings or punctuation mistakes;

      ● Incorrect links, empty cells, or wrong formats;

      ● Chinese characters in English context;

      ● Minor inconsistencies between the UI and descriptions;

      ● Low writing fluency that does not affect understanding;

      ● Incorrect version numbers, including software package names and version numbers on the UI.


      ● Incorrect or missing key steps;

      ● Missing prerequisites or precautions;

      ● Ambiguous figures, tables, or texts;

      ● Unclear logic, such as missing classifications, items, and steps.


      ● Technical principles, function descriptions, or specifications inconsistent with those of the software;

      ● Incorrect schematic or architecture diagrams;

      ● Incorrect commands or command parameters;

      ● Incorrect code;

      ● Commands inconsistent with the functions;

      ● Wrong screenshots.

      Risk Warnings

      ● Lack of risk warnings for operations that may damage the system or important data.

      Content Compliance

      ● Contents that may violate applicable laws and regulations or geo-cultural context-sensitive words and expressions;

      ● Copyright infringement.

      How satisfied are you with this document

      Not satisfied at all
      Very satisfied
      Click to create an issue. An issue template will be automatically generated based on your feedback.
      Bug Catching
      编组 3备份