-
Notifications
You must be signed in to change notification settings - Fork 249
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #2538 from EnterpriseDB/release/2022-04-08
Release: 2022-04-08
- Loading branch information
Showing
76 changed files
with
4,057 additions
and
1,021 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
16 changes: 0 additions & 16 deletions
16
product_docs/docs/efm/4/03_installing_efm/13_initial_config.mdx
This file was deleted.
Oops, something went wrong.
77 changes: 77 additions & 0 deletions
77
...uct_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,77 @@ | ||
--- | ||
title: "Installing Failover Manager on RHEL 8 IBM Power (ppc64le)" | ||
navTitle: "RHEL 8 " | ||
--- | ||
|
||
There are three steps to completing an installation: | ||
|
||
- Setting up the repository | ||
- Installing the package | ||
- Initial configuration | ||
|
||
For each step, you must be logged in as superuser. | ||
|
||
To log in as a superuser: | ||
|
||
```shell | ||
sudo su - | ||
``` | ||
|
||
## Setting up the repository | ||
|
||
1. To register with EDB to receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). | ||
|
||
1. Set up the EDB repository: | ||
|
||
```shell | ||
dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm | ||
``` | ||
|
||
This creates the /etc/yum.repos.d/edb.repo configuration file. | ||
|
||
1. Add your EDB credentials to the edb.repo file: | ||
|
||
```shell | ||
sed -i "s@<username>:<password>@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo | ||
``` | ||
|
||
Where `USERNAME:PASSWORD` is the username and password available from your | ||
[EDB account](https://www.enterprisedb.com/user). | ||
|
||
1. Install the EPEL repository and refresh the cache: | ||
|
||
```shell | ||
dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm | ||
dnf makecache | ||
``` | ||
|
||
1. Enable the codeready-builder-for-rhel-8-\*-rpms repository since EPEL packages may depend on packages from it: | ||
|
||
```shell | ||
ARCH=$( /bin/arch ) | ||
subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" | ||
``` | ||
|
||
1. Disable the built-in PostgreSQL module: | ||
```shell | ||
dnf -qy module disable postgresql | ||
``` | ||
|
||
## Installing the package | ||
|
||
```shell | ||
dnf -y install edb-efm<xx> | ||
``` | ||
where `<xx>` is the version number of Failover Manager. | ||
|
||
## Initial configuration | ||
|
||
If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). | ||
|
||
After installing on each node of the cluster: | ||
|
||
1. Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. | ||
2. Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node. | ||
3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. | ||
4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/#controlling-the-failover-manager-service). | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
64 changes: 64 additions & 0 deletions
64
...ct_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/11_efm4_sles15_ppcle.mdx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,64 @@ | ||
--- | ||
title: "Installing Failover Manager on SLES 15 IBM Power (ppc64le)" | ||
navTitle: "SLES 15" | ||
--- | ||
|
||
|
||
There are three steps to completing an installation: | ||
|
||
- [Setting up the repository](#setting-up-the-repository) | ||
- [Installing the package](#installing-the-package) | ||
- [Performing the initial configuration](#initial-configuration) | ||
|
||
For each step, you must be logged in as superuser. | ||
|
||
```shell | ||
# To log in as a superuser: | ||
sudo su - | ||
``` | ||
|
||
Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). | ||
|
||
## Setting up the repository | ||
|
||
Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. | ||
|
||
```shell | ||
# Install the repository configuration and enter your EDB repository | ||
# credentials when prompted | ||
zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo | ||
|
||
# Install SUSEConnect to register the host with SUSE, allowing access to | ||
# SUSE repositories | ||
zypper install SUSEConnect | ||
|
||
# Register the host with SUSE, allowing access to SUSE repositories | ||
# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE registration | ||
# information | ||
SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' | ||
|
||
# Activate the required SUSE module | ||
SUSEConnect -p PackageHub/15.3/ppc64le | ||
|
||
# Refresh the metadata | ||
zypper refresh | ||
``` | ||
|
||
## Installing the package | ||
|
||
```shell | ||
zypper -n install edb-efmedb-efm<4x> | ||
``` | ||
|
||
Where <4x> is the version of Failover Manager you are installing. | ||
|
||
## Initial configuration | ||
|
||
If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). | ||
|
||
After installing on each node of the cluster: | ||
|
||
1. Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. | ||
2. Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node. | ||
3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. | ||
4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/#controlling-the-failover-manager-service). |
65 changes: 65 additions & 0 deletions
65
...ct_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/12_efm4_sles12_ppcle.mdx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,65 @@ | ||
--- | ||
title: "Installing Failover Manager on SLES 12 IBM Power (ppc64le)" | ||
navTitle: "SLES 12" | ||
--- | ||
|
||
There are two steps to completing an installation: | ||
|
||
- [Setting up the repository](#setting-up-the-repository) | ||
- [Installing the package](#installing-the-package) | ||
- [Initial configuration](#initial-configuration) | ||
|
||
|
||
For each step, you must be logged in as superuser. | ||
|
||
```shell | ||
# To log in as a superuser: | ||
sudo su - | ||
``` | ||
|
||
Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). | ||
|
||
## Setting up the Repository | ||
|
||
Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. | ||
|
||
```shell | ||
# Install the repository configuration and enter your EDB repository | ||
# credentials when prompted | ||
zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo | ||
|
||
# Install SUSEConnect to register the host with SUSE, allowing access to | ||
# SUSE repositories | ||
zypper install SUSEConnect | ||
|
||
# Register the host with SUSE, allowing access to SUSE repositories | ||
# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE registration | ||
# information | ||
SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL' | ||
|
||
# Activate the required SUSE modules | ||
SUSEConnect -p PackageHub/12.5/ppc64le | ||
SUSEConnect -p sle-sdk/12.5/ppc64le | ||
|
||
# Refresh the metadata | ||
zypper refresh | ||
``` | ||
|
||
## Installing the Package | ||
|
||
```shell | ||
zypper -n install edb-efm<4x> | ||
``` | ||
|
||
Where <4x> is the version of Failover Manager you are installing. | ||
|
||
## Initial configuration | ||
|
||
If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). | ||
|
||
After installing on each node of the cluster: | ||
|
||
1. Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. | ||
2. Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node. | ||
3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. | ||
4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/#controlling-the-failover-manager-service). |
16 changes: 16 additions & 0 deletions
16
product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/index.mdx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
--- | ||
title: "Installing Failover Manager on IBM Power (ppc64le)" | ||
navTitle: "IBM Power (ppc64le)" | ||
--- | ||
|
||
<div id="installing_efm" class="registered_link"></div> | ||
|
||
<div id="linux_installation" class="registered_link"></div> | ||
|
||
For operating system-specific install instructions, including accessing the repo, see: | ||
|
||
- [RHEL 8](09_efm4_rhel8_ppcle) | ||
|
||
- [RHEL 7](10_efm4_rhel7_ppcle) | ||
- [SLES 15](11_efm4_sles15_ppcle) | ||
- [SLES 12](12_efm4_sles12_ppcle) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.