From ed55bba715b67834e8e09dfc8071be5c7cd7ff73 Mon Sep 17 00:00:00 2001 From: asteflova Date: Thu, 12 Dec 2024 13:36:40 +0000 Subject: [PATCH] deploy: a40aed33e898d2e250545d28dab0a999e34a88c5 --- .../index-foreman-deb.html | 49 +- .../index-foreman-el.html | 49 +- .../Administering_Project/index-katello.html | 49 +- .../index-orcharhino.html | 49 +- .../index-satellite.html | 53 +- .../index-foreman-deb.html | 4 +- .../index-foreman-el.html | 4 +- .../index-katello.html | 4 +- .../index-orcharhino.html | 4 +- .../index-satellite.html | 4 +- .../Installing_Proxy/index-foreman-el.html | 9 +- nightly/Installing_Proxy/index-katello.html | 9 +- .../Installing_Proxy/index-orcharhino.html | 9 +- nightly/Installing_Proxy/index-satellite.html | 9 +- nightly/Installing_Server/index-katello.html | 49 +- .../Installing_Server/index-orcharhino.html | 49 +- .../Installing_Server/index-satellite.html | 65 +- .../index-satellite.html | 65 +- nightly/Managing_Content/index-katello.html | 3 +- .../Managing_Content/index-orcharhino.html | 3 +- nightly/Managing_Content/index-satellite.html | 3 +- .../index-foreman-deb.html | 30 +- .../index-foreman-el.html | 30 +- .../index-katello.html | 27 +- .../index-orcharhino.html | 27 +- .../Planning_for_Project/index-katello.html | 730 ++++++++++----- .../index-orcharhino.html | 727 ++++++++++----- .../Planning_for_Project/index-satellite.html | 852 ++++++++++++------ 28 files changed, 2066 insertions(+), 899 deletions(-) diff --git a/nightly/Administering_Project/index-foreman-deb.html b/nightly/Administering_Project/index-foreman-deb.html index 113de6653cd..e3dfa3f390b 100644 --- a/nightly/Administering_Project/index-foreman-deb.html +++ b/nightly/Administering_Project/index-foreman-deb.html @@ -1171,10 +1171,51 @@

3.5. Creating and managing roles

-

Foreman provides a set of predefined roles with permissions sufficient for standard tasks, as listed in Predefined roles available in Foreman. -It is also possible to configure custom roles, and assign one or more permission filters to them. -Permission filters define the actions allowed for a certain resource type. -Certain Foreman plugins create roles automatically.

+

Users in Foreman can have one or more roles assigned. +These roles are associated with permissions that enable users to perform specified administrative actions in Foreman. +Permission filters define the actions allowed for a certain resource type.

+
+
+

Foreman provides a set of predefined roles with permissions sufficient for standard tasks. +For a list of these roles, see Predefined roles available in Foreman. +You can also configure custom roles.

+
+
+ + + + + +
+
Note
+		 +
+

One of the predefined roles is the Default role. +Foreman assigns the Default role to every user in the system. +By default, the Default role grants only a limited set of permissions. +Be aware that if you add a permission to the Default role, every Foreman users will gain that permission. +Assigning a different role to a user does not remove the Default role from the user.

+
+
+
+
+

The following types of roles are commonly defined within various Foreman deployments:

+
+
+
+
Roles related to applications or parts of infrastructure
+
+

For example, roles for owners of Enterprise Linux as the operating system as opposed to roles for owners of application servers and database servers.

+
+
Roles related to a particular stage of the software lifecycle
+
+

For example, roles divided among the development, testing, and production phases, where each phase has one or more owners.

+
+
Roles related to specific tasks
+
+

For example, you can create a role for security managers and a role for license managers, depending on the specific tasks users need to be able to perform within your organization.

+
+

3.5.1. Creating a role

diff --git a/nightly/Administering_Project/index-foreman-el.html b/nightly/Administering_Project/index-foreman-el.html index 122f023faa7..b2dc83b03e0 100644 --- a/nightly/Administering_Project/index-foreman-el.html +++ b/nightly/Administering_Project/index-foreman-el.html @@ -1174,10 +1174,51 @@

3.5. Creating and managing roles

-

Foreman provides a set of predefined roles with permissions sufficient for standard tasks, as listed in Predefined roles available in Foreman. -It is also possible to configure custom roles, and assign one or more permission filters to them. -Permission filters define the actions allowed for a certain resource type. -Certain Foreman plugins create roles automatically.

+

Users in Foreman can have one or more roles assigned. +These roles are associated with permissions that enable users to perform specified administrative actions in Foreman. +Permission filters define the actions allowed for a certain resource type.

+
+
+

Foreman provides a set of predefined roles with permissions sufficient for standard tasks. +For a list of these roles, see Predefined roles available in Foreman. +You can also configure custom roles.

+
+
+ + + + + +
+
Note
+		 +
+

One of the predefined roles is the Default role. +Foreman assigns the Default role to every user in the system. +By default, the Default role grants only a limited set of permissions. +Be aware that if you add a permission to the Default role, every Foreman users will gain that permission. +Assigning a different role to a user does not remove the Default role from the user.

+
+
+
+
+

The following types of roles are commonly defined within various Foreman deployments:

+
+
+
+
Roles related to applications or parts of infrastructure
+
+

For example, roles for owners of Enterprise Linux as the operating system as opposed to roles for owners of application servers and database servers.

+
+
Roles related to a particular stage of the software lifecycle
+
+

For example, roles divided among the development, testing, and production phases, where each phase has one or more owners.

+
+
Roles related to specific tasks
+
+

For example, you can create a role for security managers and a role for license managers, depending on the specific tasks users need to be able to perform within your organization.

+
+

3.5.1. Creating a role

diff --git a/nightly/Administering_Project/index-katello.html b/nightly/Administering_Project/index-katello.html index 4645ac10176..b91c38e0d19 100644 --- a/nightly/Administering_Project/index-katello.html +++ b/nightly/Administering_Project/index-katello.html @@ -1699,10 +1699,51 @@

5.5. Creating and managing roles

-

Foreman provides a set of predefined roles with permissions sufficient for standard tasks, as listed in Predefined roles available in Foreman. -It is also possible to configure custom roles, and assign one or more permission filters to them. -Permission filters define the actions allowed for a certain resource type. -Certain Foreman plugins create roles automatically.

+

Users in Foreman can have one or more roles assigned. +These roles are associated with permissions that enable users to perform specified administrative actions in Foreman. +Permission filters define the actions allowed for a certain resource type.

+
+
+

Foreman provides a set of predefined roles with permissions sufficient for standard tasks. +For a list of these roles, see Predefined roles available in Foreman. +You can also configure custom roles.

+
+
+ + + + + +
+
Note
+		 +
+

One of the predefined roles is the Default role. +Foreman assigns the Default role to every user in the system. +By default, the Default role grants only a limited set of permissions. +Be aware that if you add a permission to the Default role, every Foreman users will gain that permission. +Assigning a different role to a user does not remove the Default role from the user.

+
+
+
+
+

The following types of roles are commonly defined within various Foreman deployments:

+
+
+
+
Roles related to applications or parts of infrastructure
+
+

For example, roles for owners of Enterprise Linux as the operating system as opposed to roles for owners of application servers and database servers.

+
+
Roles related to a particular stage of the software lifecycle
+
+

For example, roles divided among the development, testing, and production phases, where each phase has one or more owners.

+
+
Roles related to specific tasks
+
+

For example, you can create a role for security managers and a role for license managers, depending on the specific tasks users need to be able to perform within your organization.

+
+

5.5.1. Creating a role

diff --git a/nightly/Administering_Project/index-orcharhino.html b/nightly/Administering_Project/index-orcharhino.html index 754c9488c0d..36a41ff04e1 100644 --- a/nightly/Administering_Project/index-orcharhino.html +++ b/nightly/Administering_Project/index-orcharhino.html @@ -1660,10 +1660,51 @@

5.5. Creating and managing roles

-

orcharhino provides a set of predefined roles with permissions sufficient for standard tasks, as listed in Predefined roles available in orcharhino. -It is also possible to configure custom roles, and assign one or more permission filters to them. -Permission filters define the actions allowed for a certain resource type. -Certain orcharhino plugins create roles automatically.

+

Users in orcharhino can have one or more roles assigned. +These roles are associated with permissions that enable users to perform specified administrative actions in orcharhino. +Permission filters define the actions allowed for a certain resource type.

+
+
+

orcharhino provides a set of predefined roles with permissions sufficient for standard tasks. +For a list of these roles, see Predefined roles available in orcharhino. +You can also configure custom roles.

+
+
+ + + + + +
+
Note
+		 +
+

One of the predefined roles is the Default role. +orcharhino assigns the Default role to every user in the system. +By default, the Default role grants only a limited set of permissions. +Be aware that if you add a permission to the Default role, every orcharhino users will gain that permission. +Assigning a different role to a user does not remove the Default role from the user.

+
+
+
+
+

The following types of roles are commonly defined within various orcharhino deployments:

+
+
+
+
Roles related to applications or parts of infrastructure
+
+

For example, roles for owners of Enterprise Linux as the operating system as opposed to roles for owners of application servers and database servers.

+
+
Roles related to a particular stage of the software lifecycle
+
+

For example, roles divided among the development, testing, and production phases, where each phase has one or more owners.

+
+
Roles related to specific tasks
+
+

For example, you can create a role for security managers and a role for license managers, depending on the specific tasks users need to be able to perform within your organization.

+
+

5.5.1. Creating a role

diff --git a/nightly/Administering_Project/index-satellite.html b/nightly/Administering_Project/index-satellite.html index afb3c7bba6a..23768e72597 100644 --- a/nightly/Administering_Project/index-satellite.html +++ b/nightly/Administering_Project/index-satellite.html @@ -1777,6 +1777,10 @@

+

You can structure locations hierarchically by providing a parent location. +Unless otherwise specified, locations inherit the settings from their parent location.

+

7.1. Creating a location

@@ -2557,10 +2561,51 @@

8.5. Creating and managing roles

-

Satellite provides a set of predefined roles with permissions sufficient for standard tasks, as listed in Predefined roles available in Satellite. -It is also possible to configure custom roles, and assign one or more permission filters to them. -Permission filters define the actions allowed for a certain resource type. -Certain Satellite plugins create roles automatically.

+

Users in Satellite can have one or more roles assigned. +These roles are associated with permissions that enable users to perform specified administrative actions in Satellite. +Permission filters define the actions allowed for a certain resource type.

+
+
+

Satellite provides a set of predefined roles with permissions sufficient for standard tasks. +For a list of these roles, see Predefined roles available in Satellite. +You can also configure custom roles.

+
+
+ + + + + +
+
Note
+		 +
+

One of the predefined roles is the Default role. +Satellite assigns the Default role to every user in the system. +By default, the Default role grants only a limited set of permissions. +Be aware that if you add a permission to the Default role, every Satellite users will gain that permission. +Assigning a different role to a user does not remove the Default role from the user.

+
+
+
+
+

The following types of roles are commonly defined within various Satellite deployments:

+
+
+
+
Roles related to applications or parts of infrastructure
+
+

For example, roles for owners of Red Hat Enterprise Linux as the operating system as opposed to roles for owners of application servers and database servers.

+
+
Roles related to a particular stage of the software lifecycle
+
+

For example, roles divided among the development, testing, and production phases, where each phase has one or more owners.

+
+
Roles related to specific tasks
+
+

For example, you can create a role for security managers and a role for license managers, depending on the specific tasks users need to be able to perform within your organization.

+
+

8.5.1. Creating a role

diff --git a/nightly/Configuring_User_Authentication/index-foreman-deb.html b/nightly/Configuring_User_Authentication/index-foreman-deb.html index bbed372ea57..28957df291e 100644 --- a/nightly/Configuring_User_Authentication/index-foreman-deb.html +++ b/nightly/Configuring_User_Authentication/index-foreman-deb.html @@ -217,7 +217,7 @@

Configuring authentication for Foreman users

-

1. Overview of authentication methods in Foreman

+

1. Overview of authentication methods in Foreman

Foreman includes native support for authentication with a username and password. diff --git a/nightly/Configuring_User_Authentication/index-foreman-el.html b/nightly/Configuring_User_Authentication/index-foreman-el.html index 6188f5d7ad5..2c47f8d5596 100644 --- a/nightly/Configuring_User_Authentication/index-foreman-el.html +++ b/nightly/Configuring_User_Authentication/index-foreman-el.html @@ -217,7 +217,7 @@

Configuring authentication for Foreman users

-

1. Overview of authentication methods in Foreman

+

1. Overview of authentication methods in Foreman

Foreman includes native support for authentication with a username and password. diff --git a/nightly/Configuring_User_Authentication/index-katello.html b/nightly/Configuring_User_Authentication/index-katello.html index 5df81e2177a..59648bd1cfb 100644 --- a/nightly/Configuring_User_Authentication/index-katello.html +++ b/nightly/Configuring_User_Authentication/index-katello.html @@ -217,7 +217,7 @@

Configuring authentication for Foreman users

-

1. Overview of authentication methods in Foreman

+

1. Overview of authentication methods in Foreman

Foreman includes native support for authentication with a username and password. diff --git a/nightly/Configuring_User_Authentication/index-orcharhino.html b/nightly/Configuring_User_Authentication/index-orcharhino.html index f8ad3b88393..9df69513e22 100644 --- a/nightly/Configuring_User_Authentication/index-orcharhino.html +++ b/nightly/Configuring_User_Authentication/index-orcharhino.html @@ -217,7 +217,7 @@

Configuring authentication for orcharhino users

-

1. Overview of authentication methods in orcharhino

+

1. Overview of authentication methods in orcharhino

orcharhino includes native support for authentication with a username and password. diff --git a/nightly/Configuring_User_Authentication/index-satellite.html b/nightly/Configuring_User_Authentication/index-satellite.html index 4d9172e1505..43b9144f6ce 100644 --- a/nightly/Configuring_User_Authentication/index-satellite.html +++ b/nightly/Configuring_User_Authentication/index-satellite.html @@ -214,7 +214,7 @@

Configuring authentication for Red Hat Satellite users

Table of Contents
@@ -3094,14 +3094,9 @@

-

Appendix A: Smart Proxy server scalability considerations

+

Appendix A: Smart Proxy server scalability considerations when managing Puppet clients

-

The maximum number of Smart Proxy servers that Foreman server can support has no fixed limit. -It was tested that a Foreman server can support 17 Smart Proxy servers with 2 vCPUs. -However, scalability is highly variable, especially when managing Puppet clients.

-
-

Smart Proxy server scalability when managing Puppet clients depends on the number of CPUs, the run-interval distribution, and the number of Puppet managed resources. Smart Proxy server has a limitation of 100 concurrent Puppet agents running at any single point in time. Running more than 100 concurrent Puppet agents results in a 503 HTTP error.

diff --git a/nightly/Installing_Proxy/index-katello.html b/nightly/Installing_Proxy/index-katello.html index c315608b039..ec8969e40bd 100644 --- a/nightly/Installing_Proxy/index-katello.html +++ b/nightly/Installing_Proxy/index-katello.html @@ -302,7 +302,7 @@

Installing a Smart Proxy Server nightly on Enterprise Linux

  • 7.5. Installing the DNS Infoblox module
    • -
  • Appendix A: Smart Proxy server scalability considerations
    • +
  • Appendix A: Smart Proxy server scalability considerations when managing Puppet clients
  • Appendix B: dhcp_isc settings
  • Appendix C: DHCP options for network configuration
    • @@ -4083,14 +4083,9 @@

    -

    Appendix A: Smart Proxy server scalability considerations

    +

    Appendix A: Smart Proxy server scalability considerations when managing Puppet clients

    -

    The maximum number of Smart Proxy servers that Foreman server can support has no fixed limit. -It was tested that a Foreman server can support 17 Smart Proxy servers with 2 vCPUs. -However, scalability is highly variable, especially when managing Puppet clients.

    -
    -

    Smart Proxy server scalability when managing Puppet clients depends on the number of CPUs, the run-interval distribution, and the number of Puppet managed resources. Smart Proxy server has a limitation of 100 concurrent Puppet agents running at any single point in time. Running more than 100 concurrent Puppet agents results in a 503 HTTP error.

    diff --git a/nightly/Installing_Proxy/index-orcharhino.html b/nightly/Installing_Proxy/index-orcharhino.html index 6efae92f1bf..478a90853b2 100644 --- a/nightly/Installing_Proxy/index-orcharhino.html +++ b/nightly/Installing_Proxy/index-orcharhino.html @@ -291,7 +291,7 @@

    Installing orcharhino Proxy

  • 7.5. Installing the DNS Infoblox module
    • -
  • Appendix A: orcharhino Proxy scalability considerations
    • +
  • Appendix A: orcharhino Proxy scalability considerations when managing Puppet clients
  • Appendix B: dhcp_isc settings
  • Appendix C: DHCP options for network configuration
    • @@ -3201,14 +3201,9 @@

    -

    Appendix A: orcharhino Proxy scalability considerations

    +

    Appendix A: orcharhino Proxy scalability considerations when managing Puppet clients

    -

    The maximum number of orcharhino Proxies that orcharhino Server can support has no fixed limit. -It was tested that a orcharhino Server can support 17 orcharhino Proxies with 2 vCPUs. -However, scalability is highly variable, especially when managing Puppet clients.

    -
    -

    orcharhino Proxy scalability when managing Puppet clients depends on the number of CPUs, the run-interval distribution, and the number of Puppet managed resources. orcharhino Proxy has a limitation of 100 concurrent Puppet agents running at any single point in time. Running more than 100 concurrent Puppet agents results in a 503 HTTP error.

    diff --git a/nightly/Installing_Proxy/index-satellite.html b/nightly/Installing_Proxy/index-satellite.html index 4add4f997c8..1e140e4d538 100644 --- a/nightly/Installing_Proxy/index-satellite.html +++ b/nightly/Installing_Proxy/index-satellite.html @@ -293,7 +293,7 @@

    Installing Capsule Server

  • 7.5. Installing the DNS Infoblox module
    • -
  • Appendix A: Capsule Server scalability considerations
    • +
  • Appendix A: Capsule Server scalability considerations when managing Puppet clients
    • @@ -3946,14 +3946,9 @@

    -

    Appendix A: Capsule Server scalability considerations

    +

    Appendix A: Capsule Server scalability considerations when managing Puppet clients

    -

    The maximum number of Capsule Servers that Satellite Server can support has no fixed limit. -It was tested that a Satellite Server can support 17 Capsule Servers with 2 vCPUs. -However, scalability is highly variable, especially when managing Puppet clients.

    -
    -

    Capsule Server scalability when managing Puppet clients depends on the number of CPUs, the run-interval distribution, and the number of Puppet managed resources. Capsule Server has a limitation of 100 concurrent Puppet agents running at any single point in time. Running more than 100 concurrent Puppet agents results in a 503 HTTP error.

    diff --git a/nightly/Installing_Server/index-katello.html b/nightly/Installing_Server/index-katello.html index 152ae7ce802..76ab782126b 100644 --- a/nightly/Installing_Server/index-katello.html +++ b/nightly/Installing_Server/index-katello.html @@ -292,10 +292,11 @@

    Installing Foreman Server with Katello nightly plugin on Enterprise Lin
  • 4.9. Resetting SSL certificate to default self-signed certificate on Foreman server
  • 4.10. Using external databases with Foreman
    • @@ -2897,30 +2898,40 @@

    4.10. Using external databases with Foreman

    -

    As part of the installation process for Foreman, the foreman-installer command installs PostgreSQL databases on the same server as Foreman. +

    The Foreman installation process includes installing a PostgreSQL database on the same host as Foreman server. In certain Foreman deployments, using external databases instead of the default local databases can help with the server load.

    +
    +

    4.10.1. Configuring Foreman server with external database

    -

    To create and use external databases for Foreman, you must complete the following procedures:

    +

    Running the foreman-installer command, used to install a Foreman server, also installs PostgreSQL databases on the server. +However, you can configure your Foreman server to use external databases instead. +Moving to external databases distributes the workload and can reduce overall Foreman memory usage.

    -
    -
      +
      +

      Consider using external databases if you plan to use your Foreman deployment for the following scenarios:

      +
      +
      +
      • -

        Preparing a host for external databases. -Prepare a host for the external databases.

        +

        Frequent remote execution tasks. +This requires a high volume of records in PostgreSQL and generates heavy database workloads.

      • -

        Installing PostgreSQL. -Prepare PostgreSQL with databases for Foreman, Candlepin and Pulp with dedicated users owning them.

        +

        High disk I/O workloads from frequent repository synchronization or content view publishing. +This requires Foreman to create a record in PostgreSQL for each job.

      • -

        Configuring Foreman server to use external databases. -Edit the parameters of foreman-installer to point to the new databases, and run foreman-installer.

        +

        High volume of hosts.

        • -
    +
  • +

    High volume of synchronized content.

    +
    • + +
    -

    4.10.1. PostgreSQL as an external database considerations

    +

    4.10.2. PostgreSQL as an external database considerations

    Foreman, Katello, and Candlepin use the PostgreSQL database. If you want to use PostgreSQL as an external database, the following information can help you decide if this option is right for your Foreman configuration. @@ -2959,7 +2970,7 @@

    -

    4.10.2. Preparing a host for external databases

    +

    4.10.3. Preparing a host for external databases

    Install a freshly provisioned system with the latest Enterprise Linux 9 to host the external databases.

    @@ -3000,7 +3011,7 @@

    -

    4.10.3. Installing PostgreSQL

    +

    4.10.4. Installing PostgreSQL

    You can install only the same version of PostgreSQL that is installed with the foreman-installer tool during an internal database installation. Foreman supports PostgreSQL version 12.

    @@ -3173,7 +3184,7 @@

    -

    4.10.4. Configuring Foreman server to use external databases

    +

    4.10.5. Configuring Foreman server to use external databases

    Use the foreman-installer command to configure Foreman to connect to an external PostgreSQL database.

    diff --git a/nightly/Installing_Server/index-orcharhino.html b/nightly/Installing_Server/index-orcharhino.html index b3da7059828..c2643e35d8e 100644 --- a/nightly/Installing_Server/index-orcharhino.html +++ b/nightly/Installing_Server/index-orcharhino.html @@ -291,10 +291,11 @@

    Installing orcharhino Server

  • 4.9. Resetting custom SSL certificate to default self-signed certificate on orcharhino Server
  • 4.10. Using external databases with orcharhino
    • @@ -2635,30 +2636,40 @@

    4.10. Using external databases with orcharhino

    -

    As part of the installation process for orcharhino, the foreman-installer command installs PostgreSQL databases on the same server as orcharhino. +

    The orcharhino installation process includes installing a PostgreSQL database on the same host as orcharhino Server. In certain orcharhino deployments, using external databases instead of the default local databases can help with the server load.

    +
    +

    4.10.1. Configuring orcharhino Server with external database

    -

    To create and use external databases for orcharhino, you must complete the following procedures:

    +

    Running the foreman-installer command, used to install a orcharhino Server, also installs PostgreSQL databases on the server. +However, you can configure your orcharhino Server to use external databases instead. +Moving to external databases distributes the workload and can reduce overall orcharhino memory usage.

    -
    -
      +
      +

      Consider using external databases if you plan to use your orcharhino deployment for the following scenarios:

      +
      +
      +
      • -

        Preparing a host for external databases. -Prepare a host for the external databases.

        +

        Frequent remote execution tasks. +This requires a high volume of records in PostgreSQL and generates heavy database workloads.

      • -

        Installing PostgreSQL. -Prepare PostgreSQL with databases for orcharhino, Candlepin and Pulp with dedicated users owning them.

        +

        High disk I/O workloads from frequent repository synchronization or content view publishing. +This requires orcharhino to create a record in PostgreSQL for each job.

      • -

        Configuring orcharhino Server to use external databases. -Edit the parameters of foreman-installer to point to the new databases, and run foreman-installer.

        +

        High volume of hosts.

        • -
    +
  • +

    High volume of synchronized content.

    +
    • + +
    -

    4.10.1. PostgreSQL as an external database considerations

    +

    4.10.2. PostgreSQL as an external database considerations

    Foreman, Katello, and Candlepin use the PostgreSQL database. If you want to use PostgreSQL as an external database, the following information can help you decide if this option is right for your orcharhino configuration. @@ -2697,7 +2708,7 @@

    -

    4.10.2. Preparing a host for external databases

    +

    4.10.3. Preparing a host for external databases

    Install a freshly provisioned system with the latest Enterprise Linux 9 to host the external databases.

    @@ -2715,7 +2726,7 @@

    -

    4.10.3. Installing PostgreSQL

    +

    4.10.4. Installing PostgreSQL

    You can install only the same version of PostgreSQL that is installed with the foreman-installer tool during an internal database installation. orcharhino supports PostgreSQL version 12.

    @@ -2885,7 +2896,7 @@

    -

    4.10.4. Configuring orcharhino Server to use external databases

    +

    4.10.5. Configuring orcharhino Server to use external databases

    Use the foreman-installer command to configure orcharhino to connect to an external PostgreSQL database.

    diff --git a/nightly/Installing_Server/index-satellite.html b/nightly/Installing_Server/index-satellite.html index e19b9e5c3df..75194152a67 100644 --- a/nightly/Installing_Server/index-satellite.html +++ b/nightly/Installing_Server/index-satellite.html @@ -298,10 +298,11 @@

    Installing Satellite Server in a connected network environment

  • 4.12. Resetting custom SSL certificate to default self-signed certificate on Satellite Server
  • 4.13. Using external databases with Satellite
    • @@ -3166,35 +3167,55 @@

    4.13. Using external databases with Satellite

    -

    As part of the installation process for Red Hat Satellite, the satellite-installer command installs PostgreSQL databases on the same server as Satellite. +

    The Satellite installation process includes installing a PostgreSQL database on the same host as Satellite Server. In certain Satellite deployments, using external databases instead of the default local databases can help with the server load.

    +
    +

    4.13.1. Configuring Satellite Server with external database

    -

    Red Hat does not provide support or tools for external database maintenance. -This includes backups, upgrades, and database tuning. -You must have your own database administrator to support and maintain external databases.

    +

    Running the satellite-installer command, used to install a Satellite Server, also installs PostgreSQL databases on the server. +However, you can configure your Satellite Server to use external databases instead. +Moving to external databases distributes the workload and can reduce overall Satellite memory usage.

    +
    + + + + + +
    +
    Note
    +
    -

    To create and use external databases for Satellite, you must complete the following procedures:

    +

    Red Hat does not provide support or tools for external database maintenance. +If you deploy Satellite with external databases, you will need to support and maintain the external databases yourself.

    -
    -
      +
    +
    +
    +

    Consider using external databases if you plan to use your Satellite deployment for the following scenarios:

    +
    +
    +
    • -

      Preparing a host for external databases. -Prepare a host for the external databases.

      +

      Frequent remote execution tasks. +This requires a high volume of records in PostgreSQL and generates heavy database workloads.

    • -

      Installing PostgreSQL. -Prepare PostgreSQL with databases for Satellite, Candlepin and Pulp with dedicated users owning them.

      +

      High disk I/O workloads from frequent repository synchronization or content view publishing. +This requires Satellite to create a record in PostgreSQL for each job.

    • -

      Configuring Satellite Server to use external databases. -Edit the parameters of satellite-installer to point to the new databases, and run satellite-installer.

      +

      High volume of hosts.

      • - +
    • +

      High volume of synchronized content.

      +
      • +
    +
    -

    4.13.1. PostgreSQL as an external database considerations

    +

    4.13.2. PostgreSQL as an external database considerations

    Foreman, Katello, and Candlepin use the PostgreSQL database. If you want to use PostgreSQL as an external database, the following information can help you decide if this option is right for your Satellite configuration. @@ -3238,7 +3259,7 @@

    -

    4.13.2. Preparing a host for external databases

    +

    4.13.3. Preparing a host for external databases

    Install a freshly provisioned system with the latest Red Hat Enterprise Linux 9 to host the external databases.

    @@ -3298,7 +3319,7 @@

    -

    4.13.3. Installing PostgreSQL

    +

    4.13.4. Installing PostgreSQL

    You can install only the same version of PostgreSQL that is installed with the satellite-installer tool during an internal database installation. Satellite supports PostgreSQL version 12.

    @@ -3468,7 +3489,7 @@

    -

    4.13.4. Configuring Satellite Server to use external databases

    +

    4.13.5. Configuring Satellite Server to use external databases

    Use the satellite-installer command to configure Satellite to connect to an external PostgreSQL database.

    diff --git a/nightly/Installing_Server_Disconnected/index-satellite.html b/nightly/Installing_Server_Disconnected/index-satellite.html index 04f63f24915..5a4c7fc1d48 100644 --- a/nightly/Installing_Server_Disconnected/index-satellite.html +++ b/nightly/Installing_Server_Disconnected/index-satellite.html @@ -276,10 +276,11 @@

    Installing Satellite Server in a disconnected network environment

  • 3.8. Using external databases with Satellite
    • @@ -3040,35 +3041,55 @@

    3.8. Using external databases with Satellite

    -

    As part of the installation process for Red Hat Satellite, the satellite-installer command installs PostgreSQL databases on the same server as Satellite. +

    The Satellite installation process includes installing a PostgreSQL database on the same host as Satellite Server. In certain Satellite deployments, using external databases instead of the default local databases can help with the server load.

    +
    +

    3.8.1. Configuring Satellite Server with external database

    -

    Red Hat does not provide support or tools for external database maintenance. -This includes backups, upgrades, and database tuning. -You must have your own database administrator to support and maintain external databases.

    +

    Running the satellite-installer command, used to install a Satellite Server, also installs PostgreSQL databases on the server. +However, you can configure your Satellite Server to use external databases instead. +Moving to external databases distributes the workload and can reduce overall Satellite memory usage.

    +
    + + + + + +
    +
    Note
    +
    -

    To create and use external databases for Satellite, you must complete the following procedures:

    +

    Red Hat does not provide support or tools for external database maintenance. +If you deploy Satellite with external databases, you will need to support and maintain the external databases yourself.

    -
    -
      +
    +
    +
    +

    Consider using external databases if you plan to use your Satellite deployment for the following scenarios:

    +
    +
    +
    • -

      Preparing a host for external databases. -Prepare a host for the external databases.

      +

      Frequent remote execution tasks. +This requires a high volume of records in PostgreSQL and generates heavy database workloads.

    • -

      Installing PostgreSQL. -Prepare PostgreSQL with databases for Satellite, Candlepin and Pulp with dedicated users owning them.

      +

      High disk I/O workloads from frequent repository synchronization or content view publishing. +This requires Satellite to create a record in PostgreSQL for each job.

    • -

      Configuring Satellite Server to use external databases. -Edit the parameters of satellite-installer to point to the new databases, and run satellite-installer.

      +

      High volume of hosts.

      • - +
    • +

      High volume of synchronized content.

      +
      • +
    +
    -

    3.8.1. PostgreSQL as an external database considerations

    +

    3.8.2. PostgreSQL as an external database considerations

    Foreman, Katello, and Candlepin use the PostgreSQL database. If you want to use PostgreSQL as an external database, the following information can help you decide if this option is right for your Satellite configuration. @@ -3112,7 +3133,7 @@

    -

    3.8.2. Preparing a host for external databases

    +

    3.8.3. Preparing a host for external databases

    Install a freshly provisioned system with the latest Red Hat Enterprise Linux 9 to host the external databases.

    @@ -3172,7 +3193,7 @@

    -

    3.8.3. Installing PostgreSQL

    +

    3.8.4. Installing PostgreSQL

    You can install only the same version of PostgreSQL that is installed with the satellite-installer tool during an internal database installation. Satellite supports PostgreSQL version 12.

    @@ -3342,7 +3363,7 @@

    -

    3.8.4. Configuring Satellite Server to use external databases

    +

    3.8.5. Configuring Satellite Server to use external databases

    Use the satellite-installer command to configure Satellite to connect to an external PostgreSQL database.

    diff --git a/nightly/Managing_Content/index-katello.html b/nightly/Managing_Content/index-katello.html index 9b5c7474328..8c68be64ae1 100644 --- a/nightly/Managing_Content/index-katello.html +++ b/nightly/Managing_Content/index-katello.html @@ -535,7 +535,8 @@

    1.1. Content types in Foreman

    -

    With Foreman, you can import and manage many content types.

    +

    With Foreman, you can import and manage many content types. +You can use content from Red Hat as well as from Canonical, Oracle, SUSE, and other custom content.

    For example, Foreman supports the following content types:

    diff --git a/nightly/Managing_Content/index-orcharhino.html b/nightly/Managing_Content/index-orcharhino.html index e4d3ea6f958..27a3387b876 100644 --- a/nightly/Managing_Content/index-orcharhino.html +++ b/nightly/Managing_Content/index-orcharhino.html @@ -509,7 +509,8 @@

    1.1. Content types in orcharhino

    -

    With orcharhino, you can import and manage many content types.

    +

    With orcharhino, you can import and manage many content types. +You can use content from Red Hat as well as from Canonical, Oracle, SUSE, and other custom content.

    For example, orcharhino supports the following content types:

    diff --git a/nightly/Managing_Content/index-satellite.html b/nightly/Managing_Content/index-satellite.html index bed97fcac21..d10526e2b29 100644 --- a/nightly/Managing_Content/index-satellite.html +++ b/nightly/Managing_Content/index-satellite.html @@ -470,7 +470,8 @@

    1.1. Content types in Red Hat Satellite

    -

    With Red Hat Satellite, you can import and manage many content types.

    +

    With Red Hat Satellite, you can import and manage many content types. +You can use Red Hat content as well as custom content and organize it into Satellite products.

    For example, Satellite supports the following content types:

    diff --git a/nightly/Managing_Organizations_and_Locations/index-foreman-deb.html b/nightly/Managing_Organizations_and_Locations/index-foreman-deb.html index ba334f48977..4b1ab082d94 100644 --- a/nightly/Managing_Organizations_and_Locations/index-foreman-deb.html +++ b/nightly/Managing_Organizations_and_Locations/index-foreman-deb.html @@ -217,7 +217,7 @@

    Managing organizations and locations in Foreman

    -

    1. Introduction to organization and location context in Foreman

    +

    1. Planning organization and location context

    -

    Context in Foreman consists of Organizations and Locations.

    +

    Context in Foreman consists of organizations and locations. +You can associate most resources, for example hosts, subnets, and domains, with at least one organization and location context.

    -

    Most resources in Foreman are associated with at least one organization and location context. -Since resources and users can generally only access resources within their own context, organizations and locations are an integral part of Foreman’s user management.

    +

    Resources and users can generally only access resources within their own context, which makes configuring organizations and locations an integral part of access management in Foreman.

    -
    -

    You can structure locations hierarchically by providing a parent location. -Unless otherwise specified, sub locations inherit the settings from their parent location.

    -
    -
    +
    -
    Caution
    +
    Important
    -

    If you use host groups to bundle provisioning and configuration information, ensure to not mismatch resources from mutually exclusive contexts. +

    If you use host groups to bundle provisioning and configuration information, avoid mismatching resources from mutually exclusive contexts. For example, setting a subnet from one organization or location and a compute resource from a different organization or location creates an invalid host group.

    -
    -

    Some resources in Foreman, such as Ansible roles and operating systems, are not part of any organization or location context.

    -
    +
    +

    Some resources in Foreman, such as Ansible roles and operating systems, are not part of any organization or location context.

    +
    @@ -461,6 +457,10 @@

    +
    +

    You can structure locations hierarchically by providing a parent location. +Unless otherwise specified, locations inherit the settings from their parent location.

    +

    3.1. Creating a location

    diff --git a/nightly/Managing_Organizations_and_Locations/index-foreman-el.html b/nightly/Managing_Organizations_and_Locations/index-foreman-el.html index ba334f48977..4b1ab082d94 100644 --- a/nightly/Managing_Organizations_and_Locations/index-foreman-el.html +++ b/nightly/Managing_Organizations_and_Locations/index-foreman-el.html @@ -217,7 +217,7 @@

    Managing organizations and locations in Foreman

    -

    1. Introduction to organization and location context in Foreman

    +

    1. Planning organization and location context

    -

    Context in Foreman consists of Organizations and Locations.

    +

    Context in Foreman consists of organizations and locations. +You can associate most resources, for example hosts, subnets, and domains, with at least one organization and location context.

    -

    Most resources in Foreman are associated with at least one organization and location context. -Since resources and users can generally only access resources within their own context, organizations and locations are an integral part of Foreman’s user management.

    +

    Resources and users can generally only access resources within their own context, which makes configuring organizations and locations an integral part of access management in Foreman.

    -
    -

    You can structure locations hierarchically by providing a parent location. -Unless otherwise specified, sub locations inherit the settings from their parent location.

    -
    -
    +
    -
    Caution
    +
    Important
    -

    If you use host groups to bundle provisioning and configuration information, ensure to not mismatch resources from mutually exclusive contexts. +

    If you use host groups to bundle provisioning and configuration information, avoid mismatching resources from mutually exclusive contexts. For example, setting a subnet from one organization or location and a compute resource from a different organization or location creates an invalid host group.

    -
    -

    Some resources in Foreman, such as Ansible roles and operating systems, are not part of any organization or location context.

    -
    +
    +

    Some resources in Foreman, such as Ansible roles and operating systems, are not part of any organization or location context.

    +
    @@ -461,6 +457,10 @@

    +
    +

    You can structure locations hierarchically by providing a parent location. +Unless otherwise specified, locations inherit the settings from their parent location.

    +

    3.1. Creating a location

    diff --git a/nightly/Managing_Organizations_and_Locations/index-katello.html b/nightly/Managing_Organizations_and_Locations/index-katello.html index 47c41921f82..e27088415c9 100644 --- a/nightly/Managing_Organizations_and_Locations/index-katello.html +++ b/nightly/Managing_Organizations_and_Locations/index-katello.html @@ -217,7 +217,7 @@

    Managing organizations and locations in Foreman

    -

    1. Introduction to organization and location context in Foreman

    +

    1. Planning organization and location context

    -

    Context in Foreman consists of Organizations and Locations.

    +

    Context in Foreman consists of organizations and locations. +You can associate most resources, for example hosts, subnets, and domains, with at least one organization and location context.

    -

    Most resources in Foreman are associated with at least one organization and location context. -Since resources and users can generally only access resources within their own context, organizations and locations are an integral part of Foreman’s user management.

    +

    Resources and users can generally only access resources within their own context, which makes configuring organizations and locations an integral part of access management in Foreman.

    -
    -

    You can structure locations hierarchically by providing a parent location. -Unless otherwise specified, sub locations inherit the settings from their parent location.

    -
    -
    +
    -
    Caution
    +
    Important
    -

    If you use host groups to bundle provisioning and configuration information, ensure to not mismatch resources from mutually exclusive contexts. +

    If you use host groups to bundle provisioning and configuration information, avoid mismatching resources from mutually exclusive contexts. For example, setting a subnet from one organization or location and a compute resource from a different organization or location creates an invalid host group.

    -
    -

    Some resources in Foreman, such as Ansible roles and operating systems, are not part of any organization or location context.

    -
    @@ -582,6 +575,10 @@

    +
    +

    You can structure locations hierarchically by providing a parent location. +Unless otherwise specified, locations inherit the settings from their parent location.

    +

    3.1. Creating a location

    diff --git a/nightly/Managing_Organizations_and_Locations/index-orcharhino.html b/nightly/Managing_Organizations_and_Locations/index-orcharhino.html index 15eec809a92..8f9ad953376 100644 --- a/nightly/Managing_Organizations_and_Locations/index-orcharhino.html +++ b/nightly/Managing_Organizations_and_Locations/index-orcharhino.html @@ -217,7 +217,7 @@

    Managing organizations and locations in orcharhino

    -

    1. Introduction to organization and location context in orcharhino

    +

    1. Planning organization and location context

    -

    Context in orcharhino consists of Organizations and Locations.

    +

    Context in orcharhino consists of organizations and locations. +You can associate most resources, for example hosts, subnets, and domains, with at least one organization and location context.

    -

    Most resources in orcharhino are associated with at least one organization and location context. -Since resources and users can generally only access resources within their own context, organizations and locations are an integral part of orcharhino’s user management.

    +

    Resources and users can generally only access resources within their own context, which makes configuring organizations and locations an integral part of access management in orcharhino.

    -
    -

    You can structure locations hierarchically by providing a parent location. -Unless otherwise specified, sub locations inherit the settings from their parent location.

    -
    -
    +
    -
    Caution
    +
    Important
    -

    If you use host groups to bundle provisioning and configuration information, ensure to not mismatch resources from mutually exclusive contexts. +

    If you use host groups to bundle provisioning and configuration information, avoid mismatching resources from mutually exclusive contexts. For example, setting a subnet from one organization or location and a compute resource from a different organization or location creates an invalid host group.

    -
    -

    Some resources in orcharhino, such as Ansible roles and operating systems, are not part of any organization or location context.

    -
    @@ -580,6 +573,10 @@

    +
    +

    You can structure locations hierarchically by providing a parent location. +Unless otherwise specified, locations inherit the settings from their parent location.

    +

    3.1. Creating a location

    diff --git a/nightly/Planning_for_Project/index-katello.html b/nightly/Planning_for_Project/index-katello.html index ccafeb95651..8f21ca0c1b1 100644 --- a/nightly/Planning_for_Project/index-katello.html +++ b/nightly/Planning_for_Project/index-katello.html @@ -225,8 +225,7 @@

    Planning for Foreman

  • 1.2. Content views in Foreman
  • 1.3. Lifecycle environments and environment paths
  • 1.4. Content types in Foreman
    • -
  • 1.5. Sources of content in Foreman
    • -
  • 1.6. Additional resources
    • +
  • 1.5. Additional resources
  • 2. Provisioning management with Foreman @@ -274,24 +273,36 @@

    Planning for Foreman

  • Foreman deployment planning