diff --git a/install_template/config.yaml b/install_template/config.yaml index c68078daea2..aa999e092fe 100644 --- a/install_template/config.yaml +++ b/install_template/config.yaml @@ -10,13 +10,13 @@ products: - name: AlmaLinux 8 or Rocky Linux 8 arch: x86_64 supported versions: [42.x.x] - - name: RHEL 7 + - name: RHEL 7 or OL 7 arch: x86_64 supported versions: [42.x.x] - - name: RHEL 8 + - name: RHEL 8 or OL 8 arch: x86_64 supported versions: [42.x.x] - - name: Ubuntu 20.04 or Debian 10 + - name: Debian 10 arch: x86_64 supported versions: [42.3.3.1] - name: Ubuntu 18.04 @@ -86,13 +86,10 @@ products: - name: AlmaLinux 8 or Rocky Linux 8 arch: x86_64 supported versions: [14.1.0.1] - - name: RHEL 7 - arch: x86_64 - supported versions: [14.1.0.1] - - name: RHEL 8 + - name: RHEL 7 or OL 7 arch: x86_64 supported versions: [14.1.0.1] - - name: Ubuntu 18.04 + - name: RHEL 8 or OL 8 arch: x86_64 supported versions: [14.1.0.1] - name: Debian 10 @@ -127,13 +124,10 @@ products: - name: AlmaLinux 8 or Rocky Linux 8 arch: x86_64 supported versions: [13.1.0.2] - - name: RHEL 7 - arch: x86_64 - supported versions: [13.1.0.2] - - name: RHEL 8 + - name: RHEL 7 or OL 7 arch: x86_64 supported versions: [13.1.0.2] - - name: Ubuntu 18.04 + - name: RHEL 8 or OL 8 arch: x86_64 supported versions: [13.1.0.2] - name: Debian 10 @@ -161,72 +155,66 @@ products: platforms: - name: CentOS 7 arch: x86_64 - supported versions: [1.14, 1.15, 1.16] + supported versions: [1.17] - name: RHEL 8 arch: ppc64le - supported versions: [1.14, 1.15, 1.16] + supported versions: [1.17] - name: AlmaLinux 8 or Rocky Linux 8 arch: x86_64 - supported versions: [1.14, 1.15, 1.16] - - name: RHEL 7 - arch: x86_64 - supported versions: [1.14, 1.15, 1.16] - - name: RHEL 8 + supported versions: [1.17] + - name: RHEL 7 or OL 7 arch: x86_64 - supported versions: [1.14, 1.15, 1.16] - - name: Ubuntu 18.04 + supported versions: [1.17] + - name: RHEL 8 or OL 8 arch: x86_64 - supported versions: [1.14, 1.15, 1.16] + supported versions: [1.17] - name: Debian 10 arch: x86_64 - supported versions: [1.14, 1.15, 1.16] + supported versions: [1.17] - name: Ubuntu 18.04 arch: x86_64 - supported versions: [1.14, 1.15, 1.16] + supported versions: [1.17] - name: Ubuntu 20.04 arch: x86_64 - supported versions: [1.14, 1.15, 1.16] + supported versions: [1.17] - name: SLES 12 arch: x86_64 - supported versions: [1.16] + supported versions: [1.17] - name: SLES 12 arch: ppc64le - supported versions: [1.16] + supported versions: [1.17] - name: SLES 15 arch: x86_64 - supported versions: [1.16] + supported versions: [1.17] - name: SLES 15 arch: ppc64le - supported versions: [1.16] + supported versions: [1.17] - name: EDB Pgpool-II platforms: - name: CentOS 7 arch: x86_64 - supported versions: [4.0, 4.1, 4.2, 4.3] + supported versions: [4.3] - name: RHEL 8 arch: ppc64le - supported versions: [4.0, 4.1, 4.2, 4.3] + supported versions: [4.3] - name: AlmaLinux 8 or Rocky Linux 8 arch: x86_64 - supported versions: [4.0, 4.1, 4.2, 4.3] - - name: RHEL 7 - arch: x86_64 - supported versions: [4.0, 4.1, 4.2, 4.3] - - name: RHEL 8 + supported versions: [4.3] + - name: RHEL 7 or OL 7 arch: x86_64 - supported versions: [4.0, 4.1, 4.2, 4.3] - - name: Ubuntu 18.04 + supported versions: [4.3] + - name: RHEL 8 or OL 8 arch: x86_64 - supported versions: [4.0, 4.1, 4.2, 4.3] + supported versions: [4.3] - name: Debian 10 arch: x86_64 - supported versions: [4.0, 4.1, 4.2, 4.3] + supported versions: [4.3] - name: Ubuntu 18.04 arch: x86_64 - supported versions: [4.0, 4.1, 4.2, 4.3] + supported versions: [4.3] - name: Ubuntu 20.04 arch: x86_64 - supported versions: [4.0, 4.1, 4.2, 4.3] + supported versions: [4.3] - name: SLES 12 arch: x86_64 supported versions: [4.3] @@ -243,31 +231,28 @@ products: platforms: - name: CentOS 7 arch: x86_64 - supported versions: [4.0, 4.1, 4.2, 4.3] + supported versions: [4.3] - name: RHEL 8 arch: ppc64le - supported versions: [4.0, 4.1, 4.2, 4.3] + supported versions: [4.3] - name: AlmaLinux 8 or Rocky Linux 8 arch: x86_64 - supported versions: [4.0, 4.1, 4.2, 4.3] - - name: RHEL 7 - arch: x86_64 - supported versions: [4.0, 4.1, 4.2, 4.3] - - name: RHEL 8 + supported versions: [4.3] + - name: RHEL 7 or OL 7 arch: x86_64 - supported versions: [4.0, 4.1, 4.2, 4.3] - - name: Ubuntu 18.04 + supported versions: [4.3] + - name: RHEL 8 or OL 8 arch: x86_64 - supported versions: [4.0, 4.1, 4.2, 4.3] + supported versions: [4.3] - name: Debian 10 arch: x86_64 - supported versions: [4.0, 4.1, 4.2, 4.3] + supported versions: [4.3] - name: Ubuntu 18.04 arch: x86_64 - supported versions: [4.0, 4.1, 4.2, 4.3] + supported versions: [4.3] - name: Ubuntu 20.04 arch: x86_64 - supported versions: [4.0, 4.1, 4.2, 4.3] + supported versions: [4.3] - name: SLES 12 arch: x86_64 supported versions: [4.3] @@ -408,9 +393,6 @@ products: - name: CentOS 7 arch: x86_64 supported versions: [2] - - name: CentOS 7 - arch: ppc64le - supported versions: [2] - name: AlmaLinux 8 or Rocky Linux 8 arch: x86_64 supported versions: [2] @@ -420,6 +402,9 @@ products: - name: RHEL 8 or OL 8 arch: x86_64 supported versions: [2] + - name: RHEL 8 + arch: ppc64le + supported versions: [2] - name: Ubuntu 18.04 arch: x86_64 supported versions: [2] @@ -449,9 +434,6 @@ products: - name: CentOS 7 arch: x86_64 supported versions: [5] - - name: CentOS 7 - arch: ppc64le - supported versions: [5] - name: AlmaLinux 8 or Rocky Linux 8 arch: x86_64 supported versions: [5] @@ -461,8 +443,8 @@ products: - name: RHEL 8 or OL 8 arch: x86_64 supported versions: [5] - - name: Debian 9 - arch: x86_64 + - name: RHEL 8 + arch: ppc64le supported versions: [5] - name: Debian 10 arch: x86_64 @@ -593,9 +575,6 @@ products: - name: Ubuntu 18.04 arch: x86_64 supported versions: [8] - - name: Ubuntu 18.04 - arch: x86_64 - supported versions: [8] - name: Ubuntu 20.04 arch: x86_64 supported versions: [8] @@ -615,16 +594,16 @@ products: platforms: - name: CentOS 7 arch: x86_64 - supported versions: [7, 8] + supported versions: [8] - name: AlmaLinux 8 or Rocky Linux 8 arch: x86_64 supported versions: [8] - name: RHEL 7 or OL 7 arch: x86_64 - supported versions: [7, 8] + supported versions: [8] - name: RHEL 8 or OL 8 arch: x86_64 - supported versions: [7, 8] + supported versions: [8] - name: RHEL 8 arch: ppc64le supported versions: [8] @@ -632,12 +611,9 @@ products: arch: x86_64 supported versions: [8] - name: Debian 9 - arch: x86_64 - supported versions: [7, 8] - - name: Ubuntu 20.04 arch: x86_64 supported versions: [8] - - name: Ubuntu 18.04 + - name: Ubuntu 20.04 arch: x86_64 supported versions: [8] - name: Ubuntu 18.04 @@ -648,7 +624,7 @@ products: supported versions: [8] - name: SLES 12 arch: x86_64 - supported versions: [7, 8] + supported versions: [8] - name: SLES 15 arch: x86_64 supported versions: [8] @@ -675,7 +651,10 @@ products: - name: Ubuntu 18.04 arch: x86_64 supported versions: [7] - - name: Ubuntu 20.04 or Debian 10 + - name: Ubuntu 20.04 + arch: x86_64 + supported versions: [7] + - name: Debian 10 arch: x86_64 supported versions: [7] - name: SLES 12 diff --git a/install_template/deploy.mjs b/install_template/deploy.mjs index 0d1174993b3..3e7ae1cc2ac 100644 --- a/install_template/deploy.mjs +++ b/install_template/deploy.mjs @@ -202,6 +202,16 @@ const moveDoc = async (product, platform, version) => { (ctx) => `hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/${fmtArchPath(ctx)}/hadoop_ubuntu18_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "Hadoop Foreign Data Wrapper", version: 2}, platform: {name: "Debian 10"}}, (ctx) => `hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/${fmtArchPath(ctx)}/hadoop_deb10_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Hadoop Foreign Data Wrapper", version: 2}, platform: {name: "CentOS 7"}}, + (ctx) => `hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/${fmtArchPath(ctx)}/hadoop_centos7_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Hadoop Foreign Data Wrapper", version: 2}, platform: {name: "AlmaLinux 8 or Rocky Linux 8"}}, + (ctx) => `hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/${fmtArchPath(ctx)}/hadoop_other_linux8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Hadoop Foreign Data Wrapper", version: 2}, platform: {name: "RHEL 7 or OL 7"}}, + (ctx) => `hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/${fmtArchPath(ctx)}/hadoop_rhel7_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Hadoop Foreign Data Wrapper", version: 2}, platform: {name: "RHEL 8 or OL 8"}}, + (ctx) => `hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/${fmtArchPath(ctx)}/hadoop_rhel8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Hadoop Foreign Data Wrapper", version: 2}, platform: {name: "RHEL 8"}}, + (ctx) => `hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/${fmtArchPath(ctx)}/hadoop_rhel8_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "EDB JDBC Connector"}, platform: {name: "SLES 12"}}, (ctx) => `jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/${fmtArchPath(ctx)}/jdbc42_sles12_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "EDB JDBC Connector"}, platform: {name: "SLES 15"}}, @@ -242,6 +252,16 @@ const moveDoc = async (product, platform, version) => { (ctx) => `mongo_data_adapter/5/04_installing_the_mongo_data_adapter/${fmtArchPath(ctx)}/mongo_ubuntu18_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "MongoDB Foreign Data Wrapper", version: 5}, platform: {name: "Debian 10"}}, (ctx) => `mongo_data_adapter/5/04_installing_the_mongo_data_adapter/${fmtArchPath(ctx)}/mongo_deb10_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "MongoDB Foreign Data Wrapper", version: 5}, platform: {name: "CentOS 7"}}, + (ctx) => `mongo_data_adapter/5/04_installing_the_mongo_data_adapter/${fmtArchPath(ctx)}/mongo_centos7_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "MongoDB Foreign Data Wrapper", version: 5}, platform: {name: "AlmaLinux 8 or Rocky Linux 8"}}, + (ctx) => `mongo_data_adapter/5/04_installing_the_mongo_data_adapter/${fmtArchPath(ctx)}/mongo_other_linux8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "MongoDB Foreign Data Wrapper", version: 5}, platform: {name: "RHEL 7 or OL 7"}}, + (ctx) => `mongo_data_adapter/5/04_installing_the_mongo_data_adapter/${fmtArchPath(ctx)}/mongo_rhel7_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "MongoDB Foreign Data Wrapper", version: 5}, platform: {name: "RHEL 8 or OL 8"}}, + (ctx) => `mongo_data_adapter/5/04_installing_the_mongo_data_adapter/${fmtArchPath(ctx)}/mongo_rhel8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "MongoDB Foreign Data Wrapper", version: 5}, platform: {name: "RHEL 8"}}, + (ctx) => `mongo_data_adapter/5/04_installing_the_mongo_data_adapter/${fmtArchPath(ctx)}/mongo_rhel8_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "MySQL Foreign Data Wrapper", version: 2}, platform: {name: "SLES 12"}}, (ctx) => `mysql_data_adapter/2/04_installing_the_mysql_data_adapter/${fmtArchPath(ctx)}/mysql_sles12_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "MySQL Foreign Data Wrapper", version: 2}, platform: {name: "SLES 15"}}, @@ -302,6 +322,16 @@ const moveDoc = async (product, platform, version) => { (ctx) => `pgpool/4.3/02_extensions/${fmtArchPath(ctx)}/pgpoolext_ubuntu18_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "EDB Pgpool-II Extensions", version: 4.3}, platform: {name: "Ubuntu 20.04"}}, (ctx) => `pgpool/4.3/02_extensions/${fmtArchPath(ctx)}/pgpoolext_ubuntu20_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Postgres Enterprise Manager server", version: 8}, platform: {name: "RHEL 8 or OL 8"}}, + (ctx) => `pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/${fmtArchPath(ctx)}/pem_server_rhel8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Postgres Enterprise Manager server", version: 8}, platform: {name: "RHEL 8"}}, + (ctx) => `pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/${fmtArchPath(ctx)}/pem_server_rhel8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Postgres Enterprise Manager server", version: 8}, platform: {name: "RHEL 7 or OL 7"}}, + (ctx) => `pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/${fmtArchPath(ctx)}/pem_server_rhel7_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Postgres Enterprise Manager server", version: 8}, platform: {name: "AlmaLinux 8 or Rocky Linux 8"}}, + (ctx) => `pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/${fmtArchPath(ctx)}/pem_server_other_linux8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Postgres Enterprise Manager server", version: 8}, platform: {name: "CentOS 7"}}, + (ctx) => `pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/${fmtArchPath(ctx)}/pem_server_centos7_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "Postgres Enterprise Manager server", version: 8}, platform: {name: "SLES 15"}}, (ctx) => `pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/${fmtArchPath(ctx)}/pem_server_sles15_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "Postgres Enterprise Manager server", version: 8}, platform: {name: "SLES 12"}}, @@ -312,6 +342,16 @@ const moveDoc = async (product, platform, version) => { (ctx) => `pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/${fmtArchPath(ctx)}/pem_server_ubuntu18_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "Postgres Enterprise Manager server", version: 8}, platform: {name: "Ubuntu 20.04"}}, (ctx) => `pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/${fmtArchPath(ctx)}/pem_server_ubuntu20_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Postgres Enterprise Manager agent", version: 8}, platform: {name: "RHEL 8 or OL 8"}}, + (ctx) => `pem/8/installing_pem_agent/installing_on_linux/${fmtArchPath(ctx)}/pem_agent_rhel8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Postgres Enterprise Manager agent", version: 8}, platform: {name: "RHEL 8"}}, + (ctx) => `pem/8/installing_pem_agent/installing_on_linux/${fmtArchPath(ctx)}/pem_agent_rhel8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Postgres Enterprise Manager agent", version: 8}, platform: {name: "RHEL 7 or OL 7"}}, + (ctx) => `pem/8/installing_pem_agent/installing_on_linux/${fmtArchPath(ctx)}/pem_agent_rhel7_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Postgres Enterprise Manager agent", version: 8}, platform: {name: "AlmaLinux 8 or Rocky Linux 8"}}, + (ctx) => `pem/8/installing_pem_agent/installing_on_linux/${fmtArchPath(ctx)}/pem_agent_other_linux8_${fmtArchFilename(ctx)}.mdx`), + when({product: {name: "Postgres Enterprise Manager agent", version: 8}, platform: {name: "CentOS 7"}}, + (ctx) => `pem/8/installing_pem_agent/installing_on_linux/${fmtArchPath(ctx)}/pem_agent_centos7_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "Postgres Enterprise Manager agent", version: 8}, platform: {name: "SLES 15"}}, (ctx) => `pem/8/installing_pem_agent/installing_on_linux/${fmtArchPath(ctx)}/pem_agent_sles15_${fmtArchFilename(ctx)}.mdx`), when({product: {name: "Postgres Enterprise Manager agent", version: 8}, platform: {name: "SLES 12"}}, diff --git a/install_template/templates/platformBase/redhat-family.njk b/install_template/templates/platformBase/redhat-family.njk index 3f55d84adba..b990b7fb2b9 100644 --- a/install_template/templates/platformBase/redhat-family.njk +++ b/install_template/templates/platformBase/redhat-family.njk @@ -7,14 +7,14 @@ # Replace '' and '' below with # your username and password for the EDB repository: sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - +{% block pemsetuprepo %} # Install the EPEL repository: {{ packageManager }} -y install {{ epelRepo }} {% if includePPC %} # Refresh the cache: dnf makecache {% endif %} -{% block redhatConfig %}{% endblock redhatConfig %} +{% block redhatConfig %}{% endblock redhatConfig %}{% endblock pemsetuprepo %} ``` {% endblock prerequisites %} {% block installCommand %} diff --git a/install_template/templates/products/edb-jdbc-connector/centos-7_ppc64le.njk b/install_template/templates/products/edb-jdbc-connector/centos-7_ppc64le.njk deleted file mode 100644 index 3fcb93ad6f3..00000000000 --- a/install_template/templates/products/edb-jdbc-connector/centos-7_ppc64le.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/edb-jdbc-connector/centos-7.njk" %} -{% set includePPC = true %} diff --git a/install_template/templates/products/edb-jdbc-connector/rhel-7-or-ol-7_ppc64le.njk b/install_template/templates/products/edb-jdbc-connector/rhel-7-or-ol-7_ppc64le.njk deleted file mode 100644 index f5b18889610..00000000000 --- a/install_template/templates/products/edb-jdbc-connector/rhel-7-or-ol-7_ppc64le.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/edb-jdbc-connector/rhel-7-or-ol-7.njk" %} -{% set includePPC = true %} \ No newline at end of file diff --git a/install_template/templates/products/edb-jdbc-connector/rhel-8_ppc64le.njk b/install_template/templates/products/edb-jdbc-connector/rhel-8_ppc64le.njk new file mode 100644 index 00000000000..b53670b906e --- /dev/null +++ b/install_template/templates/products/edb-jdbc-connector/rhel-8_ppc64le.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-jdbc-connector/rhel-8-or-ol-8.njk" %} +{% set includePPC = true %} \ No newline at end of file diff --git a/install_template/templates/products/edb-ocl-connector/centos-7_ppc64le.njk b/install_template/templates/products/edb-ocl-connector/centos-7_ppc64le.njk deleted file mode 100644 index 2c7baf131f6..00000000000 --- a/install_template/templates/products/edb-ocl-connector/centos-7_ppc64le.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/edb-ocl-connector/centos-7.njk" %} -{% set includePPC = true %} diff --git a/install_template/templates/products/edb-ocl-connector/rhel-7-or-ol-7_ppc64le.njk b/install_template/templates/products/edb-ocl-connector/rhel-7-or-ol-7_ppc64le.njk deleted file mode 100644 index f86f93620e3..00000000000 --- a/install_template/templates/products/edb-ocl-connector/rhel-7-or-ol-7_ppc64le.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/edb-ocl-connector/rhel-7-or-ol-7.njk" %} -{% set includePPC = true %} \ No newline at end of file diff --git a/install_template/templates/products/edb-ocl-connector/rhel-8_ppc64le.njk b/install_template/templates/products/edb-ocl-connector/rhel-8_ppc64le.njk new file mode 100644 index 00000000000..abcad167b00 --- /dev/null +++ b/install_template/templates/products/edb-ocl-connector/rhel-8_ppc64le.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-ocl-connector/rhel-8-or-ol-8.njk" %} +{% set includePPC = true %} \ No newline at end of file diff --git a/install_template/templates/products/edb-odbc-connector/centos-7_ppc64le.njk b/install_template/templates/products/edb-odbc-connector/centos-7_ppc64le.njk deleted file mode 100644 index 81c735ec9f7..00000000000 --- a/install_template/templates/products/edb-odbc-connector/centos-7_ppc64le.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/edb-odbc-connector/centos-7.njk" %} -{% set includePPC = true %} diff --git a/install_template/templates/products/edb-odbc-connector/rhel-7-or-ol-7_ppc64le.njk b/install_template/templates/products/edb-odbc-connector/rhel-7-or-ol-7_ppc64le.njk deleted file mode 100644 index b3ee612762e..00000000000 --- a/install_template/templates/products/edb-odbc-connector/rhel-7-or-ol-7_ppc64le.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/edb-odbc-connector/rhel-7-or-ol-7.njk" %} -{% set includePPC = true %} \ No newline at end of file diff --git a/install_template/templates/products/edb-odbc-connector/rhel-8_ppc64le.njk b/install_template/templates/products/edb-odbc-connector/rhel-8_ppc64le.njk new file mode 100644 index 00000000000..1e7393370e0 --- /dev/null +++ b/install_template/templates/products/edb-odbc-connector/rhel-8_ppc64le.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-odbc-connector/rhel-8-or-ol-8.njk" %} +{% set includePPC = true %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgbouncer/centos-7_ppc64le.njk b/install_template/templates/products/edb-pgbouncer/centos-7_ppc64le.njk deleted file mode 100644 index e6420f9bf37..00000000000 --- a/install_template/templates/products/edb-pgbouncer/centos-7_ppc64le.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/edb-pgbouncer/centos-7.njk" %} -{% set includePPC = true %} diff --git a/install_template/templates/products/edb-pgbouncer/rhel-7-or-ol-7_ppc64le.njk b/install_template/templates/products/edb-pgbouncer/rhel-7-or-ol-7_ppc64le.njk deleted file mode 100644 index 8764abd165c..00000000000 --- a/install_template/templates/products/edb-pgbouncer/rhel-7-or-ol-7_ppc64le.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/edb-pgbouncer/rhel-7-or-ol-7.njk" %} -{% set includePPC = true %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgbouncer/rhel-8_ppc64le.njk b/install_template/templates/products/edb-pgbouncer/rhel-8_ppc64le.njk new file mode 100644 index 00000000000..4c129698029 --- /dev/null +++ b/install_template/templates/products/edb-pgbouncer/rhel-8_ppc64le.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-pgbouncer/rhel-8-or-ol-8.njk" %} +{% set includePPC = true %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpool-ii-extensions/centos-7_ppc64le.njk b/install_template/templates/products/edb-pgpool-ii-extensions/centos-7_ppc64le.njk deleted file mode 100644 index ce9a0cf72d1..00000000000 --- a/install_template/templates/products/edb-pgpool-ii-extensions/centos-7_ppc64le.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/edb-pgpool-ii-extensions/centos-7.njk" %} -{% set includePPC = true %} diff --git a/install_template/templates/products/edb-pgpool-ii-extensions/rhel-7-or-ol-7_ppc64le.njk b/install_template/templates/products/edb-pgpool-ii-extensions/rhel-7-or-ol-7_ppc64le.njk deleted file mode 100644 index 1ddbea0fcd6..00000000000 --- a/install_template/templates/products/edb-pgpool-ii-extensions/rhel-7-or-ol-7_ppc64le.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/edb-pgpool-ii-extensions/rhel-7-or-ol-7.njk" %} -{% set includePPC = true %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpool-ii-extensions/rhel-8_ppc64le.njk b/install_template/templates/products/edb-pgpool-ii-extensions/rhel-8_ppc64le.njk new file mode 100644 index 00000000000..6ced8de39ae --- /dev/null +++ b/install_template/templates/products/edb-pgpool-ii-extensions/rhel-8_ppc64le.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-pgpool-ii-extensions/rhel-8-or-ol-8.njk" %} +{% set includePPC = true %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpool-ii/centos-7_ppc64le.njk b/install_template/templates/products/edb-pgpool-ii/centos-7_ppc64le.njk deleted file mode 100644 index 81a8da6e3b0..00000000000 --- a/install_template/templates/products/edb-pgpool-ii/centos-7_ppc64le.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/edb-pgpool-ii/centos-7.njk" %} -{% set includePPC = true %} diff --git a/install_template/templates/products/edb-pgpool-ii/debian-9.njk b/install_template/templates/products/edb-pgpool-ii/debian-9.njk deleted file mode 100644 index b10e66ac90d..00000000000 --- a/install_template/templates/products/edb-pgpool-ii/debian-9.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/edb-pgpool-ii/debian.njk" %} -{% set platformBaseTemplate = "debian-9" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpool-ii/rhel-7-or-ol-7_ppc64le.njk b/install_template/templates/products/edb-pgpool-ii/rhel-7-or-ol-7_ppc64le.njk deleted file mode 100644 index 1e23d7a8481..00000000000 --- a/install_template/templates/products/edb-pgpool-ii/rhel-7-or-ol-7_ppc64le.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/edb-pgpool-ii/rhel-7-or-ol-7.njk" %} -{% set includePPC = true %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpool-ii/rhel-8_ppc64le.njk b/install_template/templates/products/edb-pgpool-ii/rhel-8_ppc64le.njk new file mode 100644 index 00000000000..ec7192542f5 --- /dev/null +++ b/install_template/templates/products/edb-pgpool-ii/rhel-8_ppc64le.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-pgpool-ii/rhel-8-or-ol-8.njk" %} +{% set includePPC = true %} \ No newline at end of file diff --git a/install_template/templates/products/hadoop-foreign-data-wrapper/almalinux-8-or-rocky-linux-8.njk b/install_template/templates/products/hadoop-foreign-data-wrapper/almalinux-8-or-rocky-linux-8.njk index 7aa6155aa47..1f162e832fe 100644 --- a/install_template/templates/products/hadoop-foreign-data-wrapper/almalinux-8-or-rocky-linux-8.njk +++ b/install_template/templates/products/hadoop-foreign-data-wrapper/almalinux-8-or-rocky-linux-8.njk @@ -1,10 +1,2 @@ {% extends "products/hadoop-foreign-data-wrapper/base.njk" %} -{% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} -{% block prerequisites %} -{{ super() }} -1. Disable the built-in PostgreSQL module: - - ```sh - dnf -qy module disable postgresql - ``` -{% endblock prerequisites %} \ No newline at end of file +{% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} \ No newline at end of file diff --git a/install_template/templates/products/hadoop-foreign-data-wrapper/rhel-8-or-ol-8.njk b/install_template/templates/products/hadoop-foreign-data-wrapper/rhel-8-or-ol-8.njk index c19c16f990d..813444b77e2 100644 --- a/install_template/templates/products/hadoop-foreign-data-wrapper/rhel-8-or-ol-8.njk +++ b/install_template/templates/products/hadoop-foreign-data-wrapper/rhel-8-or-ol-8.njk @@ -1,2 +1,7 @@ {% extends "products/hadoop-foreign-data-wrapper/base.njk" %} -{% set platformBaseTemplate = "rhel-8-or-ol-8" %} \ No newline at end of file +{% set platformBaseTemplate = "rhel-8-or-ol-8" %} +{% block redhatConfig %}# Enable additional repositories to resolve dependencies: +dnf config-manager --set-enabled PowerTools + +# Disable the built-in PostgreSQL module: +dnf -qy module disable postgresql{% endblock redhatConfig %} \ No newline at end of file diff --git a/install_template/templates/products/failover-manager/rhel-8_ppc64le.njk b/install_template/templates/products/hadoop-foreign-data-wrapper/rhel-8_ppc64le.njk similarity index 55% rename from install_template/templates/products/failover-manager/rhel-8_ppc64le.njk rename to install_template/templates/products/hadoop-foreign-data-wrapper/rhel-8_ppc64le.njk index 14330fef043..62d4472fe13 100644 --- a/install_template/templates/products/failover-manager/rhel-8_ppc64le.njk +++ b/install_template/templates/products/hadoop-foreign-data-wrapper/rhel-8_ppc64le.njk @@ -1,3 +1,3 @@ -{% extends "products/failover-manager/base.njk" %} +{% extends "products/hadoop-foreign-data-wrapper/base.njk" %} {% set platformBaseTemplate = "rhel-8-or-ol-8" %} {% set includePPC = true %} diff --git a/install_template/templates/products/migration-toolkit/centos-7_ppc64le.njk b/install_template/templates/products/migration-toolkit/centos-7_ppc64le.njk deleted file mode 100644 index 0a0b88d3ff2..00000000000 --- a/install_template/templates/products/migration-toolkit/centos-7_ppc64le.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/migration-toolkit/centos-7.njk" %} -{% set includePPC = true %} diff --git a/install_template/templates/products/migration-toolkit/rhel-7_ppc64le.njk b/install_template/templates/products/migration-toolkit/rhel-7_ppc64le.njk deleted file mode 100644 index e6f0f2d98ab..00000000000 --- a/install_template/templates/products/migration-toolkit/rhel-7_ppc64le.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/migration-toolkit/rhel-7-or-ol-7.njk" %} -{% set includePPC = true %} \ No newline at end of file diff --git a/install_template/templates/products/migration-toolkit/rhel-8_ppc64le.njk b/install_template/templates/products/migration-toolkit/rhel-8_ppc64le.njk new file mode 100644 index 00000000000..eae29beb0aa --- /dev/null +++ b/install_template/templates/products/migration-toolkit/rhel-8_ppc64le.njk @@ -0,0 +1,2 @@ +{% extends "products/migration-toolkit/rhel-8-or-ol-8.njk" %} +{% set includePPC = true %} \ No newline at end of file diff --git a/install_template/templates/products/mongodb-foreign-data-wrapper/almalinux-8-or-rocky-linux-8.njk b/install_template/templates/products/mongodb-foreign-data-wrapper/almalinux-8-or-rocky-linux-8.njk index 8bcd927e031..879f608f1ee 100644 --- a/install_template/templates/products/mongodb-foreign-data-wrapper/almalinux-8-or-rocky-linux-8.njk +++ b/install_template/templates/products/mongodb-foreign-data-wrapper/almalinux-8-or-rocky-linux-8.njk @@ -1,10 +1,2 @@ {% extends "products/mongodb-foreign-data-wrapper/base.njk" %} -{% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} -{% block prerequisites %} -{{ super() }} -1. Disable the built-in PostgreSQL module: - - ```sh - dnf -qy module disable postgresql - ``` -{% endblock prerequisites %} \ No newline at end of file +{% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} \ No newline at end of file diff --git a/install_template/templates/products/mongodb-foreign-data-wrapper/rhel-8_ppc64le.njk b/install_template/templates/products/mongodb-foreign-data-wrapper/rhel-8_ppc64le.njk new file mode 100644 index 00000000000..323b995566d --- /dev/null +++ b/install_template/templates/products/mongodb-foreign-data-wrapper/rhel-8_ppc64le.njk @@ -0,0 +1,3 @@ +{% extends "products/mongodb-foreign-data-wrapper/base.njk" %} +{% set platformBaseTemplate = "rhel-8-or-ol-8" %} +{% set includePPC = true %} diff --git a/install_template/templates/products/postgres-enterprise-manager-agent/almalinux-8-or-rocky-linux-8.njk b/install_template/templates/products/postgres-enterprise-manager-agent/almalinux-8-or-rocky-linux-8.njk new file mode 100644 index 00000000000..371223e7df7 --- /dev/null +++ b/install_template/templates/products/postgres-enterprise-manager-agent/almalinux-8-or-rocky-linux-8.njk @@ -0,0 +1,2 @@ +{% extends "products/postgres-enterprise-manager-agent/base.njk" %} +{% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} \ No newline at end of file diff --git a/install_template/templates/products/postgres-enterprise-manager-agent/base.njk b/install_template/templates/products/postgres-enterprise-manager-agent/base.njk index c0b158e2e0b..18b387b4f00 100644 --- a/install_template/templates/products/postgres-enterprise-manager-agent/base.njk +++ b/install_template/templates/products/postgres-enterprise-manager-agent/base.njk @@ -1,5 +1,6 @@ {% extends "platformBase/" + platformBaseTemplate + '.njk' %} {% set packageName %}edb-pem-agent{% endset %} +{% block pemsetuprepo %}{% endblock pemsetuprepo %} {% block installCommand %} {{super()}} After installing PEM agent, you need to register the PEM agent. For detailed information see [Registering an agent](/pem/latest/registering_agent/). diff --git a/install_template/templates/products/postgres-enterprise-manager-agent/rhel-7_ppc64le.njk b/install_template/templates/products/postgres-enterprise-manager-agent/rhel-7_ppc64le.njk deleted file mode 100644 index 19ae7b153f5..00000000000 --- a/install_template/templates/products/postgres-enterprise-manager-agent/rhel-7_ppc64le.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/postgres-enterprise-manager-agent/rhel-7-or-ol-7.njk" %} -{% set includePPC = true %} \ No newline at end of file diff --git a/install_template/templates/products/postgres-enterprise-manager-server/almalinux-8-or-rocky-linux-8.njk b/install_template/templates/products/postgres-enterprise-manager-server/almalinux-8-or-rocky-linux-8.njk index 7976068b9ec..2def22fe2cb 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/almalinux-8-or-rocky-linux-8.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/almalinux-8-or-rocky-linux-8.njk @@ -1,10 +1,2 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} -{% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} -{% block prerequisites %} -{{ super() }} -1. Disable the built-in PostgreSQL module: - - ```sh - dnf -qy module disable postgresql - ``` -{% endblock prerequisites %} \ No newline at end of file +{% set platformBaseTemplate = "almalinux-8-or-rocky-linux-8" %} \ No newline at end of file diff --git a/install_template/templates/products/postgres-enterprise-manager-server/base.njk b/install_template/templates/products/postgres-enterprise-manager-server/base.njk index 39fba1b2858..2c5129d21c9 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/base.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/base.njk @@ -9,7 +9,7 @@ Before you begin the installation process: sudo su - ``` {% endblock pemprereq %} -{% block postinstallMenu %}- [Performing the initial configuration](#initial-configuration){% endblock postinstallMenu %} +{% block pemsetuprepo %}{% endblock pemsetuprepo %} {% block postinstall %} ## Initial configuration @@ -19,4 +19,7 @@ sudo su - ``` For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/installing_on_linux/configuring_the_pem_server_on_linux/). + +!!! Note +- The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. {% endblock postinstall %} \ No newline at end of file diff --git a/install_template/templates/products/postgres-enterprise-manager-server/centos-7.njk b/install_template/templates/products/postgres-enterprise-manager-server/centos-7.njk index 068544b4cc0..a4fd66e61c1 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/centos-7.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/centos-7.njk @@ -1,2 +1,8 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} -{% set platformBaseTemplate = "centos-7" %} \ No newline at end of file +{% set platformBaseTemplate = "centos-7" %} +{% block postinstall %} +{{ super() }}!!! Note: +- If you're doing a fresh installation of the PEM server on a CentOS 7.x host, the installer also installs edb-python3-mod_wsgi packages with the installation required by the operating system. + +- If you're upgrading the PEM server on a CentOS 7.x host, the mod_wsgi system package is replaced by the edb-python3-mod_wsgi package as required by the operating system. +{% endblock postinstall %} \ No newline at end of file diff --git a/install_template/templates/products/postgres-enterprise-manager-server/rhel-7-or-ol-7.njk b/install_template/templates/products/postgres-enterprise-manager-server/rhel-7-or-ol-7.njk index 13984173cc3..ee661bbae09 100644 --- a/install_template/templates/products/postgres-enterprise-manager-server/rhel-7-or-ol-7.njk +++ b/install_template/templates/products/postgres-enterprise-manager-server/rhel-7-or-ol-7.njk @@ -1,2 +1,8 @@ {% extends "products/postgres-enterprise-manager-server/base.njk" %} -{% set platformBaseTemplate = "rhel-7-or-ol-7" %} \ No newline at end of file +{% set platformBaseTemplate = "rhel-7-or-ol-7" %} +{% block postinstall %} +{{ super() }} +- If you're doing a fresh installation of the PEM server on a RHEL 7.x host, the installer also installs edb-python3-mod_wsgi packages with the installation required by the operating system. + +- If you're upgrading the PEM server on a RHEL 7.x host, the mod_wsgi system package is replaced by the edb-python3-mod_wsgi package as required by the operating system. +{% endblock postinstall %} \ No newline at end of file diff --git a/install_template/templates/products/postgres-enterprise-manager-server/rhel-7_ppc64le.njk b/install_template/templates/products/postgres-enterprise-manager-server/rhel-7_ppc64le.njk deleted file mode 100644 index 839301511ac..00000000000 --- a/install_template/templates/products/postgres-enterprise-manager-server/rhel-7_ppc64le.njk +++ /dev/null @@ -1,2 +0,0 @@ -{% extends "products/postgres-enterprise-manager-server/rhel-7-or-ol-7.njk" %} -{% set includePPC = true %} \ No newline at end of file diff --git a/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/01_preparing_azure/index.mdx b/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/01_preparing_azure/index.mdx index 412e7ea2cd9..6e6b39a9072 100644 --- a/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/01_preparing_azure/index.mdx +++ b/product_docs/docs/biganimal/release/getting_started/preparing_cloud_account/01_preparing_azure/index.mdx @@ -126,7 +126,7 @@ To check if an Azure resource provider is registered, use the following command. ```shell az provider show -n Microsoft.ContainerService - +__OUTPUT__ Namespace RegistrationPolicy RegistrationState -------------------------- -------------------- ------------------- Microsoft.ContainerService RegistrationRequired Registered @@ -139,7 +139,7 @@ You can check SKU restrictions for the VM size using the Azure Cloud Shell. For ```shell az vm list-skus -l eastus2 --zone --size Standard_E2s_v3 - +__OUTPUT__ ResourceType Locations Name Zones Restrictions --------------- ----------- --------------- ------- ------------ virtualMachines eastus2 Standard_E2s_v3 1,2,3 NotAvailableForSubscription, type: Zone, locations: eastus2, zones: 3,2 @@ -179,6 +179,7 @@ use the [register command](https://docs.microsoft.com/en-us/cli/azure/provider?v ```shell az provider register -n Microsoft.ContainerService +__OUTPUT__ Registering is still on-going. You can monitor using 'az provider show -n Microsoft.ContainerService ``` diff --git a/product_docs/docs/biganimal/release/reference/api.mdx b/product_docs/docs/biganimal/release/reference/api.mdx index 4aed4ba8eeb..381b961a96d 100644 --- a/product_docs/docs/biganimal/release/reference/api.mdx +++ b/product_docs/docs/biganimal/release/reference/api.mdx @@ -27,13 +27,13 @@ This call returns the information that either: - You need later if you're using `curl` to request the device code and tokens. - The `get-token` script uses to generate the tokens for you. -``` +```shell curl https://portal.biganimal.com/api/v2/auth/provider ``` The response returns the `clientId`, `freetrialClientId`, `issuerUri`, `scope`, and `audience`. For example: -``` +```json { "clientId": "5B79FAjzKF2Ig5dVFAOhc1acDSJYY2xh", "freetrialClientId": "m71bEVZrGsWiKtPqMI3hYCHCG3EYLPDk", @@ -66,7 +66,7 @@ The following example calls use these environment variables. This call gets a device code: -``` +```shell curl --request POST \ --url "$ISSUER_URL/oauth/device/code" \ --header "content-type: application/x-www-form-urlencoded" \ @@ -86,7 +86,7 @@ The response returns: For example: -``` +```json { "device_code": "KEOY2_5YjuVsRuIrrR-aq5gs", "user_code": "HHHJ-MMSZ", @@ -120,7 +120,7 @@ DEVICE_CODE=KEOY2_5YjuVsRuIrrR-aq5gs The `curl --request POST` call requests a token. For example: -``` +```shell curl --request POST \ --url "$ISSUER_URL/oauth/token" \ --header "content-type: application/x-www-form-urlencoded" \ @@ -139,7 +139,7 @@ If successful, the call returns: For example: -``` +```json { "access_token": "eyJhbGc.......1Qtkaw2fyho", "id_token": "eyJhbGci.......FBra7tA", @@ -152,7 +152,7 @@ For example: Store the access token and refresh token in environment variables for future use. For example: -``` +```ini RAW_ACCESS_TOKEN="eyJhbGc.......1Qtkaw2fyho" REFRESH_TOKEN="v2.MTvuZpu.......sbiionEhtTw" ``` @@ -179,7 +179,7 @@ If not successful, you receive one of the following errors: Use the raw token you obtained in the previous step [Request the raw token using `curl`](#request-the-raw-token-using-curl) to get the BigAnimal token: -``` +```shell curl -s --request POST \ --url "https://portal.biganimal.com/api/v2/auth/token" \ --header "content-type: application/json" \ @@ -192,7 +192,7 @@ If successful, the call returns: For example: -``` +```json { "token": "eyJhbGc.......0HFkr_19Vr7w" } @@ -201,7 +201,7 @@ For example: This token, as opposed to the raw-access token, is recognized by the BigAnimal API. Store this token in environment variables for future use. For example: -``` +```ini ACCESS_TOKEN="eyJhbGc.......0HFkr_19Vr7w" ``` @@ -213,7 +213,7 @@ Contact [Customer Support](../overview/support) if you have trouble obtaining a To call the BigAnimal API, your application must pass the retrieved access token as a bearer token in the Authorization header of your HTTP request. For example: -``` +```shell curl --request GET \ --url "$AUDIENCE/v2/postgres-types" \ --header "authorization: Bearer $ACCESS_TOKEN" \ @@ -222,7 +222,7 @@ curl --request GET \ Example response: -``` +```json { "pgTypesList": [ { @@ -253,7 +253,7 @@ The `get-token` script has an option to execute this step. See [Refresh the toke If you aren't using the `get-token` script to refresh your token, make a POST request to the `/oauth/token` endpoint in the Authentication API, using `grant_type=refresh_token`. For example: -``` +```shell curl --request POST \ --url "$ISSUER_URL/oauth/token" \ --header "content-type: application/x-www-form-urlencoded" \ @@ -268,7 +268,7 @@ The `client_id` is always the same one in the response when you [queried the aut The response of this API call includes the `access_token`. For example: -``` +```json { "access_token": "eyJ...MoQ", "expires_in": 86400, @@ -281,7 +281,7 @@ The response of this API call includes the `access_token`. For example: Store the access token and refresh token in environment variables for future use. For example: -``` +```ini RAW_ACCESS_TOKEN="eyJhbGc.......1Qtkaw2fyho" REFRESH_TOKEN="v2.MTvuZpu.......sbiionEhtTw" ``` @@ -322,8 +322,9 @@ Reference: https://www.enterprisedb.com/docs/biganimal/latest/reference/api/ To use the `get-token` script to get your tokens, use the script without the `--refresh` option. For example: -``` +```shell ./get-token.sh -o plain +__OUTPUT__ Please login to https://biganimal.us.auth0.com/activate?user_code=ZMNX-VVJT with your BigAnimal account @@ -343,8 +344,9 @@ xxxxxxxxxx To use the `get-token` script to refresh your token, use the script with the `--refresh ` option. For example: -``` +```shell ./get-token.sh -o json --refresh v2.MVZ9_xxxxxxxx_FRs +__OUTPUT__ { "access_token": "xxxxxxxxxx", "refresh_token": "xxxxxxxxxxxx", diff --git a/product_docs/docs/biganimal/release/reference/cli.mdx b/product_docs/docs/biganimal/release/reference/cli.mdx index 0d3e14456f5..9b580869a08 100644 --- a/product_docs/docs/biganimal/release/reference/cli.mdx +++ b/product_docs/docs/biganimal/release/reference/cli.mdx @@ -45,7 +45,11 @@ The CLI is available for Linux, MacOS, and Windows operating systems. Before using the CLI to manage BigAnimal, you need to authenticate as a valid BigAnimal user. Use the `create-credential` command to authenticate through the BigAnimal website and assign a refresh token and an access token to a local credential. For example: ```shell -$ biganimal create-credential --name ba-user1 --address portal.biganimal.com --port 443 +biganimal create-credential \ + --name ba-user1 \ + --address portal.biganimal.com \ + --port 443 +__OUTPUT__ Querying Authentication Endpoint for 'portal.biganimal.com First, copy your one-time code: CWWG-SMXC @@ -58,7 +62,8 @@ Credential "ba-user1" created! Refresh tokens expire after 30 days. To continue using the credential to access the CLI, use the `reset-credential` command to authenticate through the BigAnimal website and receive a new refresh token. ```shell -$ biganimal reset-credential ba-user1 +biganimal reset-credential ba-user1 +__OUTPUT__ Visit this URL to login: https://auth.biganimal.com/activate?user_code=****-**** or press [Enter] to continue in the web browser @@ -68,8 +73,9 @@ Credential "ba-user1" reset operation succeeded You can create multiple credentials for different BigAnimal accounts and then set one as context of your current management session. Use `show-credentials` to list all available credentials and use `config set context_credential` to set a default credential for the current context. For example: -``` -$ biganimal show-credentials +```shell +biganimal show-credentials +__OUTPUT__ ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓ ┃ Credentials ┃ ┣━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━┫ @@ -79,7 +85,10 @@ $ biganimal show-credentials ┃ ba-user2 ┃ portal.biganimal.com ┃ 443 ┃ ┃ ┗━━━━━━━━━━┻━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┻━━━━━━┻━━━━━━━━━━━━━━━━━━━━━━━━━┛ The credential ba-user1 has been set up -$ biganimal config set context_credential ba-user1 +``` + +```shell +biganimal config set context_credential ba-user1 ``` !!! Note @@ -91,7 +100,7 @@ The initial running of the CLI creates a hidden configuration folder in your use Don’t edit files in this directory directly. Instead, use the `config` subcommand to list and update the configuration settings of the CLI. Use the following command to get detailed usage and available configurations inforamtion: ```shell -$ biganimal config +biganimal config ``` ### Available configuration settings @@ -114,14 +123,14 @@ Use the `-h` or `--help` flags for more information on the CLI commands. You can You can enable command line auto completion for bash, fish, powershell, and zsh. To set up auto completion: ```shell -$ biganimal completion +biganimal completion ``` ### Interactive mode In interactive mode, the CLI prompts you for any missing mandatory flags and lists any available options for your current context. To enable interactive mode: ```shell -$ biganimal config set interactive_mode on +biganimal config set interactive_mode on ``` ## Sample use cases @@ -136,7 +145,8 @@ You can turn off prompting using the `biganimal config set interactive_mode off` !!! ```shell -$ biganimal create-cluster +biganimal create-cluster +__OUTPUT__ Cluster architecture: High Availability Number of standby replicas: 2 Replicas Provider: Azure @@ -166,8 +176,9 @@ Volume properties? You are prompted to confirm you want to create the cluster. After the cluster creation process is completed, it generates a cluster ID. -``` -$ biganimal create-cluster +```shell +biganimal create-cluster +__OUTPUT__ ........ Are you sure you want to Create Cluster ? [y|n]: y Create Cluster operation is started @@ -177,8 +188,9 @@ To check current state, run: biganimal show-clusters --id p-gxhkfww1fe Check your cluster was created successfully using the `show-clusters` command shown in the return message: -``` -$ biganimal show-clusters --id p-gxhkfww1fe +```shell +biganimal show-clusters --id p-gxhkfww1fe +__OUTPUT__ ┌─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐ │ Clusters │ ├──────────────┬──────────────────────┬────────────────────┬──────────┬──────────────┬──────────────┬──────────────────────────────┬─────────┤ @@ -223,7 +235,7 @@ Here is a sample configuration file in YAML format with Azure specified as the p !!! Note For backward compatibility, `allowIpRangeMap` and `pgConfigMap` properties also support embedded JSON format. - ``` + ```json allowIpRangeMap: [["9.9.9.9/28", "Allow traffic from App A"],["10.10.10.10/27", "Allow traffic from App B"]] pgConfigMap: [["application_name","test_app"],["array_nulls","true"]] ``` @@ -239,6 +251,7 @@ To query an enumeration of valid values for above BigAnimal and cloud service pr ```shell biganimal show-cluster-architecture +__OUTPUT__ ┌──────────────────────────────────────────────┐ │ Architecture │ ├────────┬───────────────────────────┬─────────┤ @@ -263,8 +276,12 @@ You can turn off the confirmation step with the `biganimal disable-confirm` comm To use your BigAnimal cluster, you first need to get your cluster's connection information. To get your cluster's connection information, use the `show-cluster-connection` command: -``` -$ biganimal show-cluster-connection --name my-biganimal-cluster --provider azure --region eastus +```shell +biganimal show-cluster-connection \ + --name my-biganimal-cluster \ + --provider azure \ + --region eastus +__OUTPUT__ ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓ ┃ Connection String ┃ ┣━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┫ @@ -276,7 +293,11 @@ $ biganimal show-cluster-connection --name my-biganimal-cluster --provider azure You can query the complete connection information with other output formats, like JSON or YAML. For example: ```shell -biganimal show-cluster-connection --name my-biganimal-cluster --provider azure --region eastus --ouput json +biganimal show-cluster-connection \ + --name my-biganimal-cluster \ + --provider azure \ + --region eastus \ + --ouput json ``` !!! @@ -296,13 +317,19 @@ After the cluster is created, you can update attributes of the cluster including For example, to set the public allowed IP range list, use the `--cidr-blocks` flag: ```shell -$ biganimal update-cluster --name my-biganimal-cluster --provider azure --region eastus --cidr-blocks --cidr-blocks "9.9.9.9/28=Traffic from App A" +biganimal update-cluster --name my-biganimal-cluster --provider azure \ + --region eastus \ + --cidr-blocks "9.9.9.9/28=Traffic from App A" ``` To check whether the setting took effect, use the `show-clusters` command and view the detailed cluster information output in JSON format. For example, ```shell -$ biganimal show-clusters --name my-biganimal-cluster --provider azure --region eastus --output json | jq '.[0].allowIpRangeMap' +biganimal show-clusters --name my-biganimal-cluster --provider azure \ + --region eastus \ + --output json \ +| jq '.[0].allowIpRangeMap' +__OUTPUT__ [ [ "9.9.9.9/28", @@ -316,7 +343,9 @@ $ biganimal show-clusters --name my-biganimal-cluster --provider azure --region To update the Postgres configuration of a BigAnimal cluster directly from the CLI: ```shell -biganimal update-cluster --id p-gxhkfww1fe --pg-config "application_name=ba_test_app,array_nulls=false" +biganimal update-cluster --id p-gxhkfww1fe \ + --pg-config "application_name=ba_test_app,array_nulls=false" +__OUTPUT__ Update Cluster operation is started Cluster ID is "p-gxhkfww1fe" ``` @@ -331,7 +360,20 @@ You can update "Cluster Architecture" with the `--cluster-architecture` flag. Th Biganimal continuously backs up your PostgrSQL clusters. Using CLI you can restore a cluster from its backup to any point in time as long as the backups are retained in the backup storage. The restored cluster can be a in another region and with different configurations, you can specify new configurations in restore command. For example: ```shell -biganimal restore-cluster --name "my-biganimal-cluster" --provider "azure" --region "eastus" --password "mypassword@123" --new-name "my-biganimal-cluster-restored" --new-region="eastus2" --cluster-architecture "single" --instance-type "azure:Standard_E2s_v3" --volume-type "azurepremiumstorage" --volume-property "P1" --networking "public" --cidr-blocks="10.10.10.10/27=Traffic from App B" --restore-point "2022-01-26T15:04:05+0800" +biganimal restore-cluster \ + --name "my-biganimal-cluster" \ + --provider "azure" \ + --region "eastus" \ + --password "mypassword@123" \ + --new-name "my-biganimal-cluster-restored" \ + --new-region="eastus2" \ + --cluster-architecture "single" \ + --instance-type "azure:Standard_E2s_v3" \ + --volume-type "azurepremiumstorage" \ + --volume-property "P1" \ + --networking "public" \ + --cidr-blocks="10.10.10.10/27=Traffic from App B" \ + --restore-point "2022-01-26T15:04:05+0800" ``` The password for the restored cluster is a mandatory. The other parameters, if not specified, inherit the source database's settings. In interactive mode, the source database's settings appear as the default input, or appear as the first option in a selection list. @@ -347,7 +389,10 @@ You can restore a cluster in a "Single" cluster to a "High Availability" cluster To delete a cluster you no longer need, use the `delete-cluster` command. For example: ```shell -$ biganimal delete-cluster --name my-biganimal-cluster --provider azure --region eastus +biganimal delete-cluster \ + --name my-biganimal-cluster \ + --provider azure \ + --region eastus ``` You can list all deleted clusters with the `show-deleted-clusters` command and restore them from their history backups as needed. diff --git a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/01_private_endpoint.mdx b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/01_private_endpoint.mdx index 857894ba118..f0b6884301c 100644 --- a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/01_private_endpoint.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/01_private_endpoint.mdx @@ -30,7 +30,8 @@ To walk through an example in your own environment, you need: - The IP address of your cluster. You can find the IP address of your cluster using the following command: ```shell - $ dig +short p-c4j0jfcmp3af2ieok5eg.brcxzr08qr7rbei1.biganimal.io + dig +short p-c4j0jfcmp3af2ieok5eg.brcxzr08qr7rbei1.biganimal.io + __OUTPUT__ 10.240.1.218 ``` - A Postgresql client, such as [psql](https://www.postgresql.org/download/), installed on your client VM. @@ -42,7 +43,7 @@ To walk through an example in your own environment, you need: 1. Get the resource group details from the Azure CLI or the Azure portal and note the resource group name. For example, if the cluster's virtual network is `vnet-japaneast`, use the following command: ```shell - $ az network vnet list --query "[?name==\`vnet-japaneast\`].resourceGroup" -o json + az network vnet list --query "[?name==\`vnet-japaneast\`].resourceGroup" -o json ``` @@ -67,7 +68,8 @@ To walk through an example in your own environment, you need: You can get the IP address of your cluster with the following command: ```shell - $ dig +short p-c4j0jfcmp3af2ieok5eg.brcxzr08qr7rbei1.biganimal.io + dig +short p-c4j0jfcmp3af2ieok5eg.brcxzr08qr7rbei1.biganimal.io + __OUTPUT__ 10.240.1.218 ``` @@ -84,8 +86,9 @@ To walk through an example in your own environment, you need: 5. After the private link service is created, note its alias. The alias is the unique ID for your private service, which you can share with the service consumers. Obtain the alias either from the Azure portal or by using the following CLI command: ```shell - $ az network private-link-service list --query "[?name=='p-c4j0jfcmp3af2ieok5eg-service-private-link'].alias" -o tsv - p-c4j0jfcmp3af2ieok5eg-service-private-link.48f26b42-45dc-4e80-8e3d-307d58d7d274.japaneast.azure.privatelinkservice + az network private-link-service list --query "[?name=='p-c4j0jfcmp3af2ieok5eg-service-private-link'].alias" -o tsv + __OUTPUT__ + p-c4j0jfcmp3af2ieok5eg-service-private-link.48f26b42-45dc-4e80-8e3d-307d58d7d274.japaneast.azure.privatelinkservice ``` 6. Select **Review + Create**. @@ -135,16 +138,17 @@ To walk through an example in your own environment, you need: 11. You have successfully built a tunnel between your client VM's virtual network and the cluster. You can now access the cluster from the private endpoint in your client VM. The private endpoint's private IP address is associated with an independent virtual network NIC. Get the private endpoint's private IP address using the following commands: ```shell - $ NICID=$(az network private-endpoint show -n vnet-client-private-pg-service -g rg-client --query "networkInterfaces[0].id" -o tsv) - $ az network nic show -n ${NICID##*/} -g rg-client --query "ipConfigurations[0].privateIpAddress" -o tsv - 100.64.111.5 + NICID=$(az network private-endpoint show -n vnet-client-private-pg-service -g rg-client --query "networkInterfaces[0].id" -o tsv) + az network nic show -n ${NICID##*/} -g rg-client --query "ipConfigurations[0].privateIpAddress" -o tsv + __OUTPUT__ + 100.64.111.5 ``` 12. From the client VM `vm-client`, access the cluster by using the private IP address: ```shell - $ psql -h 100.64.111.5 -U edb_admin - + psql -h 100.64.111.5 -U edb_admin + __OUTPUT__ Password for user edb_admin : psql (13.4 (Ubuntu 13.4-1.pgdg20.04+1), server 13.4.8 (Debian 13.4.8-1+deb10)) @@ -186,10 +190,10 @@ With a Private DNS Zone, you configure a DNS entry for your cluster's public hos 7. You can now access your cluster with this private domain name. ```shell - $ dig +short p-c4iabjleig40jngmac40.brcxzr08qr7rbei1.biganimal.io + dig +short p-c4iabjleig40jngmac40.brcxzr08qr7rbei1.biganimal.io + psql -h p-c4iabjleig40jngmac40.brcxzr08qr7rbei1.biganimal.io -U edb_admin + __OUTPUT__ 10.240.1.123 - - $ psql -h p-c4iabjleig40jngmac40.brcxzr08qr7rbei1.biganimal.io -U edb_admin Password for user edb_admin: psql (13.4 (Ubuntu 13.4-1.pgdg28.84+1), server 13.4.8 (Debian 13.4.8-1+deb10)) @@ -204,5 +208,5 @@ With a Private DNS Zone, you configure a DNS entry for your cluster's public hos You might need to flush your local DNS cache to resolve your domain name to the new private IP address after adding the private endpoint. For example, on Ubuntu, run the following command: ```shell - $ sudo systemd-resolve --flush-caches + sudo systemd-resolve --flush-caches ``` diff --git a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/02_virtual_network_peering.mdx b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/02_virtual_network_peering.mdx index 44c82b1c981..01917c863fa 100644 --- a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/02_virtual_network_peering.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/02_virtual_network_peering.mdx @@ -32,7 +32,8 @@ To walk through an example in your own environment, you need: - The IP address of your cluster. You can find the IP address of your cluster using the following command: ```shell - $ dig +short p-c4j0jfcmp3af2ieok5eg.brcxzr08qr7rbei1.biganimal.io + dig +short p-c4j0jfcmp3af2ieok5eg.brcxzr08qr7rbei1.biganimal.io + __OUTPUT__ 10.240.1.218 ``` - A Postgresql client, such as [psql](https://www.postgresql.org/download/), installed on your client VM. @@ -63,10 +64,10 @@ You need to add two peering links, one from the client VM's VNet `vnet-client` a Access the cluster with its domain name from your cluster's connection string. It's accessible from `vnet-client` after peering. ```shell -$ dig +short p-c4j0jfcmp3af2ieok5eg.brcxzr08qr7rbei1.biganimal.io +dig +short p-c4j0jfcmp3af2ieok5eg.brcxzr08qr7rbei1.biganimal.io +psql -h p-c4j0jfcmp3af2ieok5eg.brcxzr08qr7rbei1.biganimal.io -U edb_admin +__OUTPUT__ 10.240.1.123 - -$ psql -h p-c4j0jfcmp3af2ieok5eg.brcxzr08qr7rbei1.biganimal.io -U edb_admin Password for user edb_admin: psql (13.4 (Ubuntu 13.4-1.pgdg28.84+1), server 13.4.8 (Debian 13.4.8-1+deb10)) diff --git a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/03_vnet_vnet.mdx b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/03_vnet_vnet.mdx index 72724598765..557d1bfdf3d 100644 --- a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/03_vnet_vnet.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/03_vnet_vnet.mdx @@ -34,7 +34,8 @@ To walk through an example in your own environment, you need: - The IP address of your cluster. You can find the IP address of your cluster using the following command: ```shell - $ dig +short p-c4j0jfcmp3af2ieok5eg.brcxzr08qr7rbei1.biganimal.io + dig +short p-c4j0jfcmp3af2ieok5eg.brcxzr08qr7rbei1.biganimal.io + __OUTPUT__ 10.240.1.218 ``` - A Postgresql client, such as [psql](https://www.postgresql.org/download/), installed on your client VM. @@ -68,21 +69,29 @@ Use the Azure CLI (or [PowerShell](https://docs.microsoft.com/en-us/azure/vpn-ga **From the BigAnimal subscription**: ```shell - $ az network vnet-gateway show -n vpng-biganimal -g brCxzr08qr7RBEi1-rg-japaneast-management --query "[id]" -otsv + az network vnet-gateway show -n vpng-biganimal -g brCxzr08qr7RBEi1-rg-japaneast-management --query "[id]" -otsv + __OUTPUT__ subscriptions/.../vpng-biganimal ``` **From the client VM's subscription**: ```shell - $ az network vnet-gateway show -n vpng-client -g rg-client --query "[id]" -o tsv + az network vnet-gateway show -n vpng-client -g rg-client --query "[id]" -o tsv + __OUTPUT__ /subscriptions/.../vpng-client ``` 2. From the BigAnimal subscription, create a connection from `vpng-biganimal` to `vpng-client`. ```shell - $ az network vpn-connection create -n vpnc-biganimal-client -g brCxzr08qr7RBEi1-rg-japaneast-management --vnet-gateway1 /subscriptions/.../vpng-biganimal -l japaneast --shared-key "a_very_long_and_complex_psk" \--vnet-gateway2 /subscriptions/.../vpng-client + az network vpn-connection create \ + -n vpnc-biganimal-client \ + -g brCxzr08qr7RBEi1-rg-japaneast-management \ + --vnet-gateway1 /subscriptions/.../vpng-biganimal \ + -l japaneast + --shared-key "a_very_long_and_complex_psk" \ + --vnet-gateway2 /subscriptions/.../vpng-client ``` @@ -91,7 +100,13 @@ Use the Azure CLI (or [PowerShell](https://docs.microsoft.com/en-us/azure/vpn-ga 3. From the client VM's subscription, create another connection from `vpng-client` to `vpng-ebdcloud`. ```shell - $ az network vpn-connection create -n vpnc-client-biganimal -g rg-client --vnet-gateway1 /subscriptions/.../vpng-client -l japaneast --shared-key "a_very_long_and_complex_psk!" --vnet-gateway2 /subscriptions/.../vpng-biganimal + az network vpn-connection create \ + -n vpnc-client-biganimal \ + -g rg-client \ + --vnet-gateway1 /subscriptions/.../vpng-client \ + -l japaneast \ + --shared-key "a_very_long_and_complex_psk!" \ + --vnet-gateway2 /subscriptions/.../vpng-biganimal ``` #### Step 4: Verify the connection @@ -99,17 +114,19 @@ Use the Azure CLI (or [PowerShell](https://docs.microsoft.com/en-us/azure/vpn-ga 1. After a few minutes, verify the gateway connection status from either virtual networks with the following command: ```shell - $ az network vpn-connection show --name vpnc-client-biganimal -g rg-client --query "[connectionStatus]" -o tsv + az network vpn-connection show --name vpnc-client-biganimal -g rg-client \ + --query "[connectionStatus]" -o tsv + __OUTPUT__ Connected ``` 2. Verify the connectivity to the cluster: ```shell - $ dig +short p-c4j0jfcmp3af2ieok5eg.brcxzr08qr7rbei1.biganimal.io + dig +short p-c4j0jfcmp3af2ieok5eg.brcxzr08qr7rbei1.biganimal.io + psql -h p-c4j0jfcmp3af2ieok5eg.brcxzr08qr7rbei1.biganimal.io -U edb_admin + __OUTPUT__ 10.240.1.123 - - $ psql -h p-c4j0jfcmp3af2ieok5eg.brcxzr08qr7rbei1.biganimal.io -U edb_admin Password for user edb_admin: psql (13.4 (Ubuntu 13.4-1.pgdg28.84+1), server 13.4.8 (Debian 13.4.8-1+deb10)) diff --git a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/02_connecting_from_aws/01_vpc_endpoint.mdx b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/02_connecting_from_aws/01_vpc_endpoint.mdx index 59349a30df4..46470b89dbf 100644 --- a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/02_connecting_from_aws/01_vpc_endpoint.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/02_connecting_from_aws/01_vpc_endpoint.mdx @@ -99,7 +99,8 @@ Now that your endpoint service is created, you can connect it to the cluster VPC In your application's AWS account, select **VPC** and then select **Endpoints**. Select the endpoint you created previously and use the DNS name provided in the details section to access your cluster. ```shell - $ psql -h vpce-XXXXXXXXXXXXXXXXXXXX.eu-west-1.vpce.amazonaws.com -U edb_admin + psql -h vpce-XXXXXXXXXXXXXXXXXXXX.eu-west-1.vpce.amazonaws.com -U edb_admin + __OUTPUT__ Password for user edb_admin: psql (13.4 (Ubuntu 13.4-1.pgdg28.84+1), server 13.4.8 (Debian 13.4.8-1+deb10)) diff --git a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/02_connecting_from_aws/02_vpc_peering.mdx b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/02_connecting_from_aws/02_vpc_peering.mdx index bef71dcec38..79ab68a8311 100644 --- a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/02_connecting_from_aws/02_vpc_peering.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/02_connecting_from_aws/02_vpc_peering.mdx @@ -91,16 +91,17 @@ You can create a VPC peering connection with a VPC in the same region or a diffe 1. Access the cluster with its domain name from your cluster's connection string. It's accessible from `vpc-client` after peering. -```shell - $ psql -h vpce-XXXXXXXXXXXXXXXXXXXX.eu-west-1.vpce.amazonaws.com -U edb_admin - Password for user edb_admin: + ```shell + psql -h vpce-XXXXXXXXXXXXXXXXXXXX.eu-west-1.vpce.amazonaws.com -U edb_admin + __OUTPUT__ + Password for user edb_admin: - psql (13.4 (Ubuntu 13.4-1.pgdg28.84+1), server 13.4.8 (Debian 13.4.8-1+deb10)) - WARNING : psql major version 13, server major version 13. Some psql features might not work. - SSL connection (protocol : TLSV1.3cipherTLS_AES_256_GCM_SHA384, bits : 256, compression : off) Type "help" for help. + psql (13.4 (Ubuntu 13.4-1.pgdg28.84+1), server 13.4.8 (Debian 13.4.8-1+deb10)) + WARNING : psql major version 13, server major version 13. Some psql features might not work. + SSL connection (protocol : TLSV1.3cipherTLS_AES_256_GCM_SHA384, bits : 256, compression : off) Type "help" for help. - edb_admin=> -``` + edb_admin=> + ``` ### Create a VPC peering connection with a VPC in a different region @@ -132,13 +133,14 @@ You can create a VPC peering connection with a VPC in the same region or a diffe 1. Access the cluster with its domain name from your cluster's connection string. It's accessible from `vpc-client` after peering. -```shell - $ psql -h vpce-XXXXXXXXXXXXXXXXXXXX.eu-west-1.vpce.amazonaws.com -U edb_admin - Password for user edb_admin: + ```shell + psql -h vpce-XXXXXXXXXXXXXXXXXXXX.eu-west-1.vpce.amazonaws.com -U edb_admin + __OUTPUT__ + Password for user edb_admin: - psql (13.4 (Ubuntu 13.4-1.pgdg28.84+1), server 13.4.8 (Debian 13.4.8-1+deb10)) - WARNING : psql major version 13, server major version 13. Some psql features might not work. - SSL connection (protocol : TLSV1.3cipherTLS_AES_256_GCM_SHA384, bits : 256, compression : off) Type "help" for help. + psql (13.4 (Ubuntu 13.4-1.pgdg28.84+1), server 13.4.8 (Debian 13.4.8-1+deb10)) + WARNING : psql major version 13, server major version 13. Some psql features might not work. + SSL connection (protocol : TLSV1.3cipherTLS_AES_256_GCM_SHA384, bits : 256, compression : off) Type "help" for help. - edb_admin=> -``` + edb_admin=> + ``` diff --git a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/ibm_power_ppc64le/hadoop_rhel8_ppcle.mdx b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/ibm_power_ppc64le/hadoop_rhel8_ppcle.mdx index c42ee9ae186..0f6af2cd5bb 100644 --- a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/ibm_power_ppc64le/hadoop_rhel8_ppcle.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/ibm_power_ppc64le/hadoop_rhel8_ppcle.mdx @@ -1,67 +1,44 @@ --- -title: "Installing Hadoop Foreign Data Wrapper on RHEL 8 IBM Power (ppc64le)" -navTitle: "RHEL 8" +navTitle: RHEL 8 +title: Installing Hadoop Foreign Data Wrapper on RHEL 8 ppc64le --- -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. - -To log in as a superuser: +Before you begin the installation process, log in as superuser. ```shell +# To log in as a superuser: 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 - ``` +## Set up the repository - This creates the /etc/yum.repos.d/edb.repo configuration file. +Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). -1. Add your EDB credentials to the edb.repo file: - - ```shell - sed -i "s@:@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). +```shell +# Set up the EDB repository: +dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm -1. Install the EPEL repository and refresh the cache: +# Replace '' and '' below with +# your username and password for the EDB repository: +sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ```shell - dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm - dnf makecache - ``` +# Install the EPEL repository: +dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -1. Enable the codeready-builder-for-rhel-8-\*-rpms repository since EPEL packages may depend on packages from it: +# Refresh the cache: +dnf makecache - ```shell - ARCH=$( /bin/arch ) - subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" - ``` +# Enable additional repositories to resolve dependencies: +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 - ``` +# Disable the built-in PostgreSQL module: +dnf -qy module disable postgresql +``` -## Installing the package +## Install the package ```shell -dnf -y install edb-as-hdfs_fdw +dnf -y install edb-as14-hdfs_fdw ``` -where `xx` is the server version number. - - +Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_centos7_x86.mdx b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_centos7_x86.mdx index 20dc578a07b..dce6184082c 100644 --- a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_centos7_x86.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_centos7_x86.mdx @@ -1,30 +1,37 @@ --- -title: "Installing Hadoop Foreign Data Wrapper on CentOS 7 x86" -navTitle: "CentOS 7" +navTitle: CentOS 7 +title: Installing Hadoop Foreign Data Wrapper on CentOS 7 x86_64 --- -1. To create the repository configuration file, assume superuser privileges, and invoke the following command: +Before you begin the installation process, log in as superuser. - ```text - yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` +```shell +# To log in as a superuser: +sudo su - +``` -2. Replace ‘USERNAME:PASSWORD’ below with your username and password for the EDB repositories: +## Set up the repository - ```text - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` +Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). -3. Install the EPEL repository: +```shell +# Set up the EDB repository: +yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ```text - yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm - ``` +# Replace '' and '' below with +# your username and password for the EDB repository: +sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo -5. Install the selected package: +# Install the EPEL repository: +yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm - ```text - dnf install edb-as-hdfs_fdw - ``` - where `xx` is the server version number. +``` + +## Install the package + +```shell +yum -y install edb-as14-hdfs_fdw +``` + +Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_other_linux8_x86.mdx b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_other_linux8_x86.mdx index 8a5afe2db79..4965f469783 100644 --- a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_other_linux8_x86.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_other_linux8_x86.mdx @@ -1,42 +1,41 @@ --- -title: "Installing Hadoop Foreign Data Wrapper on Rocky Linux 8/AlmaLinux 8 x86" -navTitle: "Rocky Linux 8/AlmaLinux 8" +navTitle: AlmaLinux 8 or Rocky Linux 8 +title: Installing Hadoop Foreign Data Wrapper on AlmaLinux 8 or Rocky Linux 8 x86_64 --- -1. To create the repository configuration file, assume superuser privileges, and invoke the following command: - - ```text - dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` +Before you begin the installation process, log in as superuser. -2. Replace ‘USERNAME:PASSWORD’ below with your username and password for the EDB repositories: +```shell +# To log in as a superuser: +sudo su - +``` - ```text - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` +## Set up the repository -3. Install the EPEL repository: +Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - ```text - dnf -y install epel-release - ``` +```shell +# Set up the EDB repository: +dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm -4. Enable the additional repositories to resolve dependencies: +# Replace '' and '' below with +# your username and password for the EDB repository: +sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ```text - dnf config-manager --set-enabled PowerTools - ``` +# Install the EPEL repository: +dnf -y install epel-release -5. Disable the built-in PostgreSQL module: +# Enable additional repositories to resolve dependencies: +dnf config-manager --set-enabled PowerTools - ```text - dnf -qy module disable postgresql - ``` -6. Install the selected package: - - ```text - dnf install edb-as-hdfs_fdw - ``` +# Disable the built-in PostgreSQL module: +dnf -qy module disable postgresql +``` - where `xx` is the server version number. +## Install the package +```shell +dnf -y install edb-as14-hdfs_fdw +``` + +Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_rhel7_x86.mdx b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_rhel7_x86.mdx index 56b636b5419..37d6884a244 100644 --- a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_rhel7_x86.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_rhel7_x86.mdx @@ -1,36 +1,38 @@ --- -title: "Hadoop Foreign Data Wrapper on RHEL 7/OL 7 x86" -navTitle: "RHEL 7/OL 7 " +navTitle: RHEL 7 or OL 7 +title: Installing Hadoop Foreign Data Wrapper on RHEL 7 or OL 7 x86_64 --- -1. To create the repository configuration file, assume superuser privileges, and invoke the following command: +Before you begin the installation process, log in as superuser. - ```text - yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` +```shell +# To log in as a superuser: +sudo su - +``` -2. Replace ‘USERNAME:PASSWORD’ below with your username and password for the EDB repositories: +## Set up the repository - ```text - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` +Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). -3. Install the EPEL repository: +```shell +# Set up the EDB repository: +yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ```text - yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm - ``` +# Replace '' and '' below with +# your username and password for the EDB repository: +sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo -4. Enable additional repositories to resolve dependencies: +# Install the EPEL repository: +yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm - ```text - subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" - ``` +# Enable additional repositories to resolve dependencies: +subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" +``` -5. Install the selected package: +## Install the package - ```text - dnf install edb-as-hdfs_fdw - ``` +```shell +yum -y install edb-as14-hdfs_fdw +``` - where `xx` is the server version number. +Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_rhel8_x86.mdx b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_rhel8_x86.mdx index 5f32859801a..d9c29e9492d 100644 --- a/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_rhel8_x86.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/x86_amd64/hadoop_rhel8_x86.mdx @@ -1,42 +1,41 @@ --- -title: "Installing Hadoop Foreign Data Wrapper on RHEL 8/OL 8 x86" -navTitle: "RHEL 8/OL 8" +navTitle: RHEL 8 or OL 8 +title: Installing Hadoop Foreign Data Wrapper on RHEL 8 or OL 8 x86_64 --- -1. To create the repository configuration file, assume superuser privileges, and invoke the following command: - - ```text - dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` +Before you begin the installation process, log in as superuser. -2. Replace ‘USERNAME:PASSWORD’ below with your username and password for the EDB repositories: +```shell +# To log in as a superuser: +sudo su - +``` - ```text - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` +## Set up the repository -3. Install the EPEL repository: +Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - ```text - dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm - ``` +```shell +# Set up the EDB repository: +dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm -4. Enable the additional repositories to resolve dependencies: +# Replace '' and '' below with +# your username and password for the EDB repository: +sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ```text - dnf config-manager --set-enabled PowerTools - ``` +# Install the EPEL repository: +dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -5. Disable the built-in PostgreSQL module: +# Enable additional repositories to resolve dependencies: +dnf config-manager --set-enabled PowerTools - ```text - dnf -qy module disable postgresql - ``` -6. Install the selected package: - - ```text - dnf install edb-as-hdfs_fdw - ``` +# Disable the built-in PostgreSQL module: +dnf -qy module disable postgresql +``` - where `xx` is the server version number. +## Install the package +```shell +dnf -y install edb-as14-hdfs_fdw +``` + +Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/ibm_power_ppc64le/mongo_rhel8_ppcle.mdx b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/ibm_power_ppc64le/mongo_rhel8_ppcle.mdx index 12a1e8a3bd0..f0473a7202c 100644 --- a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/ibm_power_ppc64le/mongo_rhel8_ppcle.mdx +++ b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/ibm_power_ppc64le/mongo_rhel8_ppcle.mdx @@ -1,66 +1,44 @@ --- -title: "Installing MongoDB Foreign Data Wrapper on RHEL 8 IBM Power (ppc64le)" -navTitle: "RHEL 8" +navTitle: RHEL 8 +title: Installing MongoDB Foreign Data Wrapper on RHEL 8 ppc64le --- -There are two steps to completing an installation: - -- Setting up the repository -- Installing the package - -For each step, you must be logged in as superuser. - -To log in as a superuser: +Before you begin the installation process, log in as superuser. ```shell +# To log in as a superuser: 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 - ``` +## Set up the repository - This creates the /etc/yum.repos.d/edb.repo configuration file. +Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). -1. Add your EDB credentials to the edb.repo file: - - ```shell - sed -i "s@:@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). +```shell +# Set up the EDB repository: +dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm -1. Install the EPEL repository and refresh the cache: +# Replace '' and '' below with +# your username and password for the EDB repository: +sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ```shell - dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm - dnf makecache - ``` +# Install the EPEL repository: +dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -1. Enable the codeready-builder-for-rhel-8-\*-rpms repository since EPEL packages may depend on packages from it: +# Refresh the cache: +dnf makecache - ```shell - ARCH=$( /bin/arch ) - subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" - ``` +# Enable additional repositories to resolve dependencies: +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 - ``` +# Disable the built-in PostgreSQL module: +dnf -qy module disable postgresql +``` -## Installing the package +## Install the package ```shell -dnf -y install edb-as-mongo_fdw +dnf -y install edb-as14-mongo_fdw ``` -where `xx` is the server version number. - +Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_centos7_x86.mdx b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_centos7_x86.mdx index b3db364d58b..1c42e21f74e 100644 --- a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_centos7_x86.mdx +++ b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_centos7_x86.mdx @@ -1,31 +1,37 @@ --- -title: "Installing MongoDB Foreign Data Wrapper on CentOS 7 x86" -navTitle: "CentOS 7" +navTitle: CentOS 7 +title: Installing MongoDB Foreign Data Wrapper on CentOS 7 x86_64 --- -1. To create the repository configuration file, assume superuser privileges, and invoke the following command: +Before you begin the installation process, log in as superuser. - ```text - yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` +```shell +# To log in as a superuser: +sudo su - +``` -2. Replace ‘USERNAME:PASSWORD’ below with your username and password for the EDB repositories: +## Set up the repository - ```text - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` +Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). -3. Install the EPEL repository: +```shell +# Set up the EDB repository: +yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ```text - yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm - ``` - -5. Install the selected package: +# Replace '' and '' below with +# your username and password for the EDB repository: +sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ```text - dnf install edb-as-mongo_fdw - ``` +# Install the EPEL repository: +yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm - where `xx` is the server version number. +``` + +## Install the package + +```shell +yum -y install edb-as14-mongo_fdw +``` + +Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_other_linux8_x86.mdx b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_other_linux8_x86.mdx index ebc9671a4f1..7f976b231da 100644 --- a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_other_linux8_x86.mdx +++ b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_other_linux8_x86.mdx @@ -1,42 +1,41 @@ --- -title: "Installing MongoDB Foreign Data Wrapper on Rocky Linux 8/AlmaLinux 8 x86" -navTitle: "Rocky Linux 8/AlmaLinux 8" +navTitle: AlmaLinux 8 or Rocky Linux 8 +title: Installing MongoDB Foreign Data Wrapper on AlmaLinux 8 or Rocky Linux 8 x86_64 --- -1. To create the repository configuration file, assume superuser privileges, and invoke the following command: - - ```text - dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` +Before you begin the installation process, log in as superuser. -2. Replace ‘USERNAME:PASSWORD’ below with your username and password for the EDB repositories: +```shell +# To log in as a superuser: +sudo su - +``` - ```text - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` +## Set up the repository -3. Install the EPEL repository: +Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - ```text - dnf -y install epel-release - ``` +```shell +# Set up the EDB repository: +dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm -4. Enable additional repositories to resolve dependencies: +# Replace '' and '' below with +# your username and password for the EDB repository: +sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ```text - dnf config-manager --set-enabled PowerTools - ``` +# Install the EPEL repository: +dnf -y install epel-release -5. Disable the built-in PostgreSQL module: +# Enable additional repositories to resolve dependencies: +dnf config-manager --set-enabled PowerTools - ```text - dnf -qy module disable postgresql - ``` +# Disable the built-in PostgreSQL module: +dnf -qy module disable postgresql +``` -6. Install the selected package: - - ```text - dnf install edb-as-mongo_fdw - ``` +## Install the package - where `xx` is the server version number. \ No newline at end of file +```shell +dnf -y install edb-as14-mongo_fdw +``` + +Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_rhel7_x86.mdx b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_rhel7_x86.mdx index e6b783ca1d7..2994671ceb8 100644 --- a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_rhel7_x86.mdx +++ b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_rhel7_x86.mdx @@ -1,37 +1,38 @@ --- -title: "Installing MongoDB Foreign Data Wrapper on RHEL 7/OL 7 x86" -navTitle: "RHEL 7/OL 7 " +navTitle: RHEL 7 or OL 7 +title: Installing MongoDB Foreign Data Wrapper on RHEL 7 or OL 7 x86_64 --- -1. To create the repository configuration file, assume superuser privileges, and invoke the following command: +Before you begin the installation process, log in as superuser. - ```text - yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` +```shell +# To log in as a superuser: +sudo su - +``` -2. Replace ‘USERNAME:PASSWORD’ below with your username and password for the EDB repositories: +## Set up the repository - ```text - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` +Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). -3. Install the EPEL repository: +```shell +# Set up the EDB repository: +yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ```text - yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm - ``` +# Replace '' and '' below with +# your username and password for the EDB repository: +sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo -4. Enable additional repositories to resolve dependencies: +# Install the EPEL repository: +yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm - ```text - subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" - ``` +# Enable additional repositories to resolve dependencies: +subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" +``` -5. Install the selected package: +## Install the package - ```text - dnf install edb-as-mongo_fdw - ``` - - where `xx` is the server version number. +```shell +yum -y install edb-as14-mongo_fdw +``` +Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_rhel8_x86.mdx b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_rhel8_x86.mdx index 9cf49d211fa..a214b6985a2 100644 --- a/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_rhel8_x86.mdx +++ b/product_docs/docs/mongo_data_adapter/5/04_installing_the_mongo_data_adapter/x86_amd64/mongo_rhel8_x86.mdx @@ -1,41 +1,41 @@ --- -title: "Installing MongoDB Foreign Data Wrapper on RHEL 8/OL 8 x86" -navTitle: "RHEL 8/OL 8" +navTitle: RHEL 8 or OL 8 +title: Installing MongoDB Foreign Data Wrapper on RHEL 8 or OL 8 x86_64 --- -1. To create the repository configuration file, assume superuser privileges, and invoke the following command: - - ```text - dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` +Before you begin the installation process, log in as superuser. -2. Replace ‘USERNAME:PASSWORD’ below with your username and password for the EDB repositories: +```shell +# To log in as a superuser: +sudo su - +``` - ```text - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` +## Set up the repository -3. Install the EPEL repository: +Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - ```text - dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm - ``` +```shell +# Set up the EDB repository: +dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm -4. Enable additional repositories to resolve dependencies: +# Replace '' and '' below with +# your username and password for the EDB repository: +sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ```text - ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" - ``` +# Install the EPEL repository: +dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -5. Disable the built-in PostgreSQL module: +# Enable additional repositories to resolve dependencies: +ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" - ```text - dnf -qy module disable postgresql - ``` -6. Install the selected package: - - ```text - dnf install edb-as-mongo_fdw - ``` +# Disable the built-in PostgreSQL module: +dnf -qy module disable postgresql +``` - where `xx` is the server version number. \ No newline at end of file +## Install the package + +```shell +dnf -y install edb-as14-mongo_fdw +``` + +Where `14` is the version of EDB Postgres Advanced Server. Replace `14` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/ibm_power_ppc64le/pem_agent_rhel8_ppcle.mdx b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/ibm_power_ppc64le/pem_agent_rhel8_ppcle.mdx index e4251563877..54e717eabe1 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/ibm_power_ppc64le/pem_agent_rhel8_ppcle.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/ibm_power_ppc64le/pem_agent_rhel8_ppcle.mdx @@ -1,66 +1,33 @@ --- -title: "Installing the PEM agent on RHEL 8 ppc64le" -navTitle: "RHEL 8" +navTitle: RHEL 8 +title: Installing Postgres Enterprise Manager agent on RHEL 8 ppc64le --- - -Perform these two steps to complete an installation. You must be logged in as superuser. - - -- [Setting up the repository](#setting-up-the-repository) -- [Installing the package](#installing-the-package) - -To log in as a superuser: +Before you begin the installation process, log in as superuser. ```shell +# To log in as a superuser: 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 coommand creates the `/etc/yum.repos.d/edb.repo` configuration file. - -1. Replace `'USERNAME:PASSWORD'` with your username and password available from your - [EDB account](https://www.enterprisedb.com/user) in the `edb.repo` file: - ```shell - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` +## Set up the repository -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 might 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 - ``` +Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). +```shell +# Set up the EDB repository: +dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm -### Installing the package +# Replace '' and '' below with +# your username and password for the EDB repository: +sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo +``` - ```shell - dnf -y install edb-pem-agent - ``` -After installing the PEM agent, you must register the agent. For detailed information, see [Registering an agent](../../../registering_agent). +## Install the package +```shell +dnf -y install edb-pem-agent +``` +After installing PEM agent, you need to register the PEM agent. For detailed information see [Registering an agent](/pem/latest/registering_agent/). diff --git a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_centos7_x86.mdx b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_centos7_x86.mdx index de13b682e5a..c945bf2df33 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_centos7_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_centos7_x86.mdx @@ -1,47 +1,32 @@ --- -title: "Installing the PEM agent on CentOS 7 x86" -navTitle: "CentOS 7" +navTitle: CentOS 7 +title: Installing Postgres Enterprise Manager agent on CentOS 7 x86_64 --- -A PEM agent can monitor one or more servers on one or more hosts. For detailed information about managing a PEM agent, see the [Managing an agent](../../../managing_pem_agent). - -On a CentOS system, you can use the yum package manager to install a PEM agent. The installation tool you use depends on the version of the host operating system. Before installing the agent, verify that your system contains the required prerequisite software. - -## Install the epel-release package +Before you begin the installation process, log in as superuser. ```shell -yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm +# To log in as a superuser: +sudo su - ``` -## Install and configure the edb.repo file +## Set up the repository -To create an EDB repository configuration file, assume superuser privileges and invoke the following command: +Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). ```shell -yum -y install https://yum.enterprisedb.com/edb-repo-rpms/edb-repo-latest.noarch.rpm -``` - -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. After creating the `edb.repo` file, use the following command to replace the `USERNAME` and `PASSWORD` placeholders in the `baseurl` specification with the username and password of a registered EDB user: +# Set up the EDB repository: +yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm -```shell +# Replace '' and '' below with +# your username and password for the EDB repository: sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo ``` -To request credentials for the repository, contact [EDB](https://www.enterprisedb.com/repository-access-request). - -## Installing the PEM agent - -Install the PEM agent package: +## Install the package - ```shell - yum install edb-pem-agent - ``` - -When the installation is complete, you can review a list of the installed packages and dependencies. - -When you install an RPM package that's signed by a source that isn't recognized by your system, yum might ask for your permission to import the key to your local server. If prompted, and you're satisfied that the packages come from a trustworthy source, enter `y`, and press **Return** to continue. - -During the installation, yum might encounter a dependency that it can't resolve. If it does, it provides a list of the required dependencies to manually resolve. - -After installing PEM agent using yum, register the PEM agent. For detailed information, see [Registering an agent](../../../registering_agent). +```shell +yum -y install edb-pem-agent +``` +After installing PEM agent, you need to register the PEM agent. For detailed information see [Registering an agent](/pem/latest/registering_agent/). diff --git a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_other_linux8_x86.mdx b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_other_linux8_x86.mdx index 0bb4d452899..613e2b2f042 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_other_linux8_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_other_linux8_x86.mdx @@ -1,52 +1,33 @@ --- -title: "Installing the PEM agent on Rocky Linux 8/AlmaLinux x86" -navTitle: "Rocky Linux 8/AlmaLinux 8" +navTitle: AlmaLinux 8 or Rocky Linux 8 +title: Installing Postgres Enterprise Manager agent on AlmaLinux 8 or Rocky Linux 8 x86_64 --- -A PEM Agent can monitor one or more servers on one or more hosts. For detailed information about managing a PEM agent, see [Managing an agent](../../../managing_pem_agent). -On a Rocky Linux or AlmaLinux system, you can use the `dnf` command to install a PEM agent. Tthe installation tool you use depends on the version of the host operating system. Before installing the agent, verify that your system contains the required prerequisite software. - -## Install the epel-release package - -```shell -dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -``` - -## Enable the powertools repository since EPEL packages may depend on packages from it +Before you begin the installation process, log in as superuser. ```shell -dnf config-manager --set-enabled powertools +# To log in as a superuser: +sudo su - ``` -## Install and configure the edb.repo file +## Set up the repository -To create an EDB repository configuration file, assume superuser privileges and invoke the following command: +Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). ```shell -dnf -y install https://yum.enterprisedb.com/edb-repo-rpms/edb-repo-latest.noarch.rpm -``` +# Set up the EDB repository: +dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. After creating the `edb.repo` file, use the following command to replace the `USERNAME` and `PASSWORD` placeholders in the `baseurl` specification with the username and password of a registered EDB user: - -```shell +# Replace '' and '' below with +# your username and password for the EDB repository: sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo ``` -To request credentials for the repository, contact [EDB](https://www.enterprisedb.com/repository-access-request). +## Install the package -## Installing the PEM agent - -- Install the PEM agent package: - - ```shell - dnf install edb-pem-agent - ``` - -When the installation is complete, you can review a list of the installed packages and dependencies. - -When you install an RPM package that's signed by a source that isn't recognized by your system, yum might ask for your permission to import the key to your local server. If prompted, and you're satisfied that the packages come from a trustworthy source, enter `y`, and press **Return** to continue. - -During the installation, yum might encounter a dependency that it can't resolve. If it does, it provides a list of the required dependencies to manually resolve. +```shell +dnf -y install edb-pem-agent +``` -After installing PEM Agent using `dnf`, register the PEM agent. For detailed information, see [Registering an agent](../../../registering_agent). +After installing PEM agent, you need to register the PEM agent. For detailed information see [Registering an agent](/pem/latest/registering_agent/). diff --git a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_rhel7_x86.mdx b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_rhel7_x86.mdx index 7cf0a37af34..9f348185f2f 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_rhel7_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_rhel7_x86.mdx @@ -1,53 +1,34 @@ --- -title: "Installing the PEM agent on RHEL 7/OL 7 x86" -navTitle: "RHEL 7/OL 7" +navTitle: RHEL 7 or OL 7 +title: Installing Postgres Enterprise Manager agent on RHEL 7 or OL 7 x86_64 --- -A PEM agent can monitor one or more servers on one or more hosts. For detailed information about managing a PEM agent, see [Managing an agent](../../../managing_pem_agent). -On a RHEL or OL system, you can use the yum package manager to install a PEM Agent. The installation tool you use depends on the version of the host operating system. Before installing the agent, verify that your system contains the required prerequisite software. - -## Install the epel-release package - -```shell -yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm -``` - -If you are a Red Hat Network user, enable the optional, extras, and HA repositories since EPEL packages might depend on packages from these repositories: +Before you begin the installation process, log in as superuser. ```shell -subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" +# To log in as a superuser: +sudo su - ``` -## Install and configure the edb.repo file +## Set up the repository -To create an EDB repository configuration file, assume superuser privileges and invoke the following command: +Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). ```shell -yum -y install https://yum.enterprisedb.com/edb-repo-rpms/edb-repo-latest.noarch.rpm -``` +# Set up the EDB repository: +yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. After creating the `edb.repo` file, use the following command to replace the `USERNAME` and `PASSWORD` placeholders in the `baseurl` specification with the username and password of a registered EDB user: - -```shell +# Replace '' and '' below with +# your username and password for the EDB repository: sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo ``` -To request credentials for the repository, contact [EDB](https://www.enterprisedb.com/repository-access-request). +## Install the package -## Installing the PEM agent - -Install the PEM agent package: - - ```shell - yum install edb-pem-agent - ``` - -When the installation is complete, you can review a list of the installed packages and dependencies. - -When you install an RPM package that's signed by a source that isn't recognized by your system, yum might ask for your permission to import the key to your local server. If prompted, and you're satisfied that the packages come from a trustworthy source, enter `y`, and press **Return** to continue. - -During the installation, yum might encounter a dependency that it can't resolve. If it does, it provides a list of the required dependencies to manually resolve. +```shell +yum -y install edb-pem-agent +``` -After installing PEM agent using yum, register the PEM agent. For detailed information, see [Registering an agent](../../../registering_agent). +After installing PEM agent, you need to register the PEM agent. For detailed information see [Registering an agent](/pem/latest/registering_agent/). diff --git a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_rhel8_x86.mdx b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_rhel8_x86.mdx index 8d599fa1dfc..b433f43ada0 100644 --- a/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_rhel8_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_agent/installing_on_linux/x86_amd64/pem_agent_rhel8_x86.mdx @@ -1,53 +1,34 @@ --- -title: "Installing the PEM agent on RHEL 8/OL 8 x86" -navTitle: "RHEL 8/OL 8" +navTitle: RHEL 8 or OL 8 +title: Installing Postgres Enterprise Manager agent on RHEL 8 or OL 8 x86_64 --- -A PEM agent can monitor one or more servers on one or more hosts. For detailed information about managing a PEM agent, see [Managing an agent](../../../managing_pem_agent). -On a RHEL or OL system, you can use the `dnf` command to install a PEM agent. The installation tool you use depends on the version of the host operating system. Before installing the agent, verify that your system contains the required prerequisite software. - -## Install the epel-release package +Before you begin the installation process, log in as superuser. ```shell -dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm +# To log in as a superuser: +sudo su - ``` -If you are a Red Hat Network user, enable the codeready-builder-for-rhel-8-*-rpms repository, since EPEL packages might depend on packages from it: - -```shell -ARCH=$( /bin/arch ) -subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" -``` +## Set up the repository -## Install and configure the edb.repo file - -To create an EDB repository configuration file, assume superuser privileges and invoke the following command: +Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). ```shell -dnf -y install https://yum.enterprisedb.com/edb-repo-rpms/edb-repo-latest.noarch.rpm -``` - -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. After creating the `edb.repo` file, use the following command to replace the `USERNAME` and `PASSWORD` placeholders in the `baseurl` specification with the username and password of a registered EDB user: +# Set up the EDB repository: +dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm -```shell +# Replace '' and '' below with +# your username and password for the EDB repository: sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo ``` -To request credentials for the repository, contact [EDB](https://www.enterprisedb.com/repository-access-request). - -## Installing the PEM agent - -- Install the PEM agent package: - - ```shell - dnf install edb-pem-agent - ``` -When the installation is complete, you can review a list of the installed packages and dependencies. +## Install the package -When you install an RPM package that's signed by a source that isn't recognized by your system, yum might ask for your permission to import the key to your local server. If prompted, and you're satisfied that the packages come from a trustworthy source, enter `y`, and press **Return** to continue. - -During the installation, yum might encounter a dependency that it can't resolve. If it does, it provides a list of the required dependencies to manually resolve. +```shell +dnf -y install edb-pem-agent +``` -After installing PEM agent using `dnf`, register the PEM agent. For detailed information, see [Registering an agent](../../../registering_agent). +After installing PEM agent, you need to register the PEM agent. For detailed information see [Registering an agent](/pem/latest/registering_agent/). diff --git a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/ibm_power_ppc64le/pem_server_rhel8_ppcle.mdx b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/ibm_power_ppc64le/pem_server_rhel8_ppcle.mdx index 3fedbfa0f48..c2640ef4e89 100644 --- a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/ibm_power_ppc64le/pem_server_rhel8_ppcle.mdx +++ b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/ibm_power_ppc64le/pem_server_rhel8_ppcle.mdx @@ -1,87 +1,37 @@ --- -title: "Installing the PEM server on RHEL 8 ppc64le" -navTitle: "RHEL 8" +navTitle: RHEL 8 +title: Installing Postgres Enterprise Manager server on RHEL 8 ppc64le --- -Before you begin the installation process, log in as superuser: +Before you begin the installation process: + +1. Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). + +2. Log in as superuser: ```shell -# To log in as a superuser: sudo su - ``` -## Prerequisites - -- Postres Enterprise Manager requires a Postgres server running either [EDB Postgres Advanced Server](/epas/latest) or [PostgresSQL](/supported-open-source/postgresql/) version 11 or later to hold the Postgres Enterprise Manager backend database. - - 1. Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/epas_inst_linux) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). - - 2. Configure authentication on the Postgres server by updating the `pg_hba.conf` file. The `pg_hba.conf` file manages connections. Verify that the `pg_hba.conf` file allows connections from the PEM server, the monitoring PEM agent, and the host of the Apache web server server. - - - If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - - - If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). - - 3. Verify that the sslutils extension and `hstore` contrib module are installed on your Postgres server. - - - If you're using EDB Postgres Advanced Server, the sslutils extension and hstore contrib module are installed by default. - - - If you're using PostgreSQL, verify that you have access to the PostgreSQL community repository, and then install the sslutils extension and the hstore contrib module: - - ```shell - dnf install postgresql-_sslutils postgresql-contrib - ``` - - Where `x` is the Postgres server version. - - 4. If you're using a firewall, allow access to port 8443 on the Postgres server: - - ```shell - firewall-cmd --permanent --zone=public --add-port=8443/tcp - - firewall-cmd --reload - ``` - -- Verify that the components Postgres Enterprise Manager depends on, such as python3, libboost, openssl (1.0.2k or later), snmp++, and libcurl, are up to date: - - ```shell - dnf upgrade - ``` - -### 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). +## Set up the repository -1. Set up the EDB repository: +Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). - ```shell - dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` - - This command creates the `/etc/yum.repos.d/edb.repo` configuration file. - -1. Replace `'USERNAME:PASSWORD'` with your username and password available from your - [EDB account](https://www.enterprisedb.com/user) in the `edb.repo` file: - - ```shell - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` - -1. Disable the built-in PostgreSQL module: - - ```shell - dnf -qy module disable postgresql - ``` +```shell +# Set up the EDB repository: +dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm -### Installing the package +# Replace '' and '' below with +# your username and password for the EDB repository: +sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo +``` - ```shell - dnf -y install edb-pem - ``` - -!!! Note - The operating system user pem is created while installing the PEM Server. The PEM server web application is a WSGI application that runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. +## Install the package +```shell +dnf -y install edb-pem +``` ## Initial configuration @@ -90,4 +40,8 @@ sudo su - /usr/edb/pem/bin/configure-pem-server.sh ``` -For more details, see [Configuring the PEM server on Linux](../../configuring_the_pem_server_on_linux/). +For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/pem_server_inst_linux/configuring_the_pem_server_on_linux/). + +!!! Note + - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + diff --git a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/ibm_power_ppc64le/pem_server_sles12_ppcle.mdx b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/ibm_power_ppc64le/pem_server_sles12_ppcle.mdx index 963d89568eb..9a337d65d76 100644 --- a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/ibm_power_ppc64le/pem_server_sles12_ppcle.mdx +++ b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/ibm_power_ppc64le/pem_server_sles12_ppcle.mdx @@ -5,7 +5,7 @@ title: Installing Postgres Enterprise Manager server on SLES 12 ppc64le Before you begin the installation process: -1. Review the [prerequisites](/pem/latest/installing_pem_server/installing_on_linux/prerequisites/). +1. Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). 2. Log in as superuser: @@ -52,4 +52,7 @@ zypper -n install edb-pem /usr/edb/pem/bin/configure-pem-server.sh ``` -For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/installing_on_linux/configuring_the_pem_server_on_linux/). +For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/pem_server_inst_linux/configuring_the_pem_server_on_linux/). + +!!! Note + - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. diff --git a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/ibm_power_ppc64le/pem_server_sles15_ppcle.mdx b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/ibm_power_ppc64le/pem_server_sles15_ppcle.mdx index 73d9a285af4..dd996675ec7 100644 --- a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/ibm_power_ppc64le/pem_server_sles15_ppcle.mdx +++ b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/ibm_power_ppc64le/pem_server_sles15_ppcle.mdx @@ -5,7 +5,7 @@ title: Installing Postgres Enterprise Manager server on SLES 15 ppc64le Before you begin the installation process: -1. Review the [prerequisites](/pem/latest/installing_pem_server/installing_on_linux/prerequisites/). +1. Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). 2. Log in as superuser: @@ -51,4 +51,7 @@ zypper -n install edb-pem /usr/edb/pem/bin/configure-pem-server.sh ``` -For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/installing_on_linux/configuring_the_pem_server_on_linux/). +For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/pem_server_inst_linux/configuring_the_pem_server_on_linux/). + +!!! Note + - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. diff --git a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/index.mdx b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/index.mdx index fadefa02226..fffede13f40 100644 --- a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/index.mdx +++ b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/index.mdx @@ -12,7 +12,6 @@ navigation: - pem_server_ubuntu20_x86 - pem_server_ubuntu18_x86 - pem_server_deb10_x86 -- pem_server_deb9_x86 --- For Linux x86-64 (amd64), see: @@ -26,4 +25,4 @@ For Linux x86-64 (amd64), see: - [Ubuntu 20.04](pem_server_ubuntu20_x86) - [Ubuntu 18.04](pem_server_ubuntu18_x86) - [Debian 10](pem_server_deb10_x86) - - [Debian 9](pem_server_deb9_x86) + diff --git a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_centos7_x86.mdx b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_centos7_x86.mdx index b2b0ec29834..fbe1f476d4c 100644 --- a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_centos7_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_centos7_x86.mdx @@ -1,83 +1,52 @@ --- -title: "Installing the PEM server on CentOS 7 x86" -navTitle: "CentOS 7" +navTitle: CentOS 7 +title: Installing Postgres Enterprise Manager server on CentOS 7 x86_64 --- -On a CentOS system, you can use the yum package manager to install a PEM server. The installation tool you use depends on the version of the host operating system. Before installing the server, you must verify that your system contains the required prerequisite software. -## Prerequisites +Before you begin the installation process: -- Postres Enterprise Manager requires a Postgres server running either [EDB Postgres Advanced Server](/epas/latest) or [PostgresSQL](/supported-open-source/postgresql/) version 11 or later to hold the Postgres Enterprise Manager backend database. - - 1. Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/epas_inst_linux) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). - - 2. Configure authentication on the Postgres server by updating the `pg_hba.conf` file. The `pg_hba.conf` file manages connections. Make sure that the `pg_hba.conf` file allows connections from the PEM server, the monitoring PEM agent, and the host of the Apache web server server. - - - If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - - - If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). - - 3. Verify that the sslutils extension and hstore contrib module are installed on your Postgres server. - - - If you're using EDB Postgres Advanced Server, the sslutils extension and hstore contrib module are installed by default. +1. Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). - - If you're using PostgreSQL, verify that you have access to the PostgreSQL community repository, and then install the sslutils extension and the hstore contrib module: +2. Log in as superuser: - ```shell - yum install postgresql-_sslutils postgresql-contrib - ``` - - Where `x` is the Postgres server version. - - 4. If you're using a firewall, allow access to port 8443 on the Postgres server: - - ```shell - firewall-cmd --permanent --zone=public --add-port=8443/tcp - - firewall-cmd --reload - ``` +```shell +sudo su - +``` -- Verify that the components Postgres Enterprise Manager depends on, such as python3, libboost, openssl (1.0.2k or later), snmp++, and libcurl, are up to date: +## Set up the repository - ```shell - yum upgrade - ``` +Setting up the repository is a one-time task. If you have already set up your repository, you do not need to perform this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). -## Install and configure the edb.repo file +```shell +# Set up the EDB repository: +yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm -To create an EnterpriseDB repository configuration file, assume superuser privileges and invoke the following command: +# Replace '' and '' below with +# your username and password for the EDB repository: +sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo -```shell -yum -y install https://yum.enterprisedb.com/edb-repo-rpms/edb-repo-latest.noarch.rpm ``` -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. After creating the `edb.repo` file, use the following command to replace the `USERNAME` and `PASSWORD` placeholders in the `baseurl` specification with the username and password of a registered EDB user: +## Install the package ```shell -sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo +yum -y install edb-pem ``` -To request credentials for the repository, contact [EDB](https://www.enterprisedb.com/repository-access-request). - -## Install the PEM server - -After meeting the platform-specific prerequisites, you can use yum to install the PEM server: +## Initial configuration ```shell -yum install edb-pem +# You can configure the PEM server using the following command: +/usr/edb/pem/bin/configure-pem-server.sh ``` -!!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. +For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/pem_server_inst_linux/configuring_the_pem_server_on_linux/). -If you're doing a fresh installation of the PEM server on a CentOS 7.x host, the installer also installs `edb-python3-mod_wsgi` packages with the installation as required by the operating system. -If you're upgrading the PEM server on a CentOS 7.x host, the `mod_wsgi system` package is replaced by the `edb-python3-mod_wsgi` package as required by the operating system. - -When you install an RPM package that's signed by a source that isn't recognized by your system, yum might ask for your permission to import the key to your local server. If prompted, and you are satisfied that the packages come from a trustworthy source, enter `y`, and press **Return** to continue. - -During the installation, yum might encounter a dependency that it can't resolve. If it does, it provides a list of the required dependencies to manually resolve. - -If you want to install PEM server on a machine that's in an isolated network, you must first create a PEM repository on that machine. For more information, see [Creating a PEM repository in an isolated network](../../creating_pem_repository_in_isolated_network/). +!!! Note + - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + + - If you're doing a fresh installation of the PEM server on a CentOS 7.x host, the installer also installs edb-python3-mod_wsgi packages with the installation required by the operating system. -After installing PEM server using yum, you need to configure the PEM server. For detailed information, see [Configuring the PEM server on Linux platforms](../../configuring_the_pem_server_on_linux/). + - If you're upgrading the PEM server on a CentOS 7.x host, the mod_wsgi system package is replaced by the edb-python3-mod_wsgi package as required by the operating system. \ No newline at end of file diff --git a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_deb10_x86.mdx b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_deb10_x86.mdx index a428d267681..340684683e2 100644 --- a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_deb10_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_deb10_x86.mdx @@ -5,7 +5,7 @@ title: Installing Postgres Enterprise Manager server on Debian 10 x86_64 Before you begin the installation process: -1. Review the [prerequisites](/pem/latest/installing_pem_server/installing_on_linux/prerequisites/). +1. Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). 2. Log in as superuser: @@ -49,4 +49,7 @@ apt-get install edb-pem /usr/edb/pem/bin/configure-pem-server.sh ``` -For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/installing_on_linux/configuring_the_pem_server_on_linux/). +For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/pem_server_inst_linux/configuring_the_pem_server_on_linux/). + +!!! Note + - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. diff --git a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_other_linux8_x86.mdx b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_other_linux8_x86.mdx index 37605b56842..c301340b49f 100644 --- a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_other_linux8_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_other_linux8_x86.mdx @@ -1,85 +1,45 @@ --- -title: "Installing the PEM server on Rocky Linux 8/AlmaLinux 8 x86" -navTitle: "Rocky Linux 8/AlmaLinux 8" +navTitle: AlmaLinux 8 or Rocky Linux 8 +title: Installing Postgres Enterprise Manager server on AlmaLinux 8 or Rocky Linux 8 x86_64 --- -On a Rocky Linux or AlmaLinux system, you can use the yum package manager or `dnf` command to install a PEM server. The installation tool you use depends on the version of the host operating system. Before installing the server, verify that your system contains the required prerequisite software. +Before you begin the installation process: -## Prerequisites +1. Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). -- Postres Enterprise Manager requires a Postgres server running either [EDB Postgres Advanced Server](/epas/latest) or [PostgresSQL](/supported-open-source/postgresql/) version 11 or later to hold the Postgres Enterprise Manager backend database. - - 1. Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/epas_inst_linux) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). - - 2. Configure authentication on the Postgres server by updating the `pg_hba.conf` file. The `pg_hba.conf` file manages connections. Verify that the `pg_hba.conf` file allows connections from the PEM server, the monitoring PEM agent, and the host of the Apache web server server. - - - If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - - - If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). - - 3. Verify that the sslutils extension and hstore contrib module are installed on your Postgres server. - - - If you're using EDB Postgres Advanced Server, the sslutils extension and hstore contrib module are installed by default. - - - If you're using PostgreSQL, verify that you have access to the PostgreSQL community repository, and then install the sslutils extension and the hstore contrib module: - - ```shell - dnf install postgresql-_sslutils postgresql-contrib - ``` - - Where `x` is the Postgres server version. - - 4. If you're using a firewall, allow access to port 8443 on the Postgres server: - - ```shell - firewall-cmd --permanent --zone=public --add-port=8443/tcp - - firewall-cmd --reload - ``` - -- Verify that the components Postgres Enterprise Manager depends on, such as python3, libboost, openssl (1.0.2k or later), snmp++, and libcurl, are up to date: - - ```shell - dnf upgrade - ``` - -## Install and configure the edb.repo file - -To create an EnterpriseDB repository configuration file, assume superuser privileges and invoke the following command: +2. Log in as superuser: ```shell -dnf -y install https://yum.enterprisedb.com/edb-repo-rpms/edb-repo-latest.noarch.rpm +sudo su - ``` -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. After creating the `edb.repo` file, use the following command to replace the `USERNAME` and `PASSWORD` placeholders in the `baseurl` specification with the username and password of a registered EDB user: +## Set 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 this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). ```shell +# Set up the EDB repository: +dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + +# Replace '' and '' below with +# your username and password for the EDB repository: sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo ``` -To request credentials for the repository, contact [EDB](https://www.enterprisedb.com/repository-access-request). - -## Disable the built-in PostgreSQL module +## Install the package ```shell -dnf -qy module disable PostgreSQL +dnf -y install edb-pem ``` -## Install the PEM server - -After meeting the platform-specific prerequisites, you can use the `dnf` command to install the PEM server: +## Initial configuration ```shell -dnf install edb-pem +# You can configure the PEM server using the following command: +/usr/edb/pem/bin/configure-pem-server.sh ``` -!!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. - -When you install an RPM package that's signed by a source that isn't recognized by your system, yum might ask for your permission to import the key to your local server. If prompted, and you're satisfied that the packages come from a trustworthy source, enter `y`, and press **Return** to continue. - -During the installation, yum might encounter a dependency that it can't resolve. If it does, it provides a list of the required dependencies to manually resolve. +For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/pem_server_inst_linux/configuring_the_pem_server_on_linux/). -If you want to install PEM server on a machine that's in an isolated network, you must first create the PEM repository on that machine. For more information, see [Creating a PEM repository in an isolated network](../../creating_pem_repository_in_isolated_network/). - -After installing PEM server using yum or the `dnf` command, you need to configure the PEM server. For detailed information, see [Configuring the PEM server on Linux platforms](../../configuring_the_pem_server_on_linux/). +!!! Note + - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. diff --git a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_rhel7_x86.mdx b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_rhel7_x86.mdx index 10b26c4dbde..b3e0899624f 100644 --- a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_rhel7_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_rhel7_x86.mdx @@ -1,84 +1,50 @@ --- -title: "Installing the PEM server on RHEL 7/OL 7 x86" -navTitle: "RHEL 7/OL 7" +navTitle: RHEL 7 or OL 7 +title: Installing Postgres Enterprise Manager server on RHEL 7 or OL 7 x86_64 --- -Before following the detailed instructions that install the PEM server on your specific platform, you must perform the prerequisite steps detailed in [Prerequisites](#prerequisites). +Before you begin the installation process: -On a RHEL or OL system, you can use the yum package manager to install a PEM server. The installation tool you use depends on the version of the host operating system. Before installing the server, verify that your system contains the required prerequisite software. +1. Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). -## Prerequisites - -- Postres Enterprise Manager requires a Postgres server running either [EDB Postgres Advanced Server](/epas/latest) or [PostgresSQL](/supported-open-source/postgresql/) version 11 or later to hold the Postgres Enterprise Manager backend database. - - 1. Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/epas_inst_linux) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). - - 2. Configure authentication on the Postgres server by updating the `pg_hba.conf` file. The `pg_hba.conf` file manages connections. Verify that the `pg_hba.conf` file allows connections from the PEM server, the monitoring PEM agent, and the host of the Apache web server server. - - - If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - - - If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). - - 3. Ensure that the sslutils extension and hstore contrib module are installed on your Postgres server. - - - If you're using EDB Postgres Advanced Server, the sslutils extension and hstore contrib module are installed by default. - - - If you're using PostgreSQL, verify that you have access to the PostgreSQL community repository, and then install the sslutils extension and the hstore contrib module: - - ```shell - yum install postgresql-_sslutils postgresql-contrib - ``` - - Where `x` is the Postgres server version. - - 4. If you're using a firewall, allow access to port 8443 on the Postgres server: - - ```shell - firewall-cmd --permanent --zone=public --add-port=8443/tcp - firewall-cmd --reload - ``` - -- Verify that the components Postgres Enterprise Manager depends on, such as python3, libboost, openssl (1.0.2k or later), snmp++, and libcurl, are up to date: - - ```shell - yum upgrade - ``` - -## Install and configure the edb.repo file - -To create an EnterpriseDB repository configuration file, assume superuser privileges and invoke the following command: +2. Log in as superuser: ```shell -yum -y install https://yum.enterprisedb.com/edb-repo-rpms/edb-repo-latest.noarch.rpm +sudo su - ``` -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. After creating the `edb.repo` file, use the following command to replace the `USERNAME` and `PASSWORD` placeholders in the `baseurl` specification with the username and password of a registered EDB user: +## Set 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 this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). ```shell +# Set up the EDB repository: +yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + +# Replace '' and '' below with +# your username and password for the EDB repository: sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo ``` -To request credentials for the repository, contact [EDB](https://www.enterprisedb.com/repository-access-request). - -## Install the PEM server -After meeting the platform-specific prerequisites, you can use yum to install the PEM server: +## Install the package ```shell -yum install edb-pem +yum -y install edb-pem ``` -!!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. - -If you're doing a fresh installation of the PEM server on a RHEL 7.x host, the installer also installs `edb-python3-mod_wsgi` packages with the installation required by the operating system. +## Initial configuration -If you're upgrading the PEM server on a RHEL 7.x host, the `mod_wsgi system` package is replaced by the `edb-python3-mod_wsgi` package as required by the operating system. +```shell +# You can configure the PEM server using the following command: +/usr/edb/pem/bin/configure-pem-server.sh +``` -When you install an RPM package that's signed by a source that isn't recognized by your system, yum might ask for your permission to import the key to your local server. If prompted, and you're satisfied that the packages come from a trustworthy source, enter `y`, and press **Return** to continue. +For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/pem_server_inst_linux/configuring_the_pem_server_on_linux/). -During the installation, yum might encounter a dependency that it can't resolve. If it does, it provides a list of the required dependencies to manually resolve. +!!! Note + - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. -If you want to install PEM server on a machine that's in an isolated network, you must first create a PEM repository on that machine. For more information, see [Creating a PEM repository in an isolated network](../../creating_pem_repository_in_isolated_network/). + - If you're doing a fresh installation of the PEM server on a RHEL 7.x host, the installer also installs edb-python3-mod_wsgi packages with the installation required by the operating system. -After installing PEM Server using yum, you need to configure the PEM server. For detailed information, see [Configuring the PEM server on Linux platforms](../../configuring_the_pem_server_on_linux/). + - If you're upgrading the PEM server on a RHEL 7.x host, the mod_wsgi system package is replaced by the edb-python3-mod_wsgi package as required by the operating system. diff --git a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_rhel8_x86.mdx b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_rhel8_x86.mdx index 1ac8bd96156..a0799d618bd 100644 --- a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_rhel8_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_rhel8_x86.mdx @@ -1,79 +1,46 @@ --- -title: "Installing the PEM server on RHEL 8/OL 8 x86" -navTitle: "RHEL 8/OL 8 x86" +navTitle: RHEL 8 or OL 8 +title: Installing Postgres Enterprise Manager server on RHEL 8 or OL 8 x86_64 --- -On a RHEL or OL system, you can use the `dnf` command to install a PEM server. The installation tool you use depends on the version of the host operating system. Before installing the server, you must verify that your system contains the required prerequisite software. +Before you begin the installation process: -## Prerequisites +1. Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). -- Postres Enterprise Manager requires a Postgres server running either [EDB Postgres Advanced Server](/epas/latest) or [PostgresSQL](/supported-open-source/postgresql/) version 11 or later to hold the Postgres Enterprise Manager backend database. - - 1. Install the Postgres server. See [Installing EDB Postgres Advanced Server on Linux](/epas/latest/epas_inst_linux) or [Installing PostgreSQL](/supported-open-source/postgresql/installer/). - - 2. Configure authentication on the Postgres server by updating the `pg_hba.conf` file. The `pg_hba.conf` file manages connections. Verify that the `pg_hba.conf` file allows connections from the PEM server, the monitoring PEM agent, and the host of the Apache web server server. - - - If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). - - - If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). - - 3. Verify that the sslutils extension and hstore contrib module are installed on your Postgres server. - - - If you're using EDB Postgres Advanced Server, the sslutils extension and hstore contrib module are installed by default. - - - If you're using PostgreSQL, verify that you have access to the PostgreSQL community repository, and then install the sslutils extension and the hstore contrib module: - - ```shell - dnf install postgresql-_sslutils postgresql-contrib - ``` - - Where `x` is the Postgres server version. - - 4. If you're using a firewall, allow access to port 8443 on the Postgres server: - - ```shell - firewall-cmd --permanent --zone=public --add-port=8443/tcp - firewall-cmd --reload - ``` - -- Verify that the components Postgres Enterprise Manager depends on, such as python3, libboost, openssl (1.0.2k or later), snmp++, and libcurl, are up to date: - - ```shell - dnf upgrade - ``` - - -## Install and configure the edb.repo file - -To create an EnterpriseDB repository configuration file, assume superuser privileges and invoke the following command: +2. Log in as superuser: ```shell -dnf -y install https://yum.enterprisedb.com/edb-repo-rpms/edb-repo-latest.noarch.rpm +sudo su - ``` -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. After creating the `edb.repo` file, use the following command to replace the `USERNAME` and `PASSWORD` placeholders in the `baseurl` specification with the username and password of a registered EDB user: +## Set 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 this step. If you do need to set up the repository, you must register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). ```shell +# Set up the EDB repository: +dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + +# Replace '' and '' below with +# your username and password for the EDB repository: sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo ``` -To request credentials for the repository, contact [EDB](https://www.enterprisedb.com/repository-access-request). - -## Install the PEM server - -After meeting the platform-specific prerequisites, you can use the `dnf` command to install the PEM server: +## Install the package ```shell -dnf install edb-pem +dnf -y install edb-pem ``` -!!! Note - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. -When you install an RPM package that's signed by a source that isn't recognized by your system, yum might ask for your permission to import the key to your local server. If prompted, and you are satisfied that the packages come from a trustworthy source, enter `y`, and press **Return** to continue. +## Initial configuration -During the installation, yum might encounter a dependency that it can't resolve. If it does, it provides a list of the required dependencies to manually resolve. +```shell +# You can configure the PEM server using the following command: +/usr/edb/pem/bin/configure-pem-server.sh +``` -If you want to install PEM server on a machine that's in an isolated network, you must first create a PEM repository on that machine. For more information, see [Creating a PEM repository in an isolated network](../../creating_pem_repository_in_isolated_network/). +For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/pem_server_inst_linux/configuring_the_pem_server_on_linux/). -After installing PEM server using yum or the `dnf` command, you need to configure the PEM server. For detailed information, see [Configuring the PEM server on Linux platforms](../../configuring_the_pem_server_on_linux/). +!!! Note + - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. diff --git a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_sles12_x86.mdx b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_sles12_x86.mdx index 0da2b94bcb5..b7337a9000c 100644 --- a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_sles12_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_sles12_x86.mdx @@ -5,7 +5,7 @@ title: Installing Postgres Enterprise Manager server on SLES 12 x86_64 Before you begin the installation process: -1. Review the [prerequisites](/pem/latest/installing_pem_server/installing_on_linux/prerequisites/). +1. Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). 2. Log in as superuser: @@ -52,4 +52,7 @@ zypper -n install edb-pem /usr/edb/pem/bin/configure-pem-server.sh ``` -For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/installing_on_linux/configuring_the_pem_server_on_linux/). +For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/pem_server_inst_linux/configuring_the_pem_server_on_linux/). + +!!! Note + - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. diff --git a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_sles15_x86.mdx b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_sles15_x86.mdx index 74c2c90c851..c5bc25a9a99 100644 --- a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_sles15_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_sles15_x86.mdx @@ -5,7 +5,7 @@ title: Installing Postgres Enterprise Manager server on SLES 15 x86_64 Before you begin the installation process: -1. Review the [prerequisites](/pem/latest/installing_pem_server/installing_on_linux/prerequisites/). +1. Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). 2. Log in as superuser: @@ -51,4 +51,7 @@ zypper -n install edb-pem /usr/edb/pem/bin/configure-pem-server.sh ``` -For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/installing_on_linux/configuring_the_pem_server_on_linux/). +For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/pem_server_inst_linux/configuring_the_pem_server_on_linux/). + +!!! Note + - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. diff --git a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_ubuntu18_x86.mdx b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_ubuntu18_x86.mdx index 55c6f6e8be5..c641149abf5 100644 --- a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_ubuntu18_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_ubuntu18_x86.mdx @@ -5,7 +5,7 @@ title: Installing Postgres Enterprise Manager server on Ubuntu 18.04 x86_64 Before you begin the installation process: -1. Review the [prerequisites](/pem/latest/installing_pem_server/installing_on_linux/prerequisites/). +1. Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). 2. Log in as superuser: @@ -49,4 +49,7 @@ apt-get install edb-pem /usr/edb/pem/bin/configure-pem-server.sh ``` -For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/installing_on_linux/configuring_the_pem_server_on_linux/). +For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/pem_server_inst_linux/configuring_the_pem_server_on_linux/). + +!!! Note + - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. diff --git a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_ubuntu20_x86.mdx b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_ubuntu20_x86.mdx index d4d76362a11..d1d4dd7ce5d 100644 --- a/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_ubuntu20_x86.mdx +++ b/product_docs/docs/pem/8/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/x86_amd64/pem_server_ubuntu20_x86.mdx @@ -5,7 +5,7 @@ title: Installing Postgres Enterprise Manager server on Ubuntu 20.04 x86_64 Before you begin the installation process: -1. Review the [prerequisites](/pem/latest/installing_pem_server/installing_on_linux/prerequisites/). +1. Review the [prerequisites](/pem/latest/installing_pem_server/pem_server_inst_linux/prerequisites/). 2. Log in as superuser: @@ -49,4 +49,7 @@ apt-get install edb-pem /usr/edb/pem/bin/configure-pem-server.sh ``` -For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/installing_on_linux/configuring_the_pem_server_on_linux/). +For more details, see [Configuring the PEM Server on Linux](/pem/latest/installing_pem_server/pem_server_inst_linux/configuring_the_pem_server_on_linux/). + +!!! Note + - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. diff --git a/product_docs/docs/postgres_for_kubernetes/1/bootstrap.mdx b/product_docs/docs/postgres_for_kubernetes/1/bootstrap.mdx index ff801ca872a..b3579c6853e 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/bootstrap.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/bootstrap.mdx @@ -349,7 +349,7 @@ There are two ways to achieve this result in EDB Postgres for Kubernetes: only option available before version 1.8.0). Both recovery methods enable either full recovery (up to the last -available WAL) or up to a [point in time](#point-in-time-recovery). +available WAL) or up to a [point in time](#point-in-time-recovery-pitr). When performing a full recovery, the cluster can also be started in replica mode. diff --git a/product_docs/docs/postgres_for_kubernetes/1/database_import.mdx b/product_docs/docs/postgres_for_kubernetes/1/database_import.mdx index fc638e34fec..fcea6d97ed2 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/database_import.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/database_import.mdx @@ -142,7 +142,8 @@ spec: There are a few things you need to be aware of when using the `microservice` type: - It requires an `externalCluster` that points to an existing PostgreSQL - instance containing the data to import + instance containing the data to import (for more information, please refer to + ["The `externalClusters` section"](bootstrap.md#the-externalclusters-section)) - Traffic must be allowed between the Kubernetes cluster and the `externalCluster` during the operation - Connection to the source database must be granted with the specified user @@ -208,6 +209,7 @@ spec: host: pg96.local user: postgres dbname: postgres + sslmode: require password: name: cluster-pg96-superuser key: password @@ -216,9 +218,12 @@ spec: There are a few things you need to be aware of when using the `monolith` type: - It requires an `externalCluster` that points to an existing PostgreSQL - instance containing the data to import + instance containing the data to import (for more information, please refer to + ["The `externalClusters` section"](bootstrap.md#the-externalclusters-section)) - Traffic must be allowed between the Kubernetes cluster and the `externalCluster` during the operation +- You need to specify `sslmode: disable` in the `connectionParameters` section + if you need to connect to a PostgreSQL instance without SSL - Connection to the source database must be granted with the specified user that needs to run `pg_dump` and retrieve roles information (*superuser* is OK) diff --git a/product_docs/docs/postgres_for_kubernetes/1/faq.mdx b/product_docs/docs/postgres_for_kubernetes/1/faq.mdx index 4b8788450d5..496ab3dcede 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/faq.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/faq.mdx @@ -264,7 +264,7 @@ major version of Postgres is version 14, which ships out of the box: - declarative partitioning for horizontal table partitioning, which is a very well-known technique in the database area to improve vertical scalability on a single instance -- extensibility, with extensions like PostGIS for geographical +- extensibility, with extensions like [PostGIS](postgis.md) for geographical databases - parallel queries for vertical scalability - JSON support, unleashing the multi-model hybrid database for both @@ -359,7 +359,7 @@ spec: The time zone can be verified with: ```console -$ k exec -ti pg-italy-1 -c postgres -- psql -x -c "SHOW timezone" +$ kubectl exec -ti pg-italy-1 -c postgres -- psql -x -c "SHOW timezone" -[ RECORD 1 ]--------- TimeZone | Europe/Rome ``` diff --git a/product_docs/docs/postgres_for_kubernetes/1/index.mdx b/product_docs/docs/postgres_for_kubernetes/1/index.mdx index 7e2b48a1fab..b46acd476df 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/index.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/index.mdx @@ -3,59 +3,60 @@ title: EDB Postgres for Kubernetes originalFilePath: src/index.md indexCards: none navigation: -- rel_notes -- '!commercial_support.mdx' -- '!release_notes*' -- '!e2e.mdx' -- '!supported_releases.mdx' -- "#Getting Started" -- before_you_start -- use_cases -- architecture -- installation_upgrade -- quickstart -- interactive_demo -- "#Configuration" -- postgresql_conf -- operator_conf -- samples -- "#Using" -- bootstrap -- security -- database_import -- instance_manager -- scheduling -- resource_management -- failure_modes -- rolling_update -- replication -- backup_recovery -- storage -- labels_annotations -- monitoring -- logging -- certificates -- ssl_connections -- applications -- connection_pooling -- replica_cluster -- kubernetes_upgrade -- expose_pg_services -- troubleshooting -- fencing -- failover -- e2e -- container_images -- operator_capability_levels -- commercial_support -- faq -- wait_for_apply_queue -- api_reference -- "#Enhanced" -- cnp-plugin -- openshift -- evaluation -- license_keys + - rel_notes + - '!commercial_support.mdx' + - '!release_notes*' + - '!e2e.mdx' + - '!supported_releases.mdx' + - '#Getting Started' + - before_you_start + - use_cases + - architecture + - installation_upgrade + - quickstart + - interactive_demo + - '#Configuration' + - postgresql_conf + - operator_conf + - samples + - '#Using' + - bootstrap + - security + - database_import + - instance_manager + - scheduling + - resource_management + - failure_modes + - rolling_update + - replication + - backup_recovery + - storage + - labels_annotations + - monitoring + - logging + - certificates + - ssl_connections + - applications + - connection_pooling + - replica_cluster + - kubernetes_upgrade + - expose_pg_services + - troubleshooting + - fencing + - failover + - e2e + - container_images + - operator_capability_levels + - commercial_support + - faq + - wait_for_apply_queue + - api_reference + - '#Enhanced' + - cnp-plugin + - openshift + - evaluation + - license_keys + --- The EDB Postgres for Kubernetes operator is a fork based on [CloudNativePG](https://cloudnative-pg.io). It provides additional value such as compatibility with Oracle using EDB Postgres Advanced Server and additional supported platforms such as IBM Power and OpenShift. It is designed, developed, and supported by EDB and covers the full lifecycle of a highly available Postgres database clusters with a primary/standby architecture, using native streaming replication. diff --git a/product_docs/docs/postgres_for_kubernetes/1/operator_capability_levels.mdx b/product_docs/docs/postgres_for_kubernetes/1/operator_capability_levels.mdx index 0bbea10e97f..71dffe165c9 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/operator_capability_levels.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/operator_capability_levels.mdx @@ -230,6 +230,12 @@ connection. Import is from any supported version of Postgres and relies on `pg_dump` and `pg_restore` to be executed from the new cluster primary for all databases part of the operation and, if requested, for roles. +### PostGIS clusters + +EDB Postgres for Kubernetes supports the installation of clusters with the [PostGIS](postgis.md) +open source extension for geographical databases, one of the most popular +extensions for PostgreSQL. + ### Basic LDAP authentication for PostgreSQL The operator allows you to configure LDAP authentication for your PostgreSQL diff --git a/product_docs/docs/postgres_for_kubernetes/1/postgis.mdx b/product_docs/docs/postgres_for_kubernetes/1/postgis.mdx new file mode 100644 index 00000000000..419e33d049e --- /dev/null +++ b/product_docs/docs/postgres_for_kubernetes/1/postgis.mdx @@ -0,0 +1,155 @@ +--- +title: 'PostGIS' +originalFilePath: 'src/postgis.md' +--- + +[PostGIS](https://postgis.net/) is a very popular open source extension +for PostgreSQL that introduces support for storing GIS (Geographic Information +Systems) objects in the database and be queried via SQL. + +!!! Important + This section assumes you are familiar with PostGIS and provides some basic + information about how to create a new PostgreSQL cluster with a PostGIS database + in Kubernetes via EDB Postgres for Kubernetes. + +The CloudNativePG Community maintains container images that are built on top +of the official [PostGIS images hosted on DockerHub](https://hub.docker.com/r/postgis/postgis). +For more information please visit: + +- The [`postgis-containers` project in GitHub](https://github.com/cloudnative-pg/postgis-containers) +- The [`postgis-containers` Container Registry in GitHub](https://github.com/cloudnative-pg/postgis-containers/pkgs/container/postgis) + +Additionally, EDB provides container images for EDB Postgres Advanced Server +that include PostGIS and makes them available in the official +[registry on Quay.io](https://quay.io/repository/enterprisedb/edb-postgres-advanced?tab=tags) +with the `-postgis` suffix. + +## Basic concepts about a PostGIS cluster + +Conceptually, a PostGIS-based PostgreSQL cluster (or simply a PostGIS cluster) +is like any other PostgreSQL cluster. The only differences are: + +- the presence in the system of PostGIS and related libraries +- the presence in the database(s) of the PostGIS extension + +Since EDB Postgres for Kubernetes is based on Immutable Application Containers, the only way +to provision PostGIS is to add it to the container image that you use for the +operand. The ["Container Image Requirements" section](container_images.md) provides +detailed instructions on how this is achieved. More simply, you can just use +the PostGIS container images from the Community, as in the examples below. + +The second step is to install the extension in the PostgreSQL database. You can +do this in two ways: + +- install it in the application database, which is the main and supposedly only + database you host in the cluster according to the microservice architecture, or +- install it in the `template1` database so as to make it available for all the + databases you end up creating in the cluster, in case you adopt the monolith + architecture where the instance is shared by multiple databases + +!!! Info + For more information on the microservice vs monolith architecture in the database + please refer to the ["How many databases should be hosted in a single PostgreSQL instance?" FAQ](faq.md) + or the ["Database import" section](database_import.md). + +## Create a new PostgreSQL cluster with PostGIS + +Let's suppose you want to create a new PostgreSQL 14 cluster with PostGIS 3.2. + +The first step is to ensure you use the right PostGIS container image for the +operand, and properly set the `.spec.imageName` option in the `Cluster` +resource. + +The [`postgis-example.yaml` manifest](../samples/postgis-example.yaml) below +provides some guidance on how the creation of a PostGIS cluster can be done. + +!!! Warning + Please consider that, although convention over configuration applies in + EDB Postgres for Kubernetes, you should spend time configuring and tuning your system for + production. Also the `imageName` in the example below deliberately points + to the latest available image for PostgreSQL 14 - you should use a specific + image name or, preferably, the SHA256 digest for true immutability. + +```yaml +apiVersion: postgresql.k8s.enterprisedb.io/v1 +kind: Cluster +metadata: + name: postgis-example +spec: + instances: 3 + imageName: quay.io/enterprisedb/postgis:14 + bootstrap: + initdb: + postInitTemplateSQL: + - CREATE EXTENSION postgis; + - CREATE EXTENSION postgis_topology; + - CREATE EXTENSION fuzzystrmatch; + - CREATE EXTENSION postgis_tiger_geocoder; + + storage: + size: 1Gi +``` + +The example relies on the `postInitTemplateSQL` option which executes a list of +queries against the `template1` database, before the actual creation of the +application database (called `app`). This means that, once you have applied the +manifest and the cluster is up, you will have the above extensions installed in +both the template database and the application database, ready for use. + +!!! Info + Take some time and look at the available options in `.spec.bootstrap.initdb` + from the [API reference](api_reference.md#BootstrapInitDB), such as + `postInitApplicationSQL`. + +You can easily verify the available version of PostGIS that is in the +container, by connecting to the `app` database (you might obtain different +values from the ones in this document): + +```console +$ kubectl exec -ti postgis-example-1 -- psql app +Defaulted container "postgres" out of: postgres, bootstrap-controller (init) +psql (14.4 (Debian 14.4-1.pgdg110+1)) +Type "help" for help. + +app=# SELECT * FROM pg_available_extensions WHERE name ~ '^postgis' ORDER BY 1; + name | default_version | installed_version | comment +--------------------------+-----------------+-------------------+------------------------------------------------------------ + postgis | 3.2.2 | 3.2.2 | PostGIS geometry and geography spatial types and functions + postgis-3 | 3.2.2 | | PostGIS geometry and geography spatial types and functions + postgis_raster | 3.2.2 | | PostGIS raster types and functions + postgis_raster-3 | 3.2.2 | | PostGIS raster types and functions + postgis_sfcgal | 3.2.2 | | PostGIS SFCGAL functions + postgis_sfcgal-3 | 3.2.2 | | PostGIS SFCGAL functions + postgis_tiger_geocoder | 3.2.2 | 3.2.2 | PostGIS tiger geocoder and reverse geocoder + postgis_tiger_geocoder-3 | 3.2.2 | | PostGIS tiger geocoder and reverse geocoder + postgis_topology | 3.2.2 | 3.2.2 | PostGIS topology spatial types and functions + postgis_topology-3 | 3.2.2 | | PostGIS topology spatial types and functions +(10 rows) +``` + +The next step is to verify that the extensions listed in the +`postInitTemplateSQL` section have been correctly installed in the `app` +database. + +```console +app=# \dx + List of installed extensions + Name | Version | Schema | Description +------------------------+---------+------------+------------------------------------------------------------ + fuzzystrmatch | 1.1 | public | determine similarities and distance between strings + plpgsql | 1.0 | pg_catalog | PL/pgSQL procedural language + postgis | 3.2.2 | public | PostGIS geometry and geography spatial types and functions + postgis_tiger_geocoder | 3.2.2 | tiger | PostGIS tiger geocoder and reverse geocoder + postgis_topology | 3.2.2 | topology | PostGIS topology spatial types and functions +(5 rows) +``` + +Finally: + +```console +app=# SELECT postgis_full_version(); + postgis_full_version +---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- + POSTGIS="3.2.2 628da50" [EXTENSION] PGSQL="140" GEOS="3.9.0-CAPI-1.16.2" PROJ="7.2.1" LIBXML="2.9.10" LIBJSON="0.15" LIBPROTOBUF="1.3.3" WAGYU="0.5.0 (Internal)" TOPOLOGY +(1 row) +``` \ No newline at end of file diff --git a/product_docs/docs/postgres_for_kubernetes/1/quickstart.mdx b/product_docs/docs/postgres_for_kubernetes/1/quickstart.mdx index b418b3d1840..a96ddd576e8 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/quickstart.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/quickstart.mdx @@ -84,27 +84,28 @@ kind create cluster --name pg ### CodeReady Containers (CRC) -1. [Download Red Hat CRC](https://developers.redhat.com/products/codeready-containers/overview) -and move the binary inside a directory in your `PATH`. +1. [Download Red Hat CRC](https://developers.redhat.com/products/codeready-containers/overview) + and move the binary inside a directory in your `PATH`. -1. Run the following commands: +2. Run the following commands: - ``` - crc setup - crc start - ``` + ``` + crc setup + crc start + ``` - The `crc start` output will explain how to proceed. - -1. Execute the output of the `crc oc-env` command. + The `crc start` output will explain how to proceed. + -1. Log in as `kubeadmin` with the printed `oc login` - command. You can also open the web console running `crc console`. - User and password are the same as for the `oc login` command. +3. Execute the output of the `crc oc-env` command. -1. CRC doesn't come with a StorageClass, so one has to be configured. - Follow the [Dynamic volume provisioning wiki page](https://github.com/code-ready/crc/wiki/Dynamic-volume-provisioning) - and install `rancher/local-path-provisioner`. +4. Log in as `kubeadmin` with the printed `oc login` + command. You can also open the web console running `crc console`. + User and password are the same as for the `oc login` command. + +5. CRC doesn't come with a StorageClass, so one has to be configured. + Follow the [Dynamic volume provisioning wiki page](https://github.com/code-ready/crc/wiki/Dynamic-volume-provisioning) + and install `rancher/local-path-provisioner`. ## Part 2 - Install EDB Postgres for Kubernetes diff --git a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_16_rel_notes.mdx b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_16_rel_notes.mdx index f72a4afbdd9..705f1237aa1 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_16_rel_notes.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/rel_notes/1_16_rel_notes.mdx @@ -17,11 +17,45 @@ We are adopting a new policy to support the last two minor versions of the produ As a result, we are introducing the following head versions in the new OLM channels in OpenShift to manage the update streams for EDB Postgres for Kubernetes: -* `fast`: the latest available patch release for the latest available minor release +* `fast`: the latest available patch release for the latest available minor release * `stable-v1.16`: the latest available patch release of the 1.16 minor release * `stable-v1.15`: the latest available patch release of the 1.15 minor release -Prior to this release, the only channel that we were supporting was the `stable` channel. This channel is now obsolete. However, for back compatibility it is currently set as an alias of the `stable-v1.15` channel and it will be removed once version 1.15 goes End of Life. +Prior to this release, the only channel that we were supporting was the `stable` channel. This channel is now obsolete. However, for backward compatibility it is currently set as an alias of the `stable-v1.15` channel. It will be removed once version 1.15 reaches End of Life. +## Important information about upgrading to a 1.16.x operator version on Openshift +We have made a change to the way conditions are represented in the status of +the operator in version 1.16.0 and onward. This change could cause an operator +upgrade to hang on Openshift if one of the old conditions are set during the +upgrade process because of the way the Operator Lifecycle Manager checks new +CRDs against existing CRs. +Prior to installing 1.16.x on Openshift, if you are upgrading from a 1.15.x (or +earlier) version of the operator, we recommend uninstalling the existing +version of the operator, then deleting all of the old conditions out of the +statuses of all existing EDB Postgres for Kubernetes clusters. +This will have no effect on the operability of your existing EDB Postgres for +Kubernetes clusters. + +To remove the existing conditions run: + +```bash +while IFS=' ' read NS CLUSTER; do + kubectl -n ${NS} patch --type='json' ${CLUSTER} --subresource=status -p='[{"op": "remove", "path": "/status/conditions"}]'; +done < <(kubectl get cluster -A --no-headers=true -o jsonpath='{range .items[*]}{.metadata.namespace}{" cluster/"}{.metadata.name}{"\n"}{end}') +``` + +!!! Important + The kubectl command must be version 1.24 or higher. + If you get the output `The request is invalid` it means that the traget cluster + didn't have any condition on it. + +This command will remove all of the conditions from all of the EDB Postgres for +Kubernetes clusters in your Openshift cluster. +Once the command completes, you can safely install version 1.16.x. + +If you have already tried to upgrade to 1.16.x from 1.15.x (or earlier) and +the install of 1.16.x shows as "Pending" and the earlier version shows as +"Cannot update", uninstall both versions of the operator and +run the command that removes the statuses. diff --git a/product_docs/docs/postgres_for_kubernetes/1/samples.mdx b/product_docs/docs/postgres_for_kubernetes/1/samples.mdx index e2b0c83acb0..3892375c90e 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/samples.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/samples.mdx @@ -44,6 +44,10 @@ Full example : [`cluster-example-full.yaml`](../samples/cluster-example-full.yaml): a cluster that sets most of the available options. +PostGIS example +: [`postgis-example.yaml`](../samples/postgis-example.yaml): + an example of "PostGIS cluster" (see the [PostGIS section](postgis.md) for details.) + Replica cluster via streaming : **Prerequisites**: [`cluster-example.yaml`](../samples/cluster-example.yaml) applied and Healthy diff --git a/product_docs/docs/postgres_for_kubernetes/1/samples/cluster-example-initdb-sql-refs.yaml b/product_docs/docs/postgres_for_kubernetes/1/samples/cluster-example-initdb-sql-refs.yaml new file mode 100644 index 00000000000..b853658e570 --- /dev/null +++ b/product_docs/docs/postgres_for_kubernetes/1/samples/cluster-example-initdb-sql-refs.yaml @@ -0,0 +1,47 @@ +apiVersion: v1 +kind: ConfigMap +metadata: + name: post-init-sql-configmap +data: + configmap.sql: | + create table configmaps (i integer); + insert into configmaps (select generate_series(1,10000)); +--- +apiVersion: v1 +kind: Secret +metadata: + name: post-init-sql-secret +stringData: + secret.sql: | + create table secrets (i integer); + insert into secrets (select generate_series(1,10000)); +--- +apiVersion: postgresql.k8s.enterprisedb.io/v1 +kind: Cluster +metadata: + name: cluster-example-initdb +spec: + instances: 3 + + bootstrap: + initdb: + database: appdb + owner: appuser + postInitSQL: + - create table numbers (i integer) + - insert into numbers (select generate_series(1,10000)) + postInitTemplateSQL: + - create extension intarray + postInitApplicationSQL: + - create table application_numbers (i integer) + - insert into application_numbers (select generate_series(1,10000)) + postInitApplicationSQLRefs: + configMapRefs: + - name: post-init-sql-configmap + key: configmap.sql + secretRefs: + - name: post-init-sql-secret + key: secret.sql + + storage: + size: 1Gi diff --git a/product_docs/docs/postgres_for_kubernetes/1/samples/postgis-example.yaml b/product_docs/docs/postgres_for_kubernetes/1/samples/postgis-example.yaml new file mode 100644 index 00000000000..907e4f6b378 --- /dev/null +++ b/product_docs/docs/postgres_for_kubernetes/1/samples/postgis-example.yaml @@ -0,0 +1,17 @@ +apiVersion: postgresql.k8s.enterprisedb.io/v1 +kind: Cluster +metadata: + name: postgis-example +spec: + instances: 3 + imageName: quay.io/enterprisedb/postgis:14 + bootstrap: + initdb: + postInitTemplateSQL: + - CREATE EXTENSION postgis; + - CREATE EXTENSION postgis_topology; + - CREATE EXTENSION fuzzystrmatch; + - CREATE EXTENSION postgis_tiger_geocoder; + + storage: + size: 1Gi diff --git a/product_docs/docs/postgres_for_kubernetes/1/ssl_connections.mdx b/product_docs/docs/postgres_for_kubernetes/1/ssl_connections.mdx index 3407aedfb5f..7bb51ff2019 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/ssl_connections.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/ssl_connections.mdx @@ -86,7 +86,7 @@ spec: app: webtest spec: containers: - - image: quay.io/leonardoce/webtest:1.3.0 + - image: quay.io/enterprisedb/webtest:1.6.0 name: cert-test volumeMounts: - name: secret-volume-root-ca @@ -155,7 +155,7 @@ the `psql` command to connect to this service: ```shell kubectl exec -it cert-test -- bash -c "psql -'sslkey=/etc/secrets/app/tls.key sslcert=/etc/secrets/appuser/tls.crt +'sslkey=/etc/secrets/app/tls.key sslcert=/etc/secrets/app/tls.crt sslrootcert=/etc/secrets/ca/ca.crt host=cluster-example-rw.default.svc dbname=app user=app sslmode=verify-full' -c 'select version();'" ``` diff --git a/product_docs/docs/postgres_for_kubernetes/1/troubleshooting.mdx b/product_docs/docs/postgres_for_kubernetes/1/troubleshooting.mdx index 4ba6deec1b9..76e930ded46 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/troubleshooting.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/troubleshooting.mdx @@ -405,6 +405,17 @@ event to occur instead of relying on the overall cluster health state. Available - LastBackupSucceeded - ContinuousArchiving +- Ready + +`LastBackupSucceeded` is reporting the status of the latest backup. If set to `True` the +last backup has been taken correctly, it is set to `False` otherwise. + +`ContinuousArchiving` is reporting the status of the WAL archiving. If set to `True` the +last WAL archival process has been terminated correctly, it is set to `False` otherwise. + +`Ready` is `True` when the cluster has the number of instances specified by the user +and the primary instance is ready. This condition can be used in scripts to wait for +the cluster to be created. ### How to wait for a particular condition @@ -420,6 +431,12 @@ $ kubectl wait --for=condition=LastBackupSucceeded cluster/ -n -n ``` +- Ready (Cluster is ready or not): + +```bash +$ kubectl wait --for=condition=Ready cluster/ -n +``` + Below is a snippet of a `cluster.status` that contains a failing condition. ```bash @@ -431,14 +448,21 @@ $ kubectl get cluster/ -o yaml conditions: - message: 'unexpected failure invoking barman-cloud-wal-archive: exit status 2' - reason: Continuous Archiving is Failing + reason: ContinuousArchivingFailing status: "False" type: ContinuousArchiving - message: exit status 2 - reason: Backup is failed + reason: LastBackupFailed status: "False" type: LastBackupSucceeded + + - message: Cluster Is Not Ready + reason: ClusterIsNotReady + status: "False" + type: Ready + + ``` ## Some common issues diff --git a/src/styles/_docs.scss b/src/styles/_docs.scss index fe46546f795..3abe4f18798 100644 --- a/src/styles/_docs.scss +++ b/src/styles/_docs.scss @@ -129,6 +129,9 @@ label.link-label { background: #d1d1d1; color: #272822; text-shadow: none; + line-height: normal; + // Google doesn't serve some character ranges for Source Code Pro that we need for legible output, e.g. table listings - so use default + font-family: monospace !important; } } @@ -172,7 +175,6 @@ html.katacoda-panel-active .katacoda-exec-button { } @media print { - .topbar, .sidebar, nav { @@ -262,4 +264,4 @@ html.katacoda-panel-active .katacoda-exec-button { & span:hover { border-bottom: 1px solid grey; } -} \ No newline at end of file +}