7.5. Host Tasks

1. Click Compute Hosts.
2. Click New.
3. Use the drop-down list to select the Data Center and Host Cluster for the new host.
4. Enter the Name and the Hostname of the new host. The standard SSH port, port 22, is auto-filled in the SSH Port field.

5. Select an authentication method to use for the Manager to access the host.

   • Enter the root user’s password to use password authentication.
   • Alternatively, copy the key displayed in the SSH Public Key field to /root/.ssh/authorized_keys on the host to use public key authentication.

6. Click the Advanced Parameters button to expand the advanced host settings.

   1. Optionally disable automatic firewall configuration.
   2. Optionally add a host SSH fingerprint to increase security. You can add it manually, or fetch it automatically.
7. Optionally configure Power Management, SPM, Console, Network Provider, and Kernel. See Section 7.5.4, “Explanation of Settings and Controls in the New Host and Edit Host Windows” for more information. Hosted Engine is used when deploying or undeploying a host for a self-hosted engine deployment.
8. Click OK.

1. Click Compute Hosts.
2. Click New.
3. Use the drop-down menu to select the Host Cluster for the new host.
4. Select the Foreman/Satellite check box to display the options for adding a Satellite host provider host and select the provider from which the host is to be added.

5. Select either Discovered Hosts or Provisioned Hosts.

   • Discovered Hosts (default option): Select the host, host group, and compute resources from the drop-down lists.

   • Provisioned Hosts: Select a host from the Providers Hosts drop-down list.

     Any details regarding the host that can be retrieved from the external provider are automatically set, and can be edited as desired.

6. Enter the Name and SSH Port (Provisioned Hosts only) of the new host.

7. Select an authentication method to use with the host.

   • Enter the root user’s password to use password authentication.
   • Copy the key displayed in the SSH PublicKey field to /root/.ssh/authorized_hosts on the host to use public key authentication (Provisioned Hosts only).

8. You have now completed the mandatory steps to add a Red Hat Enterprise Linux host. Click the Advanced Parameters drop-down button to show the advanced host settings.

   1. Optionally disable automatic firewall configuration.
   2. Optionally add a host SSH fingerprint to increase security. You can add it manually, or fetch it automatically.
9. You can configure the Power Management, SPM, Console, and Network Provider using the applicable tabs now; however, as these are not fundamental to adding a Red Hat Enterprise Linux host, they are not covered in this procedure.
10. Click OK to add the host and close the window.

1. Add the Satellite server as an external provider. See Section 11.2.1, “Adding a Red Hat Satellite Instance for Host Provisioning” for more information.

2. Associate the required host with the Satellite server.

   Note

   The host must be registered to the Satellite server and have the katello-agent package installed.

   For more information on how to configure host registration see Configuring a Host for Registration in the Red Hat Satellite User Guide. For more information on how to register a host and install the katello-agent package see Registration in the Red Hat Satellite User Guide.

   1. Click Compute Hosts and select the host.
   2. Click Edit.
   3. Select the Use Foreman/Satellite check box.
   4. Select the required Satellite server from the drop-down list.
   5. Click OK.

1. Click Compute Hosts and select a host.
2. Click Management Maintenance, and click OK to confirm.
3. When the host is in maintenance mode, click Edit.
4. Click the Power Management tab.
5. Select the Enable Power Management check box to enable the fields.

6. Select the Kdump integration check box to prevent the host from fencing while performing a kernel crash dump.

   Important

   If you enable or disable Kdump integration on an existing host, you must reinstall the host for kdump to be configured.

7. Optionally, select the Disable policy control of power management check box if you do not want your host’s power management to be controlled by the Scheduling Policy of the host’s cluster.
8. Click the plus (+) button to add a new power management device. The Edit fence agent window opens.
9. Enter the User Name and Password of the power management device into the appropriate fields.
10. Select the power management device Type in the drop-down list.
11. Enter the IP address in the Address field.
12. Enter the SSH Port number used by the power management device to communicate with the host.
13. Enter the Slot number used to identify the blade of the power management device.

14. Enter the Options for the power management device. Use a comma-separated list of 'key=value' entries.

    • If both IPv4 and IPv6 IP addresses can be used (default), leave the Options field blank.
    • If only IPv4 IP addresses can be used, enter inet4_only=1.
    • If only IPv6 IP addresses can be used, enter inet6_only=1.
15. Select the Secure check box to enable the power management device to connect securely to the host.
16. Click Test to ensure the settings are correct. Test Succeeded, Host Status is: on will display upon successful verification.
17. Click OK to close the Edit fence agent window.
18. In the Power Management tab, optionally expand the Advanced Parameters and use the up and down buttons to specify the order in which the Manager will search the host’s cluster and dc (datacenter) for a fencing proxy.
19. Click OK.

1. Click Compute Hosts.
2. Click Edit.
3. Click the SPM tab.
4. Use the radio buttons to select the appropriate SPM priority for the host.
5. Click OK.

1. Click Compute Hosts and select the desired host.
2. Click Management Maintenance to open the Maintenance Host(s) confirmation window.

3. Optionally, enter a Reason for moving the host into maintenance mode, which will appear in the logs and when the host is activated again.

   Note

   The host maintenance Reason field will only appear if it has been enabled in the cluster settings. See Section 5.2.2, “General Cluster Settings Explained” for more information.

4. Optionally, select the required options for hosts that support Gluster.

   Select the Ignore Gluster Quorum and Self-Heal Validations option to avoid the default checks. By default, the Manager checks that the Gluster quorum is not lost when the host is moved to maintenance mode. The Manager also checks that there is no self-heal activity that will be affected by moving the host to maintenance mode. If the Gluster quorum will be lost or if there is self-heal activity that will be affected, the Manager prevents the host from being placed into maintenance mode. Only use this option if there is no other way to place the host in maintenance mode.

   Select the Stop Gluster Service option to stop all Gluster services while moving the host to maintenance mode.

   Note

   These fields will only appear in the host maintenance window when the selected host supports Gluster. See Replacing the Primary Gluster Storage Node in Maintaining Red Hat Hyperconverged Infrastructure for more information.

5. Click OK to initiate maintenance mode.

1. Click Compute Hosts and select the host.
2. Click Management Activate.

Configuring Firewall Rules for Hosts

1. On the Manager machine, edit ovirt-host-deploy-post-tasks.yml.example to add a custom firewall port:

   # vi /etc/ovirt-engine/ansible/ovirt-host-deploy-post-tasks.yml.example
   ---
   #
   # Any additional tasks required to be executing during host deploy process can
   # be added below
   #
   - name: Enable additional port on firewalld
     firewalld:
       port: "12345/tcp"
       permanent: yes
       immediate: yes
       state: enabled

2. Save the file to another location as ovirt-host-deploy-post-tasks.yml.

1. Click Compute Hosts and select the host.
2. Click Management Maintenance.
3. when the host is in maintenance mode, click Remove to open the Remove Host(s) confirmation window.
4. Select the Force Remove check box if the host is part of a Red Hat Gluster Storage cluster and has volume bricks on it, or if the host is non-responsive.
5. Click OK.

Procedure

1. Click Compute Hosts and select the host.
2. Click Management Maintenance.
3. Click Installation Reinstall to open the Install Host window.
4. Click OK to reinstall the host.

1. Click Compute Hosts and select a host.
2. Click More Actions Assign Tags.
3. Select the check boxes of applicable tags.
4. Click OK.

1. Click Compute Hosts.
2. Click the host’s name to open the details view.
3. Click the Errata tab.

1. Click Compute Hosts.
2. Click the host’s name to open the details view.
3. Click Host Devices tab.

1. In the Administration Portal, click Compute Hosts.
2. Click the host’s name to open the details view.
3. Click the General tab, and click Hardware. Locate the GPU device vendor ID:product ID. In this example, the IDs are 10de:13ba and 10de:0fbc.
4. Right-click the host and select Edit. Click the Kernel tab.

5. In the Kernel command line free text entry field, enter the IDs located in the previous steps.

   pci-stub.ids=10de:13ba,10de:0fbc

6. Blacklist the corresponding drivers on the host. For example, to blacklist nVidia’s nouveau driver, next to pci-stub.ids=xxxx:xxxx, enter rdblacklist=nouveau.

   pci-stub.ids=10de:13ba,10de:0fbc rdblacklist=nouveau

7. Click OK.
8. Click Installation Reinstall to commit the changes to the host.
9. Reboot the host after the reinstallation is complete.

For Linux

1. Only proprietary GPU drivers are supported. Black list the corresponding open source driver in the grub configuration file. For example:

   $ vi /etc/default/grub
   ...
   GRUB_CMDLINE_LINUX="nofb splash=quiet console=tty0 ... rdblacklist=nouveau"
   ...

2. Locate the GPU BusID. In this example, is BusID is 00:09.0.

   # lspci | grep VGA
   00:09.0 VGA compatible controller: NVIDIA Corporation GK106GL [Quadro K4000] (rev a1)

3. Edit the /etc/X11/xorg.conf file and append the following content:

   Section "Device"
   Identifier "Device0"
   Driver "nvidia"
   VendorName "NVIDIA Corporation"
   BusID "PCI:0:9:0"
   EndSection

4. Restart the virtual machine.

For Windows

1. Download and install the corresponding drivers for the device. For example, for Nvidia drivers, go to NVIDIA Driver Downloads.
2. Restart the virtual machine.

1. In the Administration Portal, click Compute Hosts and select a host.
2. Click Host Console.

1. On the Manager machine, create a file in the directory /usr/share/ovirt-engine/playbooks. For example:

   # vim /usr/share/ovirt-engine/playbooks/change-spice-cipher.yml

2. Enter the following in the file and save it:

   name: oVirt - setup weaker SPICE encryption for old clients
   hosts: hostname
   vars:
     host_deploy_spice_cipher_string: 'DEFAULT:-RC4:-3DES:-DES'
   roles:
     - ovirt-host-deploy-spice-encryption

3. Run the file you just created:

   # ansible-playbook -l hostname /usr/share/ovirt-engine/playbooks/change-spice-cipher.yml