Merge pull request #3355 from EnterpriseDB/release/2022-11-17

Release: 2022-11-17

advocacy_docs/migrating/oracle/oracle_epas_comparison/app_devel_capabilities.mdx

@@ -35,7 +35,7 @@ Databases are a foundation of today’s data-driven enterprise, and applications
 
 ## EDB Postgres Advanced Server-compatible package support
 
-EDB focuses on the most popular functions in packages. For some packages, not all Oracle functions are supported. For specific details, refer to the [EDB Postgres Advanced Server](../../../epas/latest) documentation.
+EDB focuses on the most popular functions in packages. For some packages, not all Oracle functions are supported. For specific details, refer to the [EDB Postgres Advanced Server](../../../epas/latest/epas_compat_bip_guide/03_built-in_packages/) documentation. 
 
 | Package name   | Package description |
 |----------------|---------------------|

install_template/deploy.mjs

@@ -269,30 +269,6 @@ const moveDoc = async (product, platform, version) => {
     when({product: {name: "EDB Postgres Advanced Server", version: 11}, platform: {name: "Ubuntu 18.04"}}, 
       (ctx) => `epas/11/epas_inst_linux/installing_epas_using_edb_repository/${fmtArchPath(ctx)}/epas_ubuntu18_${fmtArchFilename(ctx)}.mdx`),
 
-
-    when({product: {name: "Failover Manager", version: 4}, platform: {name: "CentOS 7"}}, 
-      (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_centos7_${fmtArchFilename(ctx)}.mdx`),
-    when({product: {name: "Failover Manager", version: 4}, platform: {name: "AlmaLinux 8 or Rocky Linux 8"}}, 
-      (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_other_linux8_${fmtArchFilename(ctx)}.mdx`),
-    when({product: {name: "Failover Manager", version: 4}, platform: {name: "RHEL 7 or OL 7"}}, 
-      (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_rhel7_${fmtArchFilename(ctx)}.mdx`),
-    when({product: {name: "Failover Manager", version: 4}, platform: {name: "RHEL 8 or OL 8"}}, 
-      (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_rhel_8_${fmtArchFilename(ctx)}.mdx`),
-    when({product: {name: "Failover Manager", version: 4}, platform: {name: "RHEL 8"}}, 
-      (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_rhel8_${fmtArchFilename(ctx)}.mdx`),
-    when({product: {name: "Failover Manager", version: 4}, platform: {name: "SLES 12"}}, 
-      (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_sles12_${fmtArchFilename(ctx)}.mdx`),
-    when({product: {name: "Failover Manager", version: 4}, platform: {name: "SLES 15"}}, 
-      (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_sles15_${fmtArchFilename(ctx)}.mdx`),
-    when({product: {name: "Failover Manager", version: 4}, platform: {name: "Debian 11"}}, 
-      (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_deb11_${fmtArchFilename(ctx)}.mdx`),  
-    when({product: {name: "Failover Manager", version: 4}, platform: {name: "Debian 10"}}, 
-      (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_deb10_${fmtArchFilename(ctx)}.mdx`),      
-    when({product: {name: "Failover Manager", version: 4}, platform: {name: "Ubuntu 18.04"}}, 
-      (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_ubuntu18_${fmtArchFilename(ctx)}.mdx`),      
-    when({product: {name: "Failover Manager", version: 4}, platform: {name: "Ubuntu 20.04"}}, 
-      (ctx) => `efm/4/03_installing_efm/${fmtArchPath(ctx)}/efm4_ubuntu20_${fmtArchFilename(ctx)}.mdx`),      
-
     when({product: {name: "EDB JDBC Connector"}, platform: {name: "CentOS 7"}}, 
       (ctx) => `jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/${fmtArchPath(ctx)}/jdbc42_centos7_${fmtArchFilename(ctx)}.mdx`),
     when({product: {name: "EDB JDBC Connector"}, platform: {name: "AlmaLinux 8 or Rocky Linux 8"}}, 
@@ -316,29 +292,6 @@ const moveDoc = async (product, platform, version) => {
     when({product: {name: "EDB JDBC Connector"}, platform: {name: "Ubuntu 20.04"}}, 
       (ctx) => `jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/${fmtArchPath(ctx)}/jdbc42_ubuntu20_${fmtArchFilename(ctx)}.mdx`),
 
-    when({product: {name: "Migration Toolkit"}, platform: {name: "SLES 12"}}, 
-      (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_sles12_${fmtArchFilename(ctx)}.mdx`),
-    when({product: {name: "Migration Toolkit"}, platform: {name: "SLES 15"}}, 
-      (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_sles15_${fmtArchFilename(ctx)}.mdx`),
-    when({product: {name: "Migration Toolkit"}, platform: {name: "Debian 10"}}, 
-      (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_deb10_${fmtArchFilename(ctx)}.mdx`),
-    when({product: {name: "Migration Toolkit"}, platform: {name: "Debian 11"}}, 
-      (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_deb11_${fmtArchFilename(ctx)}.mdx`),
-    when({product: {name: "Migration Toolkit"}, platform: {name: "Ubuntu 18.04"}}, 
-      (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_ubuntu18_${fmtArchFilename(ctx)}.mdx`),
-    when({product: {name: "Migration Toolkit"}, platform: {name: "Ubuntu 20.04"}}, 
-      (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_ubuntu20_${fmtArchFilename(ctx)}.mdx`),
-    when({product: {name: "Migration Toolkit"}, platform: {name: "RHEL 8 or OL 8"}}, 
-      (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_rhel8_${fmtArchFilename(ctx)}.mdx`),
-    when({product: {name: "Migration Toolkit"}, platform: {name: "AlmaLinux 8 or Rocky Linux 8"}}, 
-      (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_other_linux8_${fmtArchFilename(ctx)}.mdx`),
-    when({product: {name: "Migration Toolkit"}, platform: {name: "RHEL 7 or OL 7"}}, 
-      (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_rhel7_${fmtArchFilename(ctx)}.mdx`),
-    when({product: {name: "Migration Toolkit"}, platform: {name: "CentOS 7"}}, 
-      (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_centos7_${fmtArchFilename(ctx)}.mdx`),
-    when({product: {name: "Migration Toolkit"}, platform: {name: "RHEL 8"}}, 
-      (ctx) => `migration_toolkit/55/05_installing_mtk/install_on_linux/${fmtArchPath(ctx)}/mtk55_rhel8_${fmtArchFilename(ctx)}.mdx`),
-
     when({product: {name: "EDB OCL Connector"}, platform: {name: "SLES 12"}}, 
       (ctx) => `ocl_connector/${ctx.product.version}/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/${fmtArchPath(ctx)}/ocl_connector14_sles12_${fmtArchFilename(ctx)}.mdx`),
     when({product: {name: "EDB OCL Connector"}, platform: {name: "SLES 15"}}, 

install_template/templates/products/failover-manager/base.njk

@@ -1,5 +1,17 @@
 {% extends "platformBase/" + platformBaseTemplate + '.njk' %}
 {% set packageName %}edb-efm<4x>{% endset %}
+{% import "platformBase/_deploymentConstants.njk" as deploy %}
+{% block frontmatter %}
+{# 
+  If you modify deployment path here, please first copy the old expression
+  and add it to the list under "redirects:" below - this ensures we don't 
+  break any existing links.  
+#}
+deployPath: efm/{{ product.version }}/installing/linux_{{platform.arch}}/efm_{{deploy.map_platform[platform.name]}}.mdx
+redirects:
+  - efm/{{ product.version }}/03_installing_efm/{{deploy.expand_arch[platform.arch]}}/efm_{{deploy.map_platform_old[platform.name]}}_{{platform.arch | replace(r/_?64/g, "")}}.mdx
+{% endblock frontmatter %}
+
 {% block prodprereq %}{% include "platformBase/_epasinstallsameserver.njk" %}
 {% endblock prodprereq %}
 {% block postinstall %}
@@ -17,4 +29,8 @@ After installing on each node of the cluster:
 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/).
-{% endblock postinstall %} 
+{% endblock postinstall %} 
+
+
+
+xxxxxx

install_template/templates/products/failover-manager/ubuntu-22.04.njk

@@ -1,2 +1,5 @@
 {% extends "products/failover-manager/base.njk" %}
-{% set platformBaseTemplate = "ubuntu-22.04" %}
+{% set platformBaseTemplate = "ubuntu-22.04" %}
+{% block frontmatter %}
+{# remove this block when Ubuntu 22 is released #}
+{% endblock frontmatter %}

install_template/templates/products/migration-toolkit/base.njk

@@ -1,5 +1,17 @@
 {% extends "platformBase/" + platformBaseTemplate + '.njk' %}
 {% set packageName %}edb-migrationtoolkit{% endset %}
+{% import "platformBase/_deploymentConstants.njk" as deploy %}
+{% block frontmatter %}
+{# 
+  If you modify deployment path here, please first copy the old expression
+  and add it to the list under "redirects:" below - this ensures we don't 
+  break any existing links.  
+#}
+deployPath: migration_toolkit/{{ product.version }}/installing/linux_{{platform.arch}}/mtk_{{deploy.map_platform[platform.name]}}.mdx
+redirects:
+  - migration_toolkit/{{ product.version }}/05_installing_mtk/install_on_linux/{{deploy.expand_arch[platform.arch]}}/mtk55_{{deploy.map_platform_old[platform.name]}}_{{platform.arch | replace(r/_?64/g, "")}}.mdx
+{% endblock frontmatter %}
+
 {% block prodprereq %}
 {% endblock prodprereq %}
 {% block postinstall %}

install_template/templates/products/migration-toolkit/ubuntu-22.04.njk

@@ -1,2 +1,5 @@
 {% extends "products/migration-toolkit/base.njk" %}
-{% set platformBaseTemplate = "ubuntu-22.04" %}
+{% set platformBaseTemplate = "ubuntu-22.04" %}
+{% block frontmatter %}
+{# remove this block when Ubuntu 22 is released #}
+{% endblock frontmatter %}

product_docs/docs/biganimal/release/overview/03a_region_support.mdx

@@ -61,13 +61,15 @@ When using AWS, you can create clusters in the following regions:
   - Asia Pacific Northeast 2 (Seoul)
   - Asia Pacific South 1 (Mumbai)
   - Asia Pacific Southeast 1 (Singapore)
-- Europe (EU)
-  - Europe 1 (Ireland)
-  - Europe 2 (London)
-- United States (US):
+- North America (NA):
+  - CA Central1 (Canada)
   - US East 1 (N. Virginia)
   - US East 2 (Ohio)
   - US West 2 (Oregon)
+- Europe (EU)
+  - Europe 1 (Ireland)
+  - Europe 2 (London)
+
 
 ## Next steps
 

product_docs/docs/biganimal/release/using_cluster/05_monitoring_and_logging/alerts.mdx

@@ -0,0 +1,50 @@
+---
+title: "Setting real-time alerts in Azure"
+
+---
+
+BigAnimal provides a wide range of metrics for your clusters, see [Metrics details](/biganimal/latest/using_cluster/05_monitoring_and_logging/metrics/). You can use a Log Analytics query to trigger a real-time alerts based on these metrics. 
+
+In this example we set up an alert that is triggered when one of your cluster groups goes down. Assume that your cluster group has an ID = *p-gjlmcos8n7* and is on a subscription called *development*.
+
+
+1. In the Azure portal, search for and select **Alerts**. On the Alerts page, you can see the metrics that BigAnimal collects from your environment.
+
+1. Select **+ Create** and select **Alert rule** to create new alert rule.
+
+1. Select **+ Select scope**. Under Select a resource:
+    1. Select your Azure subscription (**development**) in the Filter by subscription field. 
+
+    1. Select **Log Analytics workspaces** in the Filter by resource type field.
+    1. Select the Azure region of your cluster in the **Filter by location** field. 
+
+1. BigAnimal creates a Log Analytics workspace for each region in your Azure subscription. Select the Log Analytics workspace for your region and select **Done** (see right column for region).
+
+1. In the Condition tab, 
+   1. Select **Add condition** to set when the alert rule is triggered. 
+
+   1. Select **Custom log search** to monitor the Log analytics service.
+
+1. To trigger an alert when the database cluster is not detected enter the following query:
+
+    ```text
+    DpMetrics_CL
+    | where Message has "cnp_collector_up"
+    | extend m = todynamic(Message)
+    | where m.labels.role == "primary" and m.labels.postgresql == "p-gjlmcos8n7"
+    ```
+     The query programs the alert to check for the *cnp_collector_up* metric for the *p-gjlmcos8n7* database cluster. 
+
+1. After running the query, select **Continue editing alert**.
+
+1. Design the alert logic based on number of results. Under Alert logic:
+    1. Select the **Operator** as **Equals to**. 
+    1. Enter **0** in the Threshold value field.
+
+     The alert is triggered when the database cluster is unavailable and there are no metrics of *cnp_collector_up*. It can indicate that there is a monitoring problem or a critical error.
+
+1. In the Details tab, create the alert rule name.
+
+1. Select **Review + Create**.
+
+1. Select **Create**.

product_docs/docs/biganimal/release/using_cluster/05_monitoring_and_logging/index.mdx

@@ -1,5 +1,11 @@
 ---
 title: "Monitoring and logging"
+navigation:
+ - metrics
+ - monitoring_from_azure
+ - alerts
+ - monitoring_from_aws
+
 ---
 
 You can monitor your Postgres clusters by viewing the metrics and logs from your cloud provider. For more information about viewing metrics and logs from your cloud provider, see:

product_docs/docs/efm/4/index.mdx

@@ -7,14 +7,13 @@ redirects:
  - efm_user
 navigation:
   - efm_rel_notes
+  - supported_platforms
   - "#Planning"
   - architecture
   - efm_deploy_arch
-  - "#Installing"
-  - 01_prerequisites
-  - 03_installing_efm
-  - 14_install_details
-  - 12_upgrading_existing_cluster
+  - "#Installing and Upgrading"
+  - installing
+  - upgrading
   - "#Configuring"
   - 14_configuring_streaming_replication
   - 04_configuring_efm

product_docs/docs/efm/4/installing/index.mdx

@@ -0,0 +1,35 @@
+---
+title: "Installing Failover Manager on Linux"
+navTitle: "Installing"
+redirects:
+ - ../efm_user/03_installing_efm
+ - 13_initial_config
+ - /efm/4/03_installing_efm
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-failover-manager/user-guides/user-guide/4.0/installing_efm.html"
+  - "/edb-docs/d/edb-postgres-failover-manager/user-guides/user-guide/4.1/installing_efm.html"
+navigation:
+- prerequisites
+- linux_x86_64
+- linux_ppc64le
+- install_details
+---
+## [Linux x86-64 (amd64)](linux_x86_64)
+### Red Hat Enterprise Linux (RHEL) and derivatives
+- [RHEL 8](linux_x86_64/efm_rhel_8), [RHEL 7](linux_x86_64/efm_rhel_7)
+- [Oracle Linux (OL) 8](linux_x86_64/efm_rhel_8), [Oracle Linux (OL) 7](linux_x86_64/efm_rhel_7)
+- [Rocky Linux 8](linux_x86_64/efm_other_linux_8)
+- [AlmaLinux 8](linux_x86_64/efm_other_linux_8)
+- [CentOS 7](linux_x86_64/efm_centos_7)
+### SUSE Linux Enterprise (SLES) 
+- [SLES 15](linux_x86_64/efm_sles_15), [SLES 12](linux_x86_64/efm_sles_12)
+### Debian  and derivatives
+- [Ubuntu 20.04](linux_x86_64/efm_ubuntu_20), [Ubuntu 18.04](linux_x86_64/efm_ubuntu_18)
+- [Debian 11](linux_x86_64/efm_debian_11), [Debian 10](linux_x86_64/efm_debian_10)
+## [Linux on IBM Power (ppc64le)](linux_ppc64le)
+### Red Hat Enterprise Linux (RHEL) 
+- [RHEL 8](linux_ppc64le/efm_rhel_8)
+### SUSE Linux Enterprise (SLES) 
+- [SLES 15](linux_ppc64le/efm_sles_15), [SLES 12](linux_ppc64le/efm_sles_12)
+

product_docs/docs/efm/4/14_install_details.mdx → product_docs/docs/efm/4/installing/install_details.mdx

@@ -1,6 +1,7 @@
 ---
 title: "Installation details"
-
+redirects: 
+ - /efm/4/14_install_details
 ---
 
 

product_docs/docs/efm/4/03_installing_efm/ibm_power_ppc64le/efm4_rhel8_ppcle.mdx → product_docs/docs/efm/4/installing/linux_ppc64le/efm_rhel_8.mdx

@@ -1,10 +1,12 @@
 ---
 navTitle: RHEL 8
 title: Installing Failover Manager on RHEL 8 ppc64le
-
 # This topic is generated from templates. If you have feedback on it, instead of
 # editing the page and creating a pull request, please enter a GitHub issue and
 # the documentation team will update the templates accordingly.
+
+redirects:
+  - /efm/4/03_installing_efm/ibm_power_ppc64le/efm_rhel8_ppcle
 ---
 
 ## Prerequisites

product_docs/docs/efm/4/03_installing_efm/ibm_power_ppc64le/efm4_sles12_ppcle.mdx → product_docs/docs/efm/4/installing/linux_ppc64le/efm_sles_12.mdx

@@ -1,10 +1,12 @@
 ---
 navTitle: SLES 12
 title: Installing Failover Manager on SLES 12 ppc64le
-
 # This topic is generated from templates. If you have feedback on it, instead of
 # editing the page and creating a pull request, please enter a GitHub issue and
 # the documentation team will update the templates accordingly.
+
+redirects:
+  - /efm/4/03_installing_efm/ibm_power_ppc64le/efm_sles12_ppcle
 ---
 
 ## Prerequisites