Split up internal and external db docs

Author: agrare

_includes/configuration.md

@@ -42,7 +42,8 @@ options for database configuration:
   - Configure the appliance to use an internal PostgreSQL database
   - Configure the appliance to use an external PostgreSQL database
 
-{% include configuration-db.md %}
+{% include internal-configuration-db.md %}
+{% include external-configuration-db.md %}
 
 ### Configure Messaging
 

_includes/external-configuration-db.md

@@ -0,0 +1,56 @@
+#### Configuring an External Database
+
+Based on your setup, you will choose to configure the appliance to use
+an external PostgreSQL database. For example, we can only have one
+database in a single region. However, a region can be segmented into
+multiple zones, such as database zone, user interface zone, and
+reporting zone, where each zone provides a specific function. The
+appliances in these zones must be configured to use an external
+database.
+
+The `postgresql.conf` file used with {{ site.data.product.title_short }} databases requires
+specific settings for correct operation. For example, it must correctly
+reclaim table space, control session timeouts, and format the PostgreSQL
+server log for improved system support. It is recommended that external databases use a
+`postgresql.conf` file based on the standard file used by the
+{{ site.data.product.title_short }} appliance.
+
+Ensure you configure the settings in the `postgresql.conf` to suit your
+system. For example, customize the `shared_buffers` setting according to
+the amount of real storage available in the external system hosting the
+PostgreSQL instance. In addition, depending on the aggregate number of
+appliances expected to connect to the PostgreSQL instance, it may be
+necessary to alter the `max_connections` setting.
+
+**Note:**
+
+  - {{ site.data.product.title_short }} requires PostgreSQL version 10.
+
+  - Because the `postgresql.conf` file controls the operation of all
+    databases managed by a single instance of PostgreSQL, do not mix
+    {{ site.data.product.title_short }} databases with other types of databases in a single
+    PostgreSQL instance.
+
+1.  Start the appliance and open a terminal console.
+
+2.  Enter the `appliance_console` command. The {{ site.data.product.title_short }} appliance
+    summary screen displays.
+
+3.  Press **Enter** to manually configure settings.
+
+4.  Select **Configure Application** from the menu.
+
+5.  Choose **Create Region in External Database** for the database location.
+
+6.  Enter the database hostname or IP address when prompted.
+
+7.  Enter the database name or leave blank for the default
+    (`vmdb_production`).
+
+8.  Enter the database username or leave blank for the default (`root`).
+
+9. Enter the chosen database user’s password.
+
+10. Confirm the configuration if prompted.
+
+{{ site.data.product.title_short }} will then configure the external database.

_includes/configuration-db.md renamed to _includes/internal-configuration-db.md

@@ -34,7 +34,7 @@ disks; installation will fail if the disks are not blank.
         All {{ site.data.product.title_short }} appliances in a multi-region
         deployment must use the same key.
 
-6.  Choose **Create Internal Database** for the database location. 
+6.  Choose **Create Internal Database** for the database location.
 
     In the **Configure Messaging** menu, select **Make No messaging changes**. If you see ```Configuration failed: Internal database require a volume mounted at /var/lib/pgsql. Please add an unpartitioned disk and try again.``` message, then ensure to add a second disk for the database per instructions as defined above.
 
@@ -89,60 +89,3 @@ disks; installation will fail if the disks are not blank.
 {{ site.data.product.title_short }} then configures the internal database. This takes a few
 minutes. After the database is created and initialized, you can log in
 to {{ site.data.product.title_short }}.
-
-#### Configuring an External Database
-
-Based on your setup, you will choose to configure the appliance to use
-an external PostgreSQL database. For example, we can only have one
-database in a single region. However, a region can be segmented into
-multiple zones, such as database zone, user interface zone, and
-reporting zone, where each zone provides a specific function. The
-appliances in these zones must be configured to use an external
-database.
-
-The `postgresql.conf` file used with {{ site.data.product.title_short }} databases requires
-specific settings for correct operation. For example, it must correctly
-reclaim table space, control session timeouts, and format the PostgreSQL
-server log for improved system support. It is recommended that external databases use a
-`postgresql.conf` file based on the standard file used by the
-{{ site.data.product.title_short }} appliance.
-
-Ensure you configure the settings in the `postgresql.conf` to suit your
-system. For example, customize the `shared_buffers` setting according to
-the amount of real storage available in the external system hosting the
-PostgreSQL instance. In addition, depending on the aggregate number of
-appliances expected to connect to the PostgreSQL instance, it may be
-necessary to alter the `max_connections` setting.
-
-**Note:**
-
-  - {{ site.data.product.title_short }} requires PostgreSQL version 10.
-
-  - Because the `postgresql.conf` file controls the operation of all
-    databases managed by a single instance of PostgreSQL, do not mix
-    {{ site.data.product.title_short }} databases with other types of databases in a single
-    PostgreSQL instance.
-
-1.  Start the appliance and open a terminal console.
-
-2.  Enter the `appliance_console` command. The {{ site.data.product.title_short }} appliance
-    summary screen displays.
-
-3.  Press **Enter** to manually configure settings.
-
-4.  Select **Configure Application** from the menu.
-
-5.  Choose **Create Region in External Database** for the database location.
-
-6.  Enter the database hostname or IP address when prompted.
-
-7.  Enter the database name or leave blank for the default
-    (`vmdb_production`).
-
-8.  Enter the database username or leave blank for the default (`root`).
-
-9. Enter the chosen database user’s password.
-
-10. Confirm the configuration if prompted.
-
-{{ site.data.product.title_short }} will then configure the external database.

quickstart_openstack_provider_guide/_topics/configuration-quick.md

@@ -31,7 +31,8 @@ database. For instructions on how to configure an external database
 instead, see [Configuring an External
 Database](https://access.redhat.com/documentation/en/red-hat-cloudforms/4.1/single/installing-red-hat-cloudforms-on-red-hat-enterprise-linux-openstack-platform#configuring_an_external_database).
 
-{% include configuration-db.md %}
+{% include internal-configuration-db.md %}
+{% include external-configuration-db.md %}
 
 ### Configuring General {{ site.data.product.title_short }} Settings