Merge pull request #190 from percona/psc-4581

PS-4581 [DOCS]-Remove mention of CentOS from 8.4

docs/configure-cluster-rhel.md

@@ -1,7 +1,7 @@
 # Configure a cluster on Red Hat-based distributions
 
 This tutorial describes how to install and configure three Percona XtraDB Cluster nodes
-on Red Hat or CentOS 7 servers, using the packages from Percona repositories.
+on Red Hat Enterprise Linux (RHEL) 8 servers, using the packages from Percona repositories.
 
 * Node 1
 
@@ -25,7 +25,7 @@ on Red Hat or CentOS 7 servers, using the packages from Percona repositories.
 
 The procedure described in this tutorial requires the following:
 
-* All three nodes have Red Hat or Red Hat or CentOS 7 installed.
+* All three nodes have Red Hat Enterprise Linux 8 installed.
 
 * The firewall on all nodes is configured to allow connecting
 to ports 3306, 4444, 4567 and 4568.
@@ -36,11 +36,11 @@ to ports 3306, 4444, 4567 and 4568.
 
    The variable `wsrep_sst_auth` has been removed. Percona XtraDB Cluster {{vers}} automatically creates the system user [`mysql.pxc.internal.session`](glossary.md#mysqlpxcinternalsession). During [SST](glossary.md#sst), the user `mysql.pxc.sst.user` and the role [`mysql.pxc.sst.role`](glossary.md#mysqlpxcsstrole) are created on the donor node.
 
-## Step 1. Installing PXC
+## Step 1. Install 
 
-Install Percona XtraDB Cluster on all three nodes as described in [Installing Percona XtraDB Cluster on Red Hat Enterprise Linux or CentOS](yum.md#yum).
+Install Percona XtraDB Cluster on all three nodes as described in [Install on Red Hat Enterprise Linux](yum.md#yum).
 
-## Step 2. Configuring the first node
+## Step 2. Configure the first node
 
 Individual nodes should be configured to be able to bootstrap the cluster.
 For more information about bootstrapping the cluster, see [Bootstrapping the First Node](bootstrap.md#bootstrap).
@@ -76,7 +76,7 @@ on the first node (`percona1`) contains the following:
     wsrep_sst_method=xtrabackup-v2
 
     # Cluster name
-    wsrep_cluster_name=my_centos_cluster
+    wsrep_cluster_name=my_rhel_cluster
     ```
 
 2. Start the first node with the following command:
@@ -140,7 +140,7 @@ on the first node (`percona1`) contains the following:
         Query OK, 0 rows affected (0.00 sec)
         ```
 
-## Step 3. Configuring the second node
+## Step 3. Configure the second node
 
 1. Make sure that the configuration file `/etc/my.cnf` on the second node (`percona2`) contains the following:
 
@@ -169,7 +169,7 @@ on the first node (`percona1`) contains the following:
     wsrep_node_address=192.168.70.72
 
     # Cluster name
-    wsrep_cluster_name=my_centos_cluster
+    wsrep_cluster_name=my_rhel_cluster
 
     # SST method
     wsrep_sst_method=xtrabackup-v2
@@ -211,7 +211,7 @@ on the first node (`percona1`) contains the following:
         40 rows in set (0.01 sec)
         ```
 
-## Step 4. Configuring the third node
+## Step 4. Configure the third node
 
 1. Make sure that the MySQL configuration file `/etc/my.cnf` on the third node (`percona3`) contains the following:
 
@@ -240,7 +240,7 @@ on the first node (`percona1`) contains the following:
     wsrep_node_address=192.168.70.73
 
     # Cluster name
-    wsrep_cluster_name=my_centos_cluster
+    wsrep_cluster_name=my_rhel_cluster
 
     # SST method
     wsrep_sst_method=xtrabackup-v2
@@ -282,7 +282,7 @@ on the first node (`percona1`) contains the following:
         40 rows in set (0.01 sec)
         ```
 
-## Testing replication
+## Test replication
 
 To test replication, lets create a new database on second node,
 create a table for that database on the third node,

docs/configure-nodes.md

@@ -25,8 +25,8 @@ In this section, we will demonstrate how to configure a three node cluster:
     wsrep_cluster_address=gcomm://192.168.70.61,192.168.70.62,192.168.70.63
     ```
 
-    *If you use Red Hat or CentOS*, edit `/etc/my.cnf`. Note that on these systems you set
-    the wsrep_provider option to a different value:
+    *If you use Red Hat Enterprise Linux*, edit `/etc/my.cnf`. Note that on these systems you set
+    the `wsrep_provider option` to a different value:
 
     ```shell
     wsrep_provider=/usr/lib64/galera4/libgalera_smm.so
@@ -87,7 +87,7 @@ In this section, we will demonstrate how to configure a three node cluster:
 
 ## Template of the configuration file
 
-Here is an example of a full configuration file installed on CentOS to
+Here is an example of a full configuration file installed on Red Hat Enterprise Linux to
 `/etc/my.cnf`.
 
 ```text
@@ -142,7 +142,7 @@ Specify the path to the Galera library. The location depends on the distribution
 
 * Debian and Ubuntu: `/usr/lib/galera4/libgalera_smm.so`
 
-* Red Hat and CentOS: `/usr/lib64/galera4/libgalera_smm.so`
+* Red Hat Enterprise Linux: `/usr/lib64/galera4/libgalera_smm.so`
 
 [`wsrep_cluster_name`](wsrep-system-index.md#wsrep_cluster_name)
 

docs/garbd-howto.md

@@ -10,7 +10,7 @@ is a lightweight member of a **Percona XtraDB Cluster**. This member can vote bu
 !!! note
 
     For more information on how to set up a cluster you can read in the
-    [Configuring Percona XtraDB Cluster on Ubuntu](configure-cluster-ubuntu.md#ubuntu-howto) or [Configuring Percona XtraDB Cluster on CentOS](configure-cluster-rhel.md#centos-howto) manuals.
+    [Configuring Percona XtraDB Cluster on Ubuntu](configure-cluster-ubuntu.md#ubuntu-howto) or [Configure on Red Hat Enterprise Linux](configure-cluster-rhel.md#centos-howto) manuals.
 
 ## Installation
 

docs/haproxy.md

@@ -13,7 +13,7 @@ Debian or Ubuntu
     $ sudo apt install haproxy
     ```
 
-Red Hat or CentOS:
+Red Hat Enterprise Linux:
 
     ```{.bash data-prompt="$"}
     $ sudo yum update

docs/install-index.md

@@ -10,7 +10,7 @@ using the corresponding package manager for your system:
 
 * [Debian or Ubuntu](apt.md#apt)
 
-* [Red Hat or CentOS](yum.md#yum)
+* [Red Hat Enterprise Linux](yum.md#yum)
 
 !!! important
 

docs/load-balance-proxysql.md

@@ -58,7 +58,7 @@ root@proxysql:~# apt install percona-xtradb-cluster-client
 root@proxysql:~# apt install proxysql2
 ```
 
-* On Red Hat Enterprise Linux or CentOS for ProxySQL 2.x:
+* On Red Hat Enterprise Linux for ProxySQL 2.x:
 
 ```{.bash data-prompt="$"}
 $ sudo yum install Percona-XtraDB-Cluster-client-80
@@ -379,7 +379,7 @@ You can install `sysbench` from Percona software repositories:
 root@proxysql:~# apt install sysbench
 ```
 
-* For Red Hat Enterprise Linux or CentOS
+* For Red Hat Enterprise Linux
 
 ```{.bash data-prompt="root@proxysql:~#"}
 root@proxysql:~# yum install sysbench

docs/selinux.md

@@ -10,7 +10,7 @@ SELinux helps protects the user’s home directory data. SELinux provides the fo
 
 For more information, see [Percona Server and SELinux](https://www.percona.com/doc/percona-server/LATEST/security/selinux.html)
 
-Red Hat and CentOS distributes a policy module to extend the SELinux policy module for mysqld. We provide the following:
+Red Hat Enterprise Linux (RHEL) distributes a policy module to extend the SELinux policy module for `mysqld`. We provide the following:
 
 * Extended module for pxc - an extension of the default module for mysqld distributed by the operating system.
 
@@ -120,6 +120,3 @@ After ensuring that the system journal does not list any issues, the administrat
 $ semanage permissive -d mysqld_t
 ```
 
-!!! admonition "See also"
-
-    [MariaDB 10.2 Galera Cluster with SELinux-enabled on CentOS 7](https://ospi.fi/blog/mariadb-10-2-galera-cluster-with-selinux-enabled-on-centos-7.html)

docs/set-up-3nodes-ec2.md

@@ -37,7 +37,7 @@ To set up Percona XtraDB Cluster:
 
     * Percona Server for MySQL 5.6, 5.7
 
-2. Install Percona XtraDB Cluster as described in [Installing Percona XtraDB Cluster on Red Hat Enterprise Linux and CentOS](yum.md#yum).
+2. Install Percona XtraDB Cluster with [Install on Red Hat Enterprise Linux](yum.md#yum).
 
 3. Create data directories:
 

docs/tarball.md

@@ -1,23 +1,13 @@
-# Install Percona XtraDB Cluster from Binary Tarball
+# Install from Binary Tarball
 
 Percona provides generic tarballs with all required files and binaries
 for manual installation.
 
 You can download the appropriate tarball package from
-[https://www.percona.com/downloads/Percona-XtraDB-Cluster-80](https://www.percona.com/downloads/Percona-XtraDB-Cluster-80)
+[Percona Software Downloads](https://www.percona.com/downloads).
 
 ### Version updates
 
-Starting with *Percona XtraDB Cluster* 8.0.20-11, the **Linux - Generic**
-section lists only full or minimal tar files. Each tarball file replaces the
-multiple tar file listing used in earlier versions and supports all
-distributions.
-
-!!! important
-
-    Starting with *Percona XtraDB Cluster* 8.0.21, Percona does not provide a
-    tarball for RHEL 6/CentOS 6 (glibc2.12).
-
 The version number in the tarball name must be substituted with
 the appropriate version number for your system. To indicate that such a
 substitution is needed in statements, we use `<version-number>`.
@@ -27,20 +17,6 @@ substitution is needed in statements, we use `<version-number>`.
 | Percona-XtraDB-Cluster_<version-number>-Linux.x86_64.glibc2.17.tar.gz| Full| Contains binary files, libraries, test files, and debug symbols|
 | Percona-XtraDB-Cluster_<version-number>-Linux.x86_64.glibc2.17.minimal.tar.gz| Minimal| Contains binary files and libraries but does not include test files, or debug symbols|
 
-For installations before *Percona XtraDB Cluster* 8.0.20-11, the **Linux - Generic** section contains multiple tarballs based on the operating system names:
-
-```{.text .no-copy}
-Percona-XtraDB-Cluster_8.0.18-9.3_Linux.x86_64.bionic.tar.gz
-Percona-XtraDB-Cluster_8.0.18-9.3_Linux.x86_64.buster.tar.gz
-...
-```
-
-For example, you can use `curl` as follows:
-
-```{.bash data-prompt="$"}
-$ curl -O https://downloads.percona.com/downloads/Percona-XtraDB-Cluster-LATEST/Percona-XtraDB-Cluster-8.0.27/binary/tarball/Percona-XtraDB-Cluster_8.0.27-18.1_Linux.x86_64.glibc2.17-minimal.tar.gz
-```
-
 Check your system to make sure the packages that the PXC
 version requires are installed.
 
@@ -53,7 +29,7 @@ libaio1 libc6 libcurl3 libev4 libgcc1 libgcrypt20 \
 libgpg-error0 libssl1.1 libstdc++6 zlib1g libatomic1
 ```
 
-### For Red Hat Enterprise Linux or CentOS:
+### For Red Hat Enterprise Linux:
 
 ```{.bash data-prompt="$"}
 $ sudo yum install -y openssl socat  \

docs/upgrade-guide.md

@@ -79,7 +79,7 @@ All configuration settings are stored in the default MySQL configuration file:
 
 * Path on Debian and Ubuntu: `/etc/mysql/mysql.conf.d/mysqld.cnf`
 
-* Path on Red Hat and CentOS: `/etc/my.cnf`
+* Path on Red Hat Enterprise Linux: `/etc/my.cnf`
 
 After you check the log for any tech preview features or unsupported features
 and you have fixed any of the encountered incompatibilities, set the variable
@@ -97,12 +97,11 @@ All configuration settings are stored in the default MySQL configuration file:
 
 * Path on Debian and Ubuntu: `/etc/mysql/mysql.conf.d/mysqld.cnf`
 
-* Path on Red Hat and CentOS: /etc/my.cnf
+* Path on Red Hat Enterprise Linux: /etc/my.cnf
 
 Before you start the upgrade, move your custom settings from
 `/etc/mysql/percona-xtradb-cluster.conf.d/wsrep.cnf` (on Debian and
-Ubuntu) or from `/etc/percona-xtradb-cluster.conf.d/wsrep.cnf` (on Red Hat
-and CentOS) to the new location accordingly.
+Ubuntu) or from `/etc/percona-xtradb-cluster.conf.d/wsrep.cnf` (on Red Hat Enterprise Linux) to the new location accordingly.
 
 !!! note
 
@@ -141,7 +140,7 @@ $ sudo service mysql stop -->
 
 For example, if you have Percona software repositories configured,
 you might use the following commands: -->
-<!-- * On CentOS or RHEL:
+<!-- * On RHEL:
 
 .. code-block: bash
 
@@ -350,7 +349,7 @@ state transfer (IST/SST).
 
     !!! note
 
-        On CentOS, the /etc/my.cnf configuration file is renamed to `my.cnf.rpmsave`. Make sure to rename it back before joining the upgraded node back to the cluster.
+        On Red Hat Enterprise Linux, the /etc/my.cnf configuration file is renamed to `my.cnf.rpmsave`. Make sure to rename it back before joining the upgraded node back to the cluster.
 
 
     [PXC Strict Mode](strict-mode.md#pxc-strict-mode) is enabled by default, which may result in denying any

docs/virtual-sandbox.md

@@ -4,8 +4,8 @@ This section describes how to set up Percona XtraDB Cluster in a virtualized tes
 based on ProxySQL. To test the cluster, we will use the sysbench benchmark
 tool.
 
-It is assumed that each PXC node is installed on Amazon EC2 micro instances
-running CentOS 7.  However, the information in this section should apply if you
+It is assumed that each PXC node is installed on Amazon T2.micro instances
+running RHEL 8.  However, the information in this section should apply if you
 used another virtualization technology (for example, VirtualBox) with any Linux
 distribution.
 
@@ -16,7 +16,7 @@ more virtual machine has ProxySQL, which redirects requests to the nodes.
 
     Running ProxySQL on an application server, instead of having it as a dedicated entity, removes the unnecessary extra network roundtrip, because the load balancing layer in Percona XtraDB Cluster scales well with application servers.
 
-1. Install Percona XtraDB Cluster on three cluster nodes, as described in [Configuring Percona XtraDB Cluster on CentOS](configure-cluster-rhel.md#centos-howto).
+1. Install Percona XtraDB Cluster on three cluster nodes, as described in [Configure on RHEL](configure-cluster-rhel.md#centos-howto).
 
 2. On the client node, install [ProxySQL](load-balance-proxysql.md#load-balancing-with-proxysql) and `sysbench`:
 
@@ -502,6 +502,6 @@ different name):
 **Related sections and additional reading**
 
 * [Load balancing with ProxySQL](load-balance-proxysql.md#load-balancing-with-proxysql)
-* [Configuring Percona XtraDB Cluster on CentOS](configure-cluster-rhel.md#centos-howto)
+* [Configure on RHEL](configure-cluster-rhel.md#centos-howto)
 * [Percona Blog post: ProxySQL Native Support for Percona XtraDB Cluster (PXC)](https://www.percona.com/blog/2019/02/20/proxysql-native-support-for-percona-xtradb-cluster-pxc/)
 * [GitHub repository for the sysbench benchmarking tool](https://github.com/akopytov/sysbench/)