[EFM] 5.0 changes (Friday release) (#6594)

* Changes for EFM 5.0

See story for status on which changes are in this PR already and which are still waiting:
https://enterprisedb.atlassian.net/browse/EFM-1730

This first commit makes general version bumps across the docs without any new content yet. A placeholder release notes file has been added; am pushing now to get some help with figuring out the release notes ordering and various "version 4" bits in the generated pages that I don't know how to find.

* Changes for EFM 5.0

See story for status on which changes are in this PR already and which are still waiting:
https://enterprisedb.atlassian.net/browse/EFM-1730

This first commit makes general version bumps across the docs without any new content yet. A placeholder release notes file has been added; am pushing now to get some help with figuring out the release notes ordering and various "version 4" bits in the generated pages that I don't know how to find.

* Fix build (no unescaped less-than symbols)

* ...missed one

* Updated 5.0 link in release notes index. Was still pointing at 4.10. Also removed the "5" from "...describes the latest version of Failover Manager" since the 4 or 5 isn't really important and I want to try to make it clear the docs cover the latest version no matter what it is, and changes are in the release notes.

* Fix a 4.x startup log reference that shouldn't have been changed to 5.x.

* Fixed all startup log references (hopefully).

* Fixed "xlog" text in json output.

* Changing the efm version directory from 4 to 5. No other changes in this commit.

* Fixed a broken link.

Helpful error messages and "npm run links:check" rule!

* We ran out of names following the existing convention, so I've bumped all the numbers way up.

This did involve fixing a link (checked with "npm run links:check") in a pdg page that referenced an efm release.

* Updated/removed some more startup log references and fixed the general logging page.

Added a big warning about not using TRACE level.

* Updated auto.resume.period information.

* Update text for detach.on.agent.failure property.

* Add new property backup.wal.

* Add new property check.num.sync.period.

This adds the property information, along with changing the wal_sender_timeout note to say it doesn't apply to efm versions 5 and up.

* Document "DOWN" cluster members.

This adds a note to the cluster-status and 'efm reset-members' pages about DOWN nodes.

* Adding the new efm create-standby command.

* Update to release notes.

Added the 5.0 release notes, fixed a stray apostrophe in the 4.8 notes, and updated the 5.0 release date.

* Remaining 4.x references and minor edits

* Added Addresses column to all release notes

* minor edits to 5.o rn

* Removed Ubuntu 20, updated config.yaml and added _redirects static path to catch /4/ traffic

* minor rn edits

* Added some text about detach.on.agent.failure property.

* rephrase detach_on_agent_failure

---------

Co-authored-by: Josh Heyer <[email protected]>
Co-authored-by: gvasquezvargas <[email protected]>

Author: 3 people

advocacy_docs/edb-postgres-ai/overview/latest-release-news/2024q3release.mdx

@@ -19,7 +19,7 @@ With Trusted Postgres Architect (TPA), we continuously seek to create useful def
 
 TPA Version 23.24 introduces clearer and more concise CLI output, helping operators verify that deployment was successful. Today’s release includes a new module that processes the raw Ansible output into a more concise form before streaming it to the operator, making it easier to spot important information.
 
-For clusters that include EDB [Postgres Enterprise Manager](https://www.enterprisedb.com/products/postgres-enterprise-manager) (PEM), operators can now specify additional options to pass to the “register-agent” command, as well as provide their own SSL certificates to be used by the PEM web server. This enhancement improves upon earlier processes requiring the use of custom hooks or manual configuration. For [Enterprise Failover Manager](https://www.enterprisedb.com/docs/efm/latest/) (EFM) clusters, TPA now supports the new configuration parameters introduced with [EFM 4.9](https://www.enterprisedb.com/docs/efm/latest/efm_rel_notes/01_efm_49_rel_notes/). In addition, the configuration files created by TPA now include all the formatting and comments provided in the default EFM configuration files, making it easier for any operator wanting to manually inspect these files. TPA now allows users to specify whether TPA uses host names or IP addresses in EFM configuration, where previously only IP addresses were supported.
+For clusters that include EDB [Postgres Enterprise Manager](https://www.enterprisedb.com/products/postgres-enterprise-manager) (PEM), operators can now specify additional options to pass to the “register-agent” command, as well as provide their own SSL certificates to be used by the PEM web server. This enhancement improves upon earlier processes requiring the use of custom hooks or manual configuration. For [Enterprise Failover Manager](https://www.enterprisedb.com/docs/efm/latest/) (EFM) clusters, TPA now supports the new configuration parameters introduced with [EFM 4.9](https://www.enterprisedb.com/docs/efm/latest/efm_rel_notes/31_efm_49_rel_notes/). In addition, the configuration files created by TPA now include all the formatting and comments provided in the default EFM configuration files, making it easier for any operator wanting to manually inspect these files. TPA now allows users to specify whether TPA uses host names or IP addresses in EFM configuration, where previously only IP addresses were supported.
 
 Find out more about [Trusted Postgres Architect](https://www.enterprisedb.com/docs/tpa/latest/). If you’re new to TPA, try out this [TPA tutorial to spin up your first cluster](https://www.enterprisedb.com/docs/tpa/latest/firstclusterdeployment/).
 

install_template/config.yaml

@@ -489,46 +489,43 @@ products:
     platforms:
       - name: AlmaLinux 8 or Rocky Linux 8
         arch: x86_64
-        supported versions: [4]
+        supported versions: [5]
       - name: AlmaLinux 9 or Rocky Linux 9
         arch: x86_64
-        supported versions: [4]
+        supported versions: [5]
       - name: RHEL 8 or OL 8
         arch: x86_64
-        supported versions: [4]
+        supported versions: [5]
       - name: RHEL 9 or OL 9
         arch: x86_64
-        supported versions: [4]
+        supported versions: [5]
       - name: RHEL 9
         arch: ppc64le
-        supported versions: [4]
+        supported versions: [5]
       - name: RHEL 9 or OL 9
         arch: arm64
-        supported versions: [4]  
+        supported versions: [5]  
       - name: RHEL 8
         arch: ppc64le
-        supported versions: [4]
+        supported versions: [5]
       - name: Debian 11
         arch: x86_64
-        supported versions: [4]
+        supported versions: [5]
       - name: Debian 12
         arch: x86_64
-        supported versions: [4]
+        supported versions: [5]
       - name: Debian 12
         arch: arm64
-        supported versions: [4]
-      - name: Ubuntu 20.04
-        arch: x86_64
-        supported versions: [4]
+        supported versions: [5]
       - name: Ubuntu 22.04
         arch: x86_64
-        supported versions: [4]
+        supported versions: [5]
       - name: SLES 15
         arch: x86_64
-        supported versions: [4]
+        supported versions: [5]
       - name: SLES 15
         arch: ppc64le
-        supported versions: [4]
+        supported versions: [5]
   - name: Hadoop Foreign Data Wrapper
     platforms:
       - name: AlmaLinux 8 or Rocky Linux 8

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

@@ -1,5 +1,5 @@
 {% extends "platformBase/" + platformBaseTemplate + '.njk' %}
-{% set packageName %}edb-efm<4x>{% endset %}
+{% set packageName %}edb-efm<5x>{% endset %}
 {% import "platformBase/_deploymentConstants.njk" as deploy %}
 {% block frontmatter %}
 {#
@@ -21,7 +21,7 @@ redirects:
 {{ super() }}
 {% endblock product_prerequisites %}
 {% block postinstall %}
-Where `<4x>` is the version of Failover Manager that you're installing. For example, if you're installing version 4.10, the package name is `edb-efm410`.
+Where `<5x>` is the version of Failover Manager that you're installing. For example, if you're installing version 5.0, the package name is `edb-efm50`.
 
 The installation process creates a user named efm that has privileges to invoke scripts that control the Failover Manager service for clusters owned by enterprisedb or postgres.