Skip to content

Update references to "Configure Network" or "Set Hostname" #1784

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update references to "Configure Network" or "Set Hostname" #1784

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
39 changes: 15 additions & 24 deletions _includes/configuration-advanced.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,75 +13,66 @@ configuration of the appliance:
<td><p>Description</p></td>
</tr>
<tr class="even">
<td><p><strong>Configure Network</strong></p></td>
<td><p>Provides options for configuring the network for your {{ site.data.product.title_short }} appliance. The appliance is initially configured as a DHCP client with bridged networking.</p>
<p>You can use DHCP to obtain the IP address and network configuration for your {{ site.data.product.title_short }} appliance, or use an IPv4 or IPv6 static network configuration by providing specific IP address and network settings.</p>
<p>This menu also provides options to test the network configuration to check that name resolution is working correctly, and to set the appliance’s host name.</p>
<div class="important">
<p>A valid fully qualified hostname for the {{ site.data.product.title_short }} appliance is required for SmartState analysis to work correctly.</p>
</div></td>
</tr>
<tr class="odd">
<td><p><strong>Restore Database from Backup</strong></p></td>
<td><p>Restore the Virtual Management Database (VMDB) from a previous backup.</p></td>
</tr>
<tr class="even">
<tr class="odd">
<td><p><strong>Configure Application</strong></p></td>
<td><p>Configure the VMDB and Kafka. Use this option to configure the database and messaging for the appliance after installing and running it for the first time.</p></td>
</tr>
<tr class="odd">
<tr class="even">
<td><p><strong>Configure Database Replication</strong></p></td>
<td><p>Configure a primary or standby server for VMDB replication.</p></td>
</tr>
<tr class="even">
<tr class="odd">
<td><p><strong>Logfile Configuration</strong></p></td>
<td><p>Provides options for configuring a new logfile disk volume, and changing the saved logrotate count.</p></td>
</tr>
<tr class="odd">
<tr class="even">
<td><p><strong>Configure Application Database Failover Monitor</strong></p></td>
<td><p>Start or stop VMDB failover monitoring.</p></td>
</tr>
<tr class="even">
<tr class="odd">
<td><p><strong>Extend Temporary Storage</strong></p></td>
<td><p>Add temporary storage to the appliance. The appliance formats an unpartitioned disk attached to the appliance host and mounts it at <code>/var/www/miq_tmp</code>. The appliance uses this temporary storage directory to perform certain image download functions.</p></td>
</tr>
<tr class="odd">
<tr class="even">
<td><p><strong>Configure External Authentication (httpd)</strong></p></td>
<td><p>Configure authentication through an IPA server.</p></td>
</tr>
<tr class="even">
<tr class="odd">
<td><p><strong>Update External Authentication Options</strong></p></td>
<td><p>Enable or disable external authentication methods: single sign-on, SAML, and local login. For example, if the current state is <code>Enabled</code>, the prompt indicates the option should be <code>Disabled</code>.</p></td>
</tr>
<tr class="odd">
<tr class="even">
<td><p><strong>Generate Custom Encryption Key</strong></p></td>
<td><p>Regenerate the encryption key used to encode plain text password.</p></td>
</tr>
<tr class="even">
<tr class="odd">
<td><p><strong>Harden Appliance Using SCAP Configuration</strong></p></td>
<td><p>Apply Security Content Automation Protocol (SCAP) standards to the appliance. You can view these SCAP rules in the <code>/var/www/miq/lib/appliance_console/config/scap_rules.yml</code> file.</p></td>
</tr>
<tr class="odd">
<tr class="even">
<td><p><strong>Stop EVM Server Processes</strong></p></td>
<td><p>Stop all server processes. You may need to do this to perform maintenance.</p></td>
</tr>
<tr class="even">
<tr class="odd">
<td><p><strong>Start EVM Server Processes</strong></p></td>
<td><p>Start the server. You may need to do this after performing maintenance.</p></td>
</tr>
<tr class="odd">
<tr class="even">
<td><p><strong>Restart Appliance</strong></p></td>
<td><p>Restart the {{ site.data.product.title_short }} appliance. You can either restart the appliance and clear the logs or just restart the appliance.</p></td>
</tr>
<tr class="even">
<tr class="odd">
<td><p><strong>Shut Down Appliance</strong></p></td>
<td><p>Power down the appliance and exit all processes.</p></td>
</tr>
<tr class="odd">
<tr class="even">
<td><p><strong>Summary Information</strong></p></td>
<td><p>Go back to the network summary screen for the {{ site.data.product.title_short }} appliance.</p></td>
</tr>
<tr class="even">
<tr class="odd">
<td><p><strong>Quit</strong></p></td>
<td><p>Leave the {{ site.data.product.title_short }} appliance console.</p></td>
</tr>
Expand Down
75 changes: 21 additions & 54 deletions high_availability_guide/_topics/installation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,14 +18,8 @@ the non-database {{ site.data.product.title_short }} appliances.
`/etc/chrony.conf` with valid NTP server information.

3. From your host environment, open the appliance and configure the
network:

1. Log in to the appliance and run the `appliance_console` command
to access the appliance console menu.

2. Configure networking as desired by selecting the **Set DHCP
Network Configuration** or **Set Static Network Configuration**
option.
network and hostname using nmcli or nmtui from the console or from your
web browser using Cockpit on port 9090

4. Resynchronize time information across the appliances:

Expand All @@ -34,21 +28,19 @@ the non-database {{ site.data.product.title_short }} appliances.

5. In the appliance console, configure the following:

1. Configure the hostname by selecting **Set Hostname**.
1. Select **Configure Application**.

2. Select **Configure Application**.

3. Select **Create key** to create the encryption key. You can
2. Select **Create key** to create the encryption key. You can
create a new key, or use an existing key on your system by
selecting **Fetch key from remote machine** and following the
prompts.

4. Select **Create Internal Database**.
3. Select **Create Internal Database**.

5. Select the database disk. {{ site.data.product.title_short }} then activates
4. Select the database disk. {{ site.data.product.title_short }} then activates
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be Select database disk.

the configuration.

6. For **Should this appliance run as a standalone database
5. For **Should this appliance run as a standalone database
server?**, select `y`. Selecting this option configures this
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Select y should be:

Select y.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are there more of these? It feels like they should be in a different PR since it's unrelated to the changes made here.

appliance as a database-only appliance, and therefore the
{{ site.data.product.title_abbr_uc }} application and `evmserverd` processes
Expand All @@ -59,7 +51,7 @@ the non-database {{ site.data.product.title_short }} appliances.

This configuration is not reversible.

7. Create the database password.
6. Create the database password.

**Note:**

Expand Down Expand Up @@ -104,14 +96,8 @@ and secondary database-only appliances can be configured.
`/etc/chrony.conf` with valid NTP server information.

3. From your host environment, open the appliance and configure the
network:

1. Log in to the appliance and run the `appliance_console` command
to access the appliance console menu.

2. Configure networking as desired by selecting the **Set DHCP
Network Configuration** or **Set Static Network Configuration**
option.
network and hostname using nmcli or nmtui from the console or from your
web browser using Cockpit on port 9090

4. Re-synchronize time information across the appliances:

Expand All @@ -120,11 +106,9 @@ and secondary database-only appliances can be configured.

5. In the appliance console, configure the following:

1. Configure the hostname by selecting **Set Hostname**.

2. Select **Configure Application**.
1. Select **Configure Application**.

3. Configure this appliance to use the encryption key from the
2. Configure this appliance to use the encryption key from the
primary database-only appliance:

1. For **Encryption Key**, select **Fetch key from remote
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fetch key from remote should be in **.

This should be select Fetch key from remote.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@qahmed1998 I think all of these changes are "wrong" to start with. I'm wondering if we should have these changes done afterwards.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ignore my comment for fetch key from remote. This is fine.

Expand All @@ -146,7 +130,7 @@ and secondary database-only appliances can be configured.

</div>

4. Configure the database:
3. Configure the database:

1. Select **Create Region in External Database**, since the
database is external to the appliances.
Expand All @@ -164,7 +148,7 @@ and secondary database-only appliances can be configured.

4. For **Are you sure you want to continue?** Select `y`.

5. Enter the primary database-only appliance’s name and access
4. Enter the primary database-only appliance’s name and access
details:

1. Enter the hostname for the primary database-only appliance.
Expand Down Expand Up @@ -236,23 +220,14 @@ standby appliance to the cluster.
`/etc/chrony.conf` with valid NTP server information.

3. From your host environment, open the appliance and configure the
network:

1. Log in to the appliance and run the `appliance_console` command
to access the appliance console menu.

2. Configure networking as desired by selecting the **Set DHCP
Network Configuration** or **Set Static Network Configuration**
option.
network and hostname using nmcli or nmtui from the console or from your
web browser using Cockpit on port 9090

4. Re-synchronize time information across the appliances:

# systemctl enable chronyd.service
# systemctl start chronyd.service

5. In the appliance console, configure the hostname by selecting **Set
Hostname**.

You can now configure this appliance as a standby database-only
appliance in the cluster.

Expand Down Expand Up @@ -322,14 +297,8 @@ and any additional appliances in the region using the following steps:
`/etc/chrony.conf` with valid NTP server information.

3. From your host environment, open the appliance and configure the
network:

1. Log in to the appliance and run the `appliance_console` command
to access the appliance console menu.

2. Configure networking as desired by selecting the **Set DHCP
Network Configuration** or **Set Static Network Configuration**
option.
network and hostname using nmcli or nmtui from the console or from your
web browser using Cockpit on port 9090

4. Re-synchronize time information across the appliances:

Expand All @@ -338,11 +307,9 @@ and any additional appliances in the region using the following steps:

5. In the appliance console, configure the following:

1. Configure the hostname by selecting **Set Hostname**.

2. Select **Configure Application**.
1. Select **Configure Application**.

3. Configure this appliance to use the encryption key from the
2. Configure this appliance to use the encryption key from the
primary database-only appliance:

1. For **Encryption Key**, select **Fetch key from remote
Expand All @@ -363,7 +330,7 @@ and any additional appliances in the region using the following steps:
7. Select **Join Region in External Database** from the
appliance console menu.

4. Enter the primary database-only appliance’s name and access
3. Enter the primary database-only appliance’s name and access
details:

1. Enter the hostname for the primary database-only appliance.
Expand Down
8 changes: 4 additions & 4 deletions high_availability_guide/_topics/renaming_ha_appliances.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,8 +42,8 @@ following:

Run the following steps on your primary database-only appliance:

1. In the appliance console menu, configure the new hostname or IP
address from the **Configure Network** option.
1. Configure the network and hostname using nmcli or nmtui from the console or
from your web browser using Cockpit on port 9090

2. Restart the appliance.

Expand All @@ -54,8 +54,8 @@ Run the following steps on your primary database-only appliance:

Run the following steps on your standby database-only appliances:

1. In the appliance console menu, configure the new hostname or IP
address from the **Configure Network** option.
1. Configure the network and hostname using nmcli or nmtui from the console or
from your web browser using Cockpit on port 9090

2. Restart the appliance.

Expand Down